Proscube
 
All articles

MIGRATIONS

The Shopify migration checklist, in the order that protects traffic

The sequence matters more than the list. Most migrations fail because the steps happened in the wrong order.

By Manpreet Singh·October 6, 2026·10 min read
The Shopify migration checklist, in the order that protects traffic

Most migration failures are sequencing failures. The list below is ordered deliberately — doing step six before step two is how stores lose a third of their organic traffic.

Before anything is built

1. Export every URL. From your CMS, your sitemap, Search Console and your analytics. The four lists will not match, and the union of them is your real URL inventory.

2. Rank them by traffic and links. You cannot map everything manually. Sort by sessions and by referring domains; the top of that list is what must not break.

3. Export the product data and read it. Not just the count. Look at how variants, options and custom fields are actually structured, because that mapping is the bulk of the work and it is where quotes go wrong.

4. Inventory the apps and integrations. Each one is a workstream. An integration discovered in week five costs five times what it costs in week one.

If an agency has quoted without seeing a real catalogue export and a URL list, the number is a guess. This is the single most reliable tell in migration quoting.

While building

5. Build the redirect map as a document, not as code. Old URL to new URL, reviewed by someone who knows the business. Redirecting everything to the homepage is worse than a 404 — Google treats it as a soft 404 and you lose the signal either way.

6. Reproduce structured data. Product, breadcrumb, and anything else the old site emitted.

7. Keep the titles and headings. A rebuild is the wrong time to also rewrite every title tag. Change one variable at a time.

Before cutover

8. Test the redirects on staging. Every mapped URL, automatically, with the result recorded. This is a script, not a spot check.

Related service

Planning a replatform?

See how we run migrations

9. Check the new site is crawlable. The most common launch failure in this whole list is a staging noindex shipped to production.

10. Have a rollback you could actually execute. Not theoretical.

At cutover

11. Go live, then submit the new sitemap immediately.

12. Watch Search Console daily for two weeks. Coverage errors, 404 spikes, and the index count.

WHAT A REPLATFORM DOES TO TRAFFICCUTOVERNO REDIRECT MAPMAPPED FIRSTTHE DIFFERENCE IS PLANNING, NOT PLATFORM
Organic traffic through a replatform with and without the mapping done first. The recovery curve is what brands underestimate.

The mistake worth naming

Do not redesign at the same time. When traffic moves you will not know whether the platform, the URLs or the new design caused it. Migrate, stabilise, then redesign.

It is slower and it is the difference between a diagnosable outcome and a mystery.

Talk it through

Send us your platform and a URL export.

We will tell you what the migration actually involves, where the risk sits, and what it should cost.

Get it scoped

A real read within one business day — not a sales call.

About the author

Manpreet Singh

Founder of Proscube. Leads the studio's Shopify, headless and CRO engineering, and works directly with founders rather than through account managers.

More about Manpreet

Work with us

Want help with this? Here’s how we do Ecommerce Migrations.