Shopify Store Migration Checklist: 40 Pre-Launch Items

Key takeaways

A missing or broken 301 redirect map is the most common cause of a post-migration traffic drop.
Metafields, reviews and subscription data rarely move on their own. Each needs its own export, its own field mapping and a manual spot-check before launch.
Moving from a stock theme to Shopify Hydrogen keeps checkout inside Shopify but rebuilds the storefront as custom code. That's a different job to a theme swap, with its own checklist.
Analytics continuity depends on annotating GA4 at the exact cutover time and reconciling week one revenue against Shopify's own reports. Don't assume the two will agree.
A fixed-price migration should say in writing, before work starts, which of these 40 items are included and who owns testing before DNS cutover.

This Shopify store migration checklist is ordered the way the work actually happens: audit, build, final checks, launch. Work through it in order and you protect rankings, revenue and the data you use to judge both.

Why Shopify migrations lose traffic (and how much)

A clean migration costs you a little traffic for a short time. Well-executed Shopify moves typically see a dip of 10 percent or less, recovering within one to six months. A badly planned one is a different story: migrations that skip proper redirects have seen traffic losses as severe as 50 percent.

The gap between those two outcomes is almost never design. It's three unglamorous things.

The 301 redirect gap

Shopify enforces its own URL paths. Products live under /products/, collections under /collections/. If your old store used a flat structure or a different CMS, every one of those URLs changes. Without 301 redirects, users and crawlers land on 404 pages, and the link equity those pages earned goes nowhere. With clean 301s and preserved metadata, most sites recover within a few weeks to a couple of months, and some improve.

Metafields that don't map cleanly

Metafields hold the things your theme doesn't: ingredient lists, sizing tables, origin data, care instructions. They're attached to your products, not your theme, but the templates that render them are not. Swap the theme and the data survives, invisible. Move platforms and it often doesn't. Export metafields and metaobjects as their own file, map every key, then check ten products by eye.

App shutdowns nobody notices until launch day

A pre-migration audit should catalogue every connected system: ERP, CRM, WMS, PIM, email platform, loyalty programme, review platform and subscription tools. These break silently. Nothing errors. The reviews just stop showing, and you find out from a customer three weeks later.

The 40-item Shopify store migration checklist, in launch order

Four phases. Do them in sequence.

Phase	Items	Typical duration	Usually owned by	What breaks if skipped
Before the build	1–10	3–5 days	Client + studio together	Redirects get built from guesswork
During development	11–25	2–6 weeks	Developer	SEO metadata, apps and tracking arrive half-built
48 hours before launch	26–35	2 days	Whoever signs off launch	Broken checkout, wrong inventory, no rollback
Launch day and week one	36–40	7–14 days	Studio, monitored daily	Traffic loss you spot a month late

Before the build starts (items 1–10)

Crawl the live site and export every indexed URL from Search Console.
Record a baseline: organic sessions, top 50 landing pages, conversion rate, monthly revenue.
Catalogue every connected system, including anything finance or ops uses.
List every installed app with its monthly cost and whether it depends on Liquid.
Export products, variants, inventory and collections as CSV.
Export metafields and metaobjects as separate files.
Export customer accounts, and accept that passwords cannot be migrated.
Export orders, flagging anything still open or on an active subscription.
Agree the new URL structure in writing before anyone builds a template.
Agree who signs off launch and who holds DNS access.

During development (items 11–25)

Build the redirect map: one row per old URL, no wildcards for money pages.
Rebuild page titles and meta descriptions for every template and priority page.
Recreate structured data: Product, Offer, Breadcrumb, Organization.
Set canonicals, and check filtered and paginated collection URLs.
Preserve image alt text; if filenames change, redirect the image URLs too.
Generate the sitemap and confirm robots.txt carries no leftover staging rules.
Password-protect staging and block indexing on the development domain.
Migrate reviews through the app's own export and import, never by hand.
Rebuild subscription contracts with the app vendor directly.
Recreate discount codes, automatic discounts and gift cards.
Recreate shipping profiles, zones, rates and tax settings.
Test every payment gateway, including local methods, in test mode.
Rebuild transactional emails and verify the sending domain and DKIM.
Install GA4, GTM and the Meta Pixel, then fire a test purchase event.
Check Core Web Vitals per template. Target LCP under 2.5 seconds on throttled mobile.

48 hours before launch (items 26–35)

Crawl staging in full. Zero 404s, zero broken internal links.
Spot-check 50 redirect rows manually, weighted towards your top traffic pages.
Reconcile product, variant and inventory counts against the old store.
Place a real order end to end, then refund it.
Test subscription checkout and a returning customer login.
Test on iOS Safari, Android Chrome and one desktop browser.
Check localised routes and hreflang if you run bilingual pages.
Drop DNS TTL to 300 seconds.
Freeze catalogue and content changes.
Write the rollback plan: the trigger, the owner, the time it takes.

Launch day and the week after (items 36–40)

Cut DNS, force HTTPS, confirm www and non-www resolve one way.
Resubmit the sitemap and request indexing on your top 20 pages.
Annotate GA4 with the exact cutover timestamp.
Check Search Console coverage and 404 reports daily for 14 days.
Reconcile week one revenue in GA4 against Shopify's reports before drawing conclusions.

Redirect maps: the single biggest cause of post-migration traffic loss

This is the item that decides whether you lose 5 percent or 50. Treat it as the core of any ecommerce migration SEO checklist.

Pull three sources: a full crawl of the live site, the Search Console page export for the last 12 months, and your backlink list. Deduplicate into one spreadsheet with two columns, old and new. Sort by sessions. The top 200 rows get mapped by hand; everything below can follow a pattern rule, as long as you test a sample from each pattern.

Never point a retired product to the homepage. Send it to the closest live product or its parent collection. A homepage redirect tells Google the page had no specific meaning, and rankings follow that signal.

A 301 says permanent and passes ranking signals. A 302 says temporary and often doesn't. Developers reach for 302 in staging because it's easier to reverse, then forget to switch. Check the response code, not the browser behaviour — both look identical to a human.

You can test most of the map before you go live. Run the old URL list against the staging domain with the path swapped in, and log the status codes. You want 301 then 200, in one hop. Chains of two or three redirects leak and slow the page. Anything returning 404, 302 or a chain gets fixed before cutover, not after.

When a theme migration isn't enough: moving to headless Shopify (Hydrogen)

You're paying for four apps to fake one feature. Your product page needs logic a theme editor can't express, like configurators or region-specific bundles. Your Core Web Vitals sit red on mobile no matter how much you strip out. Or your pricing is premium and the store doesn't look it. A better theme would be faster and cheaper, and it would still be a theme. That's the trade-off to be honest about.

Our own write-up of when a headless rebuild actually pays off covers a Cretan olive oil brand where the storefront was rebuilt as software, checkout stayed in Shopify, and monthly sales went up eighteen times with no ad spend.

Checkout, payments, tax and orders stay in Shopify. Everything a customer sees before checkout becomes your code. That means Liquid-dependent apps stop working. Many Shopify apps were built specifically for Liquid themes and need custom integration work, so check each app's headless compatibility before you commit, not after.

Create a development store in your Partner account, connect it to the Storefront API, and build against it with real product data. Hydrogen was rebuilt in Spring 2026 to run on any stack, including Next.js, which removes the old choice between Shopify's framework and your preferred one. Keep the dev store password-protected and noindexed until cutover.

App parity: checking what breaks when you switch platforms or themes

Reviews usually migrate through the vendor's own tool, but star ratings in search results depend on structured data your new templates must output. Loyalty points balances need a vendor-side export. Subscriptions are the riskiest: active contracts are tied to payment tokens, so rebuild them with the app provider and confirm the next billing date on a live customer before launch.

Every pixel that lived in the old theme's code disappears with the theme. Reinstall, then verify with a real test purchase that the event fires once, with the correct value and currency. Double-firing purchase events is the quiet way to inflate reported ROAS for a month.

Form endpoints change. Webhooks point at old URLs. If you run CRM and WhatsApp integrations off order events or abandoned checkouts, fire one of each in staging and confirm the record lands in the right pipeline with the right fields. Test the abandoned-cart flow specifically — it's the one nobody remembers until sales dip.

Analytics handover: keeping historical data after migration

Log the exact timestamp of DNS cutover as a GA4 annotation, and note it in whatever dashboard your board reads. Without it, week one looks like a performance story rather than a migration artefact.

Client-side tags break easily on a headless build because the DOM they expect no longer exists. Server-side tracking through Shopify's order events survives the change and resists ad blockers. Post-launch you need to re-link GA4 via the Google & YouTube channel, the Meta Pixel via the Facebook channel or the theme, and Google Tag Manager for custom events.

For the first seven days, compare GA4 revenue against Shopify's own sales report daily. A variance of 2 to 5 percent is normal, driven by refunds and blocked scripts. Anything above 10 percent means a tag is missing or firing twice, and you should fix it before you make a single budget decision on those numbers.

Who should run this checklist: in-house, freelancer or a studio

If you have a developer on staff and your store is a straight theme swap with under 500 SKUs, run it in-house. A freelancer is fine when the catalogue is simple and no subscriptions are involved. Bring in a studio when subscriptions, metafields, bilingual routes or a headless rebuild are in scope, because those are the items where a mistake is expensive and hard to reverse.

Ask any studio for the list. A serious quote names which of these 40 items are in scope, who tests before cutover, and what happens if traffic drops. We do headless Shopify builds and site speed rescues on a fixed scope, fixed price agreed before work starts, from $2,000, with no hourly billing and nothing charged for the first call.

Before you hire, ask: who writes the redirect map, and do I get to review it? Which apps will stop working? Who owns DNS on launch day? What's the rollback trigger? If the answers are vague, the migration will be too.

Frequently asked questions

How long does a Shopify migration take from start to launch?

A theme-to-theme migration on a clean catalogue usually runs two to four weeks. A platform move with subscriptions, metafields and multiple integrations runs six to twelve. A full headless rebuild in Hydrogen or Next.js takes longer again, because the storefront is being written rather than configured.

Will I lose my Google rankings after migrating a Shopify store?

Expect a short dip. Well-executed migrations typically lose 10 percent or less and recover within one to six months. Skip the redirect map and losses as severe as 50 percent are on the table. The difference is almost entirely items 11, 27 and 39 on this list.

Do I need a developer to migrate a Shopify theme, or can I do it myself?

A straightforward theme swap with no metafields, no subscriptions and fewer than 500 products is doable in-house if someone is comfortable with CSV exports and Shopify's redirect tool. Once custom metafields, review apps or active subscription contracts are involved, the failure modes are silent and a developer pays for themselves.

What's the real difference between migrating to a new theme and going headless with Hydrogen?

A theme swap changes the templates rendering your store; Shopify still controls the front end. Headless replaces the entire storefront with your own code while checkout stays in Shopify. The second gives you full control of performance and behaviour, and costs you every Liquid-dependent app unless it's rebuilt.

How do I test a migration properly before it goes live?

Crawl the password-protected staging store for 404s and broken links, run your old URL list against staging to check redirect status codes, place and refund a real order, and reconcile product and inventory counts against the live store. Then test on iOS Safari and Android Chrome, not just your desktop. Write the rollback plan before you touch DNS.

What happens to my product reviews and subscriptions during a migration?

Reviews migrate through the review app's own export and import, and you need the new templates to output review structured data or your star ratings disappear from search results. Subscriptions are tied to payment tokens and must be rebuilt with the subscription vendor, never recreated by hand. Verify one live contract's next billing date before cutover.

If you're weighing a theme swap against a full headless rebuild, book the free 30-minute call and we'll tell you honestly which one your store needs.