Migrate WooCommerce to Shopify Without Losing Traffic

Most guides to migrating WooCommerce to Shopify are written for someone launching their first store. This one is not. It assumes you already have a trading business, real order volume, integrations that finance depends on, and search rankings you cannot afford to lose. At that size the platform comparison is the easy part. The hard part is moving without breaking the things that are currently working.

We have built and maintained WooCommerce stores, including one that has processed over 150,000 orders and more than £5m in revenue and has almost never missed a beat. We have also run the migrations off them. So this is not a case for Shopify being better than WooCommerce. It is a description of when the move is worth it, what it costs you if you get it wrong, and the checklist we work through before touching anything.

When migrating is the right call, and when it is not

WooCommerce is not the problem in most of the stores we are asked to look at. The problem is usually the accumulated cost of decisions made three years ago by a developer who has since left.

The move tends to be worth it when:

• Your plugin stack has become the product. You are running twenty or more active plugins, several of them doing jobs that overlap, and nobody on the team can say what would break if one were removed. Every WordPress core update is now a risk event rather than routine maintenance.
• You are carrying infrastructure you did not want. Someone on your team owns uptime, PCI scope, patching and backups. If that person is your marketing lead, or an agency you pay hourly to keep the lights on, you are paying for infrastructure with attention rather than money.
• Checkout is the constraint. This is the honest structural difference. Shop Pay and Shopify's checkout are used across every store on the platform, so a returning buyer often arrives already recognised. You cannot replicate that on your own domain, whatever you do to your checkout.
• You are hitting operational ceilings at peak. Traffic spikes cause the conversation about server sizing rather than about merchandising.

The move is usually not worth it when:

• Your store is fast, stable, maintained, and your team knows it. A well-run WooCommerce build serving a large catalogue is a perfectly good asset. Replatforming it is expensive theatre.
• You need deep content and commerce in one system, and the content side is doing genuine work. WordPress is still better at editorial.
• Your margins depend on unusual logic, such as complex B2B pricing or fulfilment rules built directly into the database, and nobody has scoped what those become on Shopify. Scope them first. The answer changes the budget.
• You are mid-peak. Nobody should be migrating in the eight weeks before their biggest trading period.

What actually goes wrong

Four things account for nearly every migration that damages a business. None of them are surprises, which is what makes them frustrating.

Search traffic falls and does not come back. This is the expensive one. It is almost always caused by incomplete redirect mapping rather than by Shopify. Shopify enforces URL prefixes: products live under /products/, collections under /collections/, blog posts under /blogs/. If your WooCommerce store used /shop/product-name or a flat /product-name, every single one of those URLs changes. A redirect map is not optional and it is not something to do the week of launch.

Customer passwords do not transfer. They are hashed and there is no route to move them. Your customers will need to reset. If you have not planned the communication for this, your support inbox becomes the launch story.

Historic orders arrive as records, not as history. Orders can be imported, but imported orders do not behave like native ones. Refunds against them, reporting continuity and the way returns tooling reads them all need checking before you decide how far back to import.

A subscription or integration quietly stops. Subscriptions, ERP connections, accounting sync and loyalty balances are the four that catch people. Each one needs an owner and a test, not an assumption.

The pre-migration checklist

This is the work that happens before anyone builds anything. If you do nothing else from this guide, do this. It is also the section worth keeping open during the project, because most migration problems are audit failures rather than build failures.

Catalogue and data

• Export a full product list, including variants, and get an exact count. Reconcile that number after import, not by eye.
• Identify products with logic behind them: bundles, subscriptions, made-to-order, personalisation, tiered or customer-specific pricing. Each needs a named Shopify equivalent before build, whether native, an app, or custom.
• Decide how far back you are importing orders, and confirm with finance and support rather than deciding it technically.
• Export customers with their marketing consent state intact. Consent does not survive a careless CSV, and losing it is a compliance problem as well as a revenue one.
• List every product image and check where they are actually hosted. Images served from a plugin or a CDN path frequently do not come along.

Search and URLs

• Pull every crawled URL from Google Search Console, not just what is in your sitemap. The sitemap shows what you meant to publish. Search Console shows what Google actually knows about, including URLs from site versions you have forgotten.
• Export your current sitemap and keep it. After launch it is the reference you test redirects against.
• Record current rankings and the landing pages that earn them, before you change anything. Without that snapshot you cannot tell a migration problem from an ordinary fluctuation, and you will spend the first month arguing about it.
• Build the redirect map as a spreadsheet of old URL to new URL, covering products, collections, content, and any category or tag archives that hold rankings.
• Decide what happens to URLs with no equivalent. A redirect to the most relevant category is right. A blanket redirect of everything to the homepage is the single most common way to lose the traffic.

Integrations and operations

• List every third-party system touching the store: payments, shipping, accounting, ERP, email, reviews, loyalty, analytics, ad platforms. For each, record who owns it and what replaces it.
• Confirm your payment provider supports Shopify in your market. In the UAE this is worth checking early, because Shopify Payments availability, local card acquiring, cash on delivery handling and the buy-now-pay-later providers your customers expect are not the same conversation as they are in the UK or US.
• Check your tax setup properly, including VAT treatment and invoicing requirements.
• Rebuild your analytics and ad tracking as a deliberate task. Conversion tracking breaking on launch day is common, and it hides for weeks because the site looks fine.

People

• Name one person who signs off go-live.
• Write the customer email about password resets before launch week.
• Book training for whoever runs the store day to day. The admin is different, and staff working around an unfamiliar system is a slow, invisible cost.

The migration itself

Build on a development store first. You do not need to point your domain anywhere. Shopify gives you a myshopify.com address to build and test against, and a partner agency can create the development store inside their account.

Move products in the order that lets you check them. Small representative batches first, covering each awkward product type, then the bulk. The options are manual entry, CSV import against Shopify's template, or a third-party import app. CSV is usually the backbone, and the work is in reshaping WooCommerce's export into Shopify's format, which is where most of the unglamorous effort in a migration actually sits.

Treat customers and orders as sensitive. Map orders to customer profiles correctly and verify a sample by hand. On accounts, Shopify offers classic accounts, which are the familiar email and password, and new customer accounts, which log in with a code sent by email. New customer accounts sidestep the password problem entirely, because there was never a password to migrate. If you are on classic accounts, the reset email is mandatory.

Decide early whether you need a sync. For a store doing meaningful daily volume, the gap between building the new site and going live is a problem: products change, customers register, orders arrive. We have built migrations that hold both systems in step, pushing new products, customers and orders from the live WooCommerce store into Shopify through the API while the new store is being built. It is not necessary for every project. For a store taking orders continuously it is the difference between a launch and a reconciliation exercise.

Protecting your rankings

This is the part that justifies the rest of the checklist, so it gets its own section.

Change as little as possible at once. The temptation during a replatform is to redesign, rewrite, restructure the navigation and change the URL taxonomy in the same release. Then traffic moves and you have no way to attribute it. Move the store first, with URL changes limited to the ones Shopify's structure forces on you. Improve afterwards, deliberately, measuring as you go.

Then, on launch day and the days after:

• Load the redirect map into Shopify before the domain switches, not after.
• Submit the new sitemap in Search Console, and keep the old sitemap to test against. Work through it and confirm each URL resolves to the right destination rather than to a 404 or a homepage redirect.
• Watch Search Console coverage daily for the first fortnight. You are looking for a rise in 404s or in pages marked crawled but not indexed. Both are recoverable if you catch them early.
• Expect a dip. A short period of movement while Google recrawls and reassigns signals is normal even on a well-executed migration. What is not normal is a decline that continues past a few weeks, and that is your signal to go back to the redirect map.
• Keep the old store accessible to your team, not to the public. You will want to check something against it, usually within the first week.

Launch and the first thirty days

Adding the domain and updating DNS is genuinely the easy step, and with a provider like Cloudflare the switch is quick. The work sits either side of it.

Run acceptance testing twice: once on the development store, and again on the production domain after the switch. The second pass matters because payment providers, tracking and anything domain-aware behave differently on the real domain. Put a real order through with a real card, then refund it.

In the first thirty days, the useful questions are narrow. Is search traffic tracking as expected against the snapshot you took, or drifting? Are conversion tracking and revenue reporting agreeing with Shopify's own numbers? Are support tickets clustered around one thing, usually account access? Is anything in the ops chain, such as accounting or fulfilment, silently not receiving orders?

Write down the standard operating procedures while the knowledge is fresh, and make sure more than one person holds them. The most common post-migration failure is not technical. It is that everything lives in one person's head.

What it costs and how long it takes

The honest answer is that it depends on the catalogue, the integrations and how much of your business logic is custom, which is why the pre-migration audit exists. A store with a clean catalogue, standard payments and no subscriptions is a very different project from one with tiered B2B pricing and an ERP connection.

Two things move the number more than anything else: the number of products with non-standard logic behind them, and the number of integrations that need rebuilding rather than reinstalling. Both are known at the end of the audit, which is why we scope from an audit rather than from a page count.

If you want to model the ongoing platform cost rather than the project cost, our Shopify fee calculator works through plan fees and transaction rates by market.

Getting help with it

If you are weighing this up for a store that is already trading, the audit is the part worth doing properly, and it is worth doing before you have committed to a date. We do WooCommerce and Magento migrations for brands in the UAE and further afield, including the synchronised builds described above. You can see the process, the timeline and what carries across on our Shopify migration page.