The Shopify migration playbook: when to leave WordPress or WooCommerce

The real trigger for a Shopify migration is simple: when your team spends more hours maintaining the store than improving it, it is time to move, and the sooner the better. If your WooCommerce build is stable, cheap to run, and only bothers you on plugin update day, you can probably wait another year and spend that money elsewhere.

That is the honest answer, and it annoys people on both sides of the platform debate. WooCommerce is genuinely good software. Shopify is genuinely good software. The migration question comes down to the total cost of keeping your current store alive, and whether that cost is growing.

We build on both platforms for e-commerce clients across Tampa and nationally, so we do not have a horse in this race. What follows is the checklist we walk through before recommending a move, and the parts of a migration that quietly break when nobody owns them.

What are the signals it’s time to leave WooCommerce?

The clearest signal is maintenance debt: you are afraid to update plugins, checkout breaks after updates, or your developer bills more for keeping the site running than for improving it. The second signal is that your store’s problems are infrastructure problems, things like slow pages, security patches, and hosting tuning, rather than merchandising problems.

Break that into specifics. You are a migration candidate if several of these sound familiar:

• Plugin updates get postponed because the last one broke something, so you are now running known-vulnerable versions.
• Checkout has failed silently at least once, and you found out from a customer instead of a monitor.
• Page speed work has become a recurring line item. You keep paying to re-optimize the same site.
• Your hosting bill climbs every time you run a promotion, because traffic spikes take the site down otherwise.
• Simple changes, like adding a product option or editing a shipping rule, require a developer.
• You have a plugin stack of 25 or more, and nobody can say what half of them do.

These symptoms usually trace back to a site built years ago by someone who is gone, with layers accumulated since. Shopify removes the infrastructure category entirely: hosting, security, PCI compliance, and checkout uptime become Shopify’s problem instead of yours. What you give up is the deep customizability of open source and you take on monthly platform and app fees. For most merchants past a certain complexity, that trade is worth it. For some it is not, and a good agency should be willing to tell you which one you are.

What does a migration need to protect?

Two things above everything else: your search rankings and your email deliverability. Products, customers, and orders are data transfers, and data transfers are checkable. Rankings and deliverability are earned assets that can quietly evaporate during a move, and rebuilding either takes months.

Here is what protecting them actually involves.

SEO. Your WooCommerce URLs will not match your Shopify URLs. Shopify forces its own structure, so /shop/blue-widget becomes /products/blue-widget, and every category, tag, and blog URL changes too. Every old URL needs a 301 redirect to its new equivalent. Pointing everything at the homepage throws away each page’s ranking equity; the map has to be one-to-one. Before migration day you should have a full crawl of the old site, a spreadsheet mapping every indexed URL to its destination, and your redirects loaded and tested. Carry over title tags, meta descriptions, and image alt text rather than letting the new theme regenerate them. Then watch Google Search Console for weeks afterward and fix the 404s that surface. A migration handled this way usually holds its rankings. A migration without a redirect map can lose years of search equity in a single afternoon.

Email deliverability. This is the one almost every migration checklist skips. Your store sends transactional email, and your marketing platform sends campaigns, and both depend on DNS records (SPF, DKIM, DMARC) that authenticate your domain. A platform move changes what sends mail on your behalf. If those records are not updated and verified as part of the migration, your receipts and campaigns start failing authentication, inbox providers lose trust in your domain, and open rates fall off a cliff while your dashboard says everything is fine.

We learned to treat this as a first-class migration task from experience. On one Shopify rebuild for a coffee brand we work with, part of the cleanup was fixing email authentication that had left their sending domain blacklisted. Their campaigns were going out; they just were not arriving. Repairing the DNS records and rebuilding sender reputation was as important to revenue as anything visual in the redesign.

What order should a migration actually run in?

Build and test the new store completely on a preview URL before touching DNS, then cut over in a planned window with redirects live from minute one. The store your customers see should switch once, cleanly. Anything that gets figured out live is a mistake you chose in advance.

The sequence we run:

1. Crawl and inventory. Export every URL, product, customer, order, discount code, and gift card. Screenshot the analytics baseline so you can prove what changed later.
2. Build in parallel. The new Shopify store gets built and populated while the old store keeps selling. Nothing is rushed because nothing is down.
3. Map redirects. Every indexed URL gets a destination. This is tedious. Do it anyway.
4. Reconnect the stack. Email platform, reviews app, accounting, shipping, ads pixels, and analytics all need rewiring. This is where integrations work pays for itself, because a missed connection here means silent data loss for weeks.
5. Verify email authentication. SPF, DKIM, and DMARC updated for every service that sends from your domain, then test sends to seed inboxes at Gmail, Outlook, and Yahoo.
6. Cut over in a quiet window. For our Tampa retail and coffee clients that means a weekday early morning, never a weekend or a promo period. Freeze orders briefly, sync final data, flip DNS, confirm redirects, place a real test order with a real card.
7. Watch for 30 days. Search Console for crawl errors, deliverability dashboards for authentication failures, and revenue against the baseline you screenshotted.

Handled this way, a migration is a foundation for growth rather than a recovery project. One of our e-commerce clients saw revenue up 42%, 4 months after the Shopify redesign, year over year. That result came from the redesign and CRO work the migration made possible, and none of it happens if the move itself loses rankings or burns the sending domain.

Questions we hear about migrations

How long does a WooCommerce to Shopify migration take? Most small and mid-size stores take one to two months from kickoff to cutover, driven more by integration count than catalog size; a store with 200 products and 12 connected services takes longer than one with 5,000 products and 2.

Will I lose my Google rankings when I move to Shopify? Not if every indexed URL gets a one-to-one 301 redirect and your metadata carries over. Expect some ranking movement for a few weeks while Google recrawls, then recovery. Ranking losses almost always trace back to missing redirects rather than the platform.

Do my customers have to reset their passwords? Yes. Password hashes cannot be exported from WooCommerce into Shopify, so returning customers set a new password on first login. Plan a short email letting them know, and make sure that email is sent from your newly authenticated domain.

Can I keep my WordPress blog? Yes, and it is often worth doing. You can run the store on Shopify and keep WordPress for content on a subdomain or subdirectory, or migrate the posts into Shopify’s blog. The right call depends on how much organic traffic the blog carries; check that before deciding, not after.