WooCommerce to Shopify Migration: What Actually Breaks

Most guides to WooCommerce to Shopify migration are guides to exporting products, which is the part that reliably works. Products, images, descriptions and prices move across with well-established tooling and rarely cause real trouble.

The things that go wrong are URLs, variant structures, customer accounts and redirects. Those are also the things that, when they go wrong, cost you traffic you had already earned.

This is a migration plan organised around the failure points.

What moves cleanly

Set expectations correctly on the easy parts, because they are genuinely easy.

Products. Titles, descriptions, images, prices, SKUs, inventory. Established migration tooling handles this, and for a standard catalogue it is close to routine.

Collections. WooCommerce categories map onto Shopify collections conceptually. The mapping needs review, because Shopify distinguishes manual and automated collections and your category logic may fit one better than the other, but the data moves.

Customers. Names, email addresses, addresses. With one enormous exception, covered below.

Content pages. About, contact, policies. Straightforward, though the URLs will change.

What actually breaks

URLs, and therefore SEO

This is the big one. WooCommerce and Shopify construct URLs differently, and Shopify's structure is not fully configurable. Product and category URLs will change, which means every indexed URL on your site needs an explicit redirect to its new destination.

This is the highest-stakes deliverable in the entire migration, and it is the one most often done partially. The failure mode is not a missing redirect returning a 404, which is at least visible. It is the lazy catch-all: redirecting everything that does not match a rule to the home page.

Build the redirect map from data, not from assumption:

1. Export every indexed URL. Use Search Console's page report and your existing sitemap, not a crawl alone, because a crawl misses URLs that are indexed but no longer linked.
2. Map each one to its new destination explicitly.
3. Include category pages, tag archives, paginated URLs and any content pages.
4. Test the map before cutover and again immediately after.
5. Re-check a sample a week later, because edge cases surface under real traffic.

Variant structures

WooCommerce attributes and variations do not map perfectly onto Shopify's option model. Shopify has a defined limit on options per product, and stores that used WooCommerce's flexibility to model complex products often need genuine rework rather than a data transform.

Find this out during planning, not during migration. Audit your most complex products first, not your simplest, because the simple ones tell you nothing about whether the migration is hard.

Customer passwords

Passwords are stored hashed. They cannot be migrated, from any platform to any other. Every customer will need to reset their password.

This is not a technical problem, it is a communications one, and it is where migrations lose customers who were otherwise perfectly happy. Plan the email. Send it at cutover, explain plainly why it is needed, and make the reset path obvious. A returning customer who hits a login failure with no explanation frequently does not come back for a second attempt.

Order history

Importable, but decide whether you want it. Historical orders in Shopify are records rather than live orders, and importing large volumes has implications for reporting and for how your numbers look afterwards. Some merchants import everything, some import a recent window, some keep a read-only archive of the old store. All three are defensible; drifting into it without deciding is not.

Sequencing the migration

Order matters more than speed.

Build first, migrate second. Get the Shopify store into a state you would be happy to launch before moving data into it. Migrating into a half-built store means finishing the build on a live site under real traffic.

Migrate data to a password-protected store. Shopify stores can be locked while you work. Use that. Import, check, fix, re-import.

Test on your worst products. The complex ones with many variants, the ones with unusual shipping rules, the bundles. If those work, the rest will.

Prepare redirects before cutover, not after. The window between DNS changing and redirects going live is a window where Google finds 404s.

Cut over at a genuinely quiet time. Not your peak season, not the week before a campaign. You want attention available for the two weeks afterwards.

Watch Search Console daily for a fortnight. Specifically coverage errors and any spike in 404s. This is when redirect gaps surface, and they are cheap to fix immediately and expensive to fix in three months.

The ranking dip is normal

Even a well-executed migration typically produces a temporary drop while Google recrawls, reprocesses redirects and re-establishes which URL is which. Recovery usually happens over weeks rather than days.

Knowing this in advance matters, because the panic response is to start changing things during the dip, which makes the cause of any subsequent movement impossible to read. Give a clean migration time before intervening.

What is not normal is a dip that does not recover, and the cause is almost always the redirect map: missing entries, or entries pointing at the home page instead of the matching page.

The integrations audit nobody does early enough

Products and URLs get attention. Integrations get discovered mid-migration, and that is where timelines slip.

Before you start, list every system that currently touches your WooCommerce store and decide what happens to each:

Payments. Which gateway, and is it available on Shopify in your country? Saved payment methods and stored cards do not transfer, and for subscription businesses this is a substantial piece of work rather than a detail.

Shipping and fulfilment. Carrier accounts, rate rules, any 3PL connection. Shopify's shipping model differs from WooCommerce plugins and complex rate logic often needs rebuilding rather than porting.

Subscriptions. If you run recurring orders, this is the single hardest part of any WooCommerce migration. Subscriptions carry billing relationships and payment tokens that generally cannot move. Scope this first, because it may change the whole plan.

Accounting and ERP. Whatever syncs orders to your finance system needs an equivalent, and the field mapping is rarely identical.

Email and marketing. Lists can move; automation logic and any behavioural triggers tied to WooCommerce events need rebuilding.

Reviews. Product reviews are valuable content and do not automatically follow. Most review platforms have an import path, but it needs doing deliberately and it is easy to lose years of reviews by forgetting.

What to do in the first fortnight after cutover

The migration is not finished at launch. The two weeks afterwards decide how much of your traffic you keep.

Daily: check Search Console coverage for new 404s and crawl errors. Every one is a redirect gap and each is cheap to fix now.

Daily for the first three days: place a real test order end to end, with a real payment method. Checkout issues are the most expensive category of post-migration bug and the least likely to be reported by customers, who simply leave.

Watch your analytics for traffic sources that vanished. A referral or email source dropping to zero usually means a link pattern nobody mapped.

Keep the old site accessible but not indexable for a short window if you can, so you have a reference while checking content came across correctly.

Resubmit your sitemap and let Google find the new structure rather than waiting.

What to ask an agency quoting the migration

Four questions separate a migration quote that includes the hard parts from one that quotes the product export.

1. "How do you build the redirect map, and does it include category and paginated URLs?" If the answer is a plugin with no mention of Search Console data, the map will be incomplete.
2. "What happens to URLs with no obvious match?" The right answer involves a judgement call per URL, or an honest 404. The wrong answer is "they go to the home page."
3. "How are you handling customer password resets?" A migration plan that has not thought about this has not thought about customers.
4. "Show me the rollback plan." For the first 48 hours there should be one.

If you are still choosing who does the work, what to look for in a Shopify development agency covers selection, and Shopify theme speed is worth reading before the build, because migration is the cheapest possible moment to get performance right.

The short version

Product data is the easy part. Budget your attention for URLs, variants, passwords and redirects.

Build the store before you migrate into it. Map every indexed URL individually and never let unmatched URLs fall to the home page. Write the password reset email before cutover. Migrate outside your peak season and watch Search Console daily for two weeks afterwards.

Expect a dip, plan for recovery in weeks, and resist changing things while it recovers. A migration done this way keeps the traffic you spent years earning. A migration done around a product export usually does not.

After the move, a monthly retainer is a reasonable way to catch the long tail of issues that surface in the months following a migration.