← Blog

Freelancer vs agency Shopify theme migration: how to choose

For e-commerce and operations managers who want a faster Shopify store without losing sales or rankings: how to choose between a freelancer and an agency, and what to ask.

Get a summary withChatGPT Claude Google AI Mode
Three paths leading to one bright storefront door, a metaphor for freelancer vs agency Shopify theme migration
On this page

If your Shopify theme is slow, you want the fix to cost you as few sales and rankings as possible. The short answer to freelancer vs agency Shopify theme migration: a freelancer suits a small store with a simple catalogue and few apps, a small agency suits most stores with several apps that need QA and support, and a large agency suits multi-market or Shopify Plus builds.

The choice matters less than how the project is scoped. A theme move touches your templates, apps, tracking and search metadata, and whoever does it should show you each of those in writing before they start.

Below you get a comparison, a way to match the route to your store, the parts a proper migration includes, a method to measure the speed gain, eight questions and the contract points to sign. This covers a one-off project. For ongoing upkeep, see our comparison of freelancer vs agency for website maintenance.

Key takeaways

  • A freelancer fits a small store with a simple catalogue and few apps, a small agency fits most stores with several apps, and a large agency fits multi-market or Shopify Plus builds.
  • A proper migration covers six parts (audit, app cleanup, Liquid rebuild, redirects, tracking and QA), so you can check any quote against that list.
  • You can measure the gain with Core Web Vitals, Lighthouse and conversion rate, recorded before the move and compared after it.
  • Code ownership, a staging store, a handover and a warranty window in the contract keep your store safe whoever builds it.

Freelancer vs agency Shopify theme migration, side by side

Start with the table: it shows the trade-offs of the three routes before the detail. Cost describes what moves a quote, not a price list, because your apps, catalogue and markets change the figure more than the type of provider does.

Three paths of different widths leading to the same lit storefront door, one per hiring route
Three hiring routes, one goal: a faster store
FreelancerSmall agencyLarge agency
Cost rangeUsually the lowest quote, driven by hoursMid-range, often priced per phaseHighest, includes project management and review layers
SpeedQuick to start, paced by one calendarParallel work by two or three peopleSlower to kick off, strong on big parallel builds
Bus factorOne person knows your storeA few people know itMany people, with formal handover
QADepends on the person, often self-checkedUsually a second person tests before launchDedicated QA role and test plans
Support after launchAd hoc, by availabilityOften a monthly planRetainer or service agreement

Bus factor means how many people can be away before your project stops. It is the row that surprises owners most.

Cost range and what drives it

The main cost drivers are the number of apps to review, the number of distinct templates, custom sections, markets and languages, and how much tracking must be rebuilt. Ask every provider for a quote split into audit, build, QA and support. Then three quotes become comparable, and you see who priced the risky parts.

If you want to know what it costs to replace a slow Shopify theme, treat any figure given before an audit as a guess. A short audit turns the guess into a scope.

Speed, bus factor and QA

A freelancer can often start sooner, because there is no queue of handoffs. The risk is one calendar: if that person falls ill or takes a bigger client mid-project, your launch date moves and nobody else knows your store.

A small agency spreads that knowledge across two or three people, and a second person usually checks the work before launch. A large agency adds dedicated QA and project management, which helps on a big build and slows a small one down.

Local or remote: what proximity adds

A local team gives you in-person workshops, your language and your time zone. Those help when several people in your company must agree on design and content. A remote team works well when working hours overlap and replies are fast, and it widens your choice.

Proximity is a convenience, so judge a local agency by the same eight questions as any other. We work with stores in the United States, Spain and Latin America, so overlapping hours are part of how we plan.

Freelancer or agency: match it to your store

Choose by four things: store size, catalogue complexity, number of apps and how much support you will need after launch. Each one points to a route.

Small store with a simple catalogue

If you sell a few hundred products in one market, with a handful of apps and a few templates, a freelancer can run the whole move. Pick one who shows a staging theme, a written scope and a recent store they moved. Keep the project small and the checks written down.

Mid-sized store with many apps

At around ten or more apps, the risk moves from design to scripts, tracking and checkout behaviour, because each app can add its own code to your theme. A small agency suits this: one person audits the apps, another builds and a third tests.

For example (an illustrative case), a store with 300 products, 12 apps, one market and paid ads has few templates but many scripts. The audit and the tracking test carry most of the risk there.

Large catalogue, markets or Shopify Plus

Multiple markets and languages, B2B pricing, Shopify Plus checkout customizations or tens of thousands of products call for more people and more process. A large agency fits when you need formal governance and many stakeholders. A small agency with Plus experience can also fit, usually at a lower cost. Ask which people named in the proposal will actually do the work.

When support after launch decides it

A theme move does not end at launch. Weeks later a payment app update, a campaign page or a new section can need a fix, and you want to know who answers.

The deciding question

Ask who answers when something breaks after launch, not who quotes the lowest price. A cheap build with nobody on call costs more the first time checkout fails on a sale day.

A freelancer can offer this too, if they commit in writing to a response time and name a backup person. Without that commitment, a small agency with a support plan is the safer route.

What a theme migration includes

A migration is more than installing a new theme. Use the six steps below as a checklist against any quote: if one is missing, ask who covers it.

  1. Audit and baseline

    List every template, section, app, script and tracking tag, and record your current speed and conversion numbers.

  2. App cleanup

    Decide for each app whether to keep it, replace it with a native theme feature or remove it.

  3. Liquid rebuild on staging

    Recreate your templates and sections on an unpublished theme you can preview.

  4. Redirects and metadata

    Map any changed URL to its new address and carry over titles, descriptions and structured data.

  5. Tracking

    Rebuild analytics events and ad pixels, then test them with a real order.

  6. QA and launch

    Test cart, checkout, forms and markets on real devices, publish and watch the numbers.

The order protects your sales. The new theme is built beside the live one, so customers keep buying on the current theme until the day you publish.

Safe theme move

  1. 01Audit and baselineTemplates, apps, tags, speed and conversion
  2. 02App cleanupKeep, replace or remove each app
  3. 03Staging rebuildNew theme built beside the live one
  4. 04QA and checksRedirects and tracking tested with a real order
  5. 05Publish and monitorOld theme stays live until this day

Flow of a safe Shopify theme move: audit, app cleanup, staging rebuild, QA and publish while the live store keeps selling

A safe theme move builds beside the live store

Audit and app cleanup

The audit finds what slows the store, and the cleanup removes it. Uninstalled apps can leave snippets behind in theme files, so a clean rebuild often drops weight nobody added on purpose. Our guide to the Shopify app ecosystem, its limits and hidden costs explains where that weight comes from.

It also helps to know what Shopify hosts and what your theme controls, which how Shopify works lays out. Shopify's own theme performance best practices (opens in a new tab) are a good reference for what an audit should check.

Liquid rebuild on a staging theme

Liquid is Shopify's theme language, and it decides how each page is assembled. The rebuild recreates your sections, templates and settings on an unpublished copy, so you can preview every page with real products. How the Liquid theme system builds scalable stores shows what is being rebuilt. Ask how your current homepage banners and metafields will be moved across.

Redirects, tracking and QA

A theme change on its own usually leaves product and collection URLs as they are, because those come from Shopify's structure and not from the theme. If any URL does change, such as a blog path or a landing page, it needs a 301 redirect, as Google's guide to site moves with URL changes (opens in a new tab) explains. Check that titles, meta descriptions, structured data and canonical tags carry over too.

Tracking is the other quiet loss. Test GA4 events, ad pixels and the purchase event with a real test order. QA then covers the cart, discount codes, forms, each market and the main phones.

Measure the speed gain before and after

You can prove the gain instead of trusting a feeling. Google publishes thresholds for three Core Web Vitals, the measures of speed and stability real visitors experience, and web.dev (opens in a new tab) explains each one.

2.5s

LCP target

How fast the main content appears, Google's good threshold at the 75th percentile

200ms

INP target

How fast the page answers a tap, Google's good threshold

0.1

CLS target

How little the layout shifts, Google's good threshold

Put these three targets in the proposal, so "faster" has a number everyone can check.

Capture a baseline first

Before any work, record numbers for five pages: home, a collection, a product, the cart and a blog post if it brings traffic. Save the Core Web Vitals report from Search Console and the PageSpeed Insights results on mobile. Add your conversion rate, add-to-cart rate and revenue per session for the last four weeks, with the date on the file.

Compare field data and lab data

Field data comes from real visitors and uses a rolling 28-day window, so it moves slowly after launch. Lab data, such as Lighthouse, is a controlled test you can run the same day. Use Lighthouse to verify the build and field data to confirm that visitors feel the change.

Run lab tests with the same device settings before and after, and take the median of several runs, because single scores vary.

Watch conversion rate after launch

Compare the same weekdays and set aside campaign spikes and sale periods. A faster store tends to help conversion, but price changes and traffic mix move it too. Read the trend across a few weeks, not one day.

Red flags and eight questions before you sign

The same vetting works for a freelancer, a local agency or a large firm. The red flags tell you to slow down, and the questions show you how the provider really works.

Red flags in a proposal

  • A fixed price offered without seeing your apps or analytics.
  • A promised Lighthouse score, when scores vary between runs and devices.
  • Work done directly on your live theme.
  • No mention of redirects, metadata or tracking.
  • Code that lives only in the provider's account.
  • One person who holds all the knowledge, with no documentation.

Eight questions to ask

  1. Which stores have you moved off a slow theme, and what changed in their speed?
  2. What does your audit cover, and what will I receive from it?
  3. How do you decide which apps stay, go or get replaced?
  4. Will you build on an unpublished theme and give me a preview link?
  5. How do you protect URLs, metadata and structured data?
  6. How do you test tracking and checkout before launch?
  7. Who else knows my store, and who covers if you are unavailable?
  8. What happens after launch: warranty, response time and support options?

Good answers are specific and come with an example. Vague answers such as "we follow best practices" tell you the process is not written down.

Contract points that protect your store

The contract is where a good conversation becomes a safe project. These points keep your store protected whoever builds it, and they cost nothing to ask for.

A key passing from one hand to another over a tidy workbench, standing for code ownership and handover
Code ownership and a clear handover keep you in control

Code ownership and repository access

The theme code should belong to you, and you should hold admin access to the store and the code repository. Ask for the theme to be delivered in your own Shopify account, not only exported at the end. This avoids a standoff if you change provider later.

Staging store and launch plan

Put in writing that the work happens on an unpublished theme or a development store, with a preview link for your team. Agree the launch day, a low-traffic time and a rollback plan. Rolling back should mean re-publishing the previous theme, which stays untouched.

Handover and warranty window

The handover is a short document: which apps remain and why, how sections are used, where tracking lives and how redirects were mapped. A warranty window, for example a few weeks in which defects from the migration are fixed at no charge, closes the project cleanly. Use this checklist when you read a draft contract.

  • Code ownership stated in your name
  • Repository and store access for you
  • Staging store or unpublished theme with a preview link
  • Redirects map delivered before launch
  • Tracking signed off with a test order
  • Handover document included in the price
  • Warranty window and response time written down

How werun.dev runs Shopify theme migrations

We start from your goal, such as a mobile product page that loads inside Google's 2.5 second target while keeping your review widget and checkout tracking. The goal sets the scope, and the scope sets the quote. You can see how we work on Shopify on our Shopify page for speed projects.

From your goal to a staging theme

We audit your theme, apps and baseline numbers, then agree with you which apps stay, go or get replaced. The rebuild happens on an unpublished theme, and you click on anything in the preview with Client Feedback to ask for a change. We then map redirects, test tracking with a real order and publish at a quiet hour. You see the progress in the client panel, and you get a reply within 2 hours on business days.

What the Care plan adds after launch

The Care plan is a monthly plan that keeps the store fast and working after the move. It covers fixes, app and theme updates, speed checks and a written monthly report, so you can see the numbers compared with your baseline. If you prefer a freelancer for the build, the contract points above still apply, and the Care plan can still cover the store afterwards.

Where to start this week

This week, record your baseline: the Core Web Vitals report, PageSpeed results for five pages, your conversion rate and a list of every app on the store with what it does. That one page already makes every quote comparable.

Then tell us your goal, for example a faster product page or fewer abandoned carts, on our Shopify page. We will tell you whether a freelancer, a small agency or our team fits your store, even when the answer is not us.

Frequently asked questions

Should I hire a freelancer or an agency to move my Shopify store off a slow theme?

A freelancer suits a small store with a simple catalogue and few apps. A small agency suits stores with several apps that need QA and support, and a large agency suits multi-market or Shopify Plus builds. Decide by who answers when something breaks after launch.

How much does it cost to replace a slow Shopify theme?

The cost depends on the number of apps, templates, custom sections, markets and tracking to rebuild. Ask for a quote split into audit, build, QA and support, because any figure given before an audit is a guess.

How long does a Shopify theme migration take?

A simple store usually takes a few weeks, and the time grows with apps, templates and markets. Most of it goes into the audit, the rebuild on a staging theme and QA, not into the launch itself.

Will changing my Shopify theme hurt my SEO?

A theme change usually keeps product and collection URLs, so the risk sits in lost titles, structured data and any URL that changes without a 301 redirect. Check those items before launch and compare Search Console after it.

Is a local web agency better than a freelancer for an ecommerce store?

Local is not better by default. It helps with in-person workshops, language and time zone, but the deciding factors are QA, support after launch and who else knows your store. Judge local and remote providers with the same questions.

What should a Shopify theme migration contract include?

It should include code ownership in your name, access to the store and repository, a staging theme, a redirects map, tracking sign-off, a handover document and a warranty window with a response time.

Running into this on your own stack?

Tell us the platform and the problem. We'll tell you what it takes and who does it.

Start a conversation No commitment. Just a conversation.