How To Move Your Store To A New Platform Without Losing Sales Or Rankings

Moving to a new platform copies your store's records into a fresh database, and the pages and settings around them get rebuilt. An ecommerce migration runs smoothly when two spreadsheets exist before the first import. One lists the old URLs and the other lists the old database's fields.

After that the data moves at least twice. A rehearsal goes onto a hidden store first, and a catch-up then brings across the orders taken in the meantime.

For the URL list, my first stop is GA4, where I check which pages bring traffic and give each a new page matching the search it ranked for. Next come the pages that feed those with links, because a URL with plenty of backlinks but little traffic is often overlooked. So export your top landing pages from GA4 and Search Console before the first import.

What A Migration Carries Across And What It Rebuilds

A migration carries records from one database to another. Your theme and your checkout code belong to the old platform and stay with it, along with most of the SEO settings you've built up over the years. Sorting each part of your store onto one side of that line is the first job.

The Import Order For Products, Customers And Orders

Products go in first, then customers, then orders. Every order points at a product and a customer, so both have to exist on the new store before an order can land and attach to them.

On Shopify, the free importer handles products and customers but stops short of order history, which has to arrive through a paid migration tool or the API. The better tools write each one with its original dates, order numbers and fulfilment status, so a returning customer can still see what they bought last year.

Once it's there, use that history for customer service, such as a returns query or a warranty claim on something bought two years ago. Don't expect the totals to match your old reports to the penny. WooCommerce accepts order maths and invalid contact details that Shopify rejects at import. Keep your historical revenue reporting in an export from the old system.

Passwords, Lifetime Totals And SEO Plugin Fields Left Behind

A store moving onto Shopify now skips the password problem entirely. Shopify's newer customer accounts have no password field at all, because shoppers type their email address and get a one-time code to sign in.

Your job shifts from forcing password resets to one clear launch email saying the store has moved and how sign-in now works.

WooCommerce stores get caught out by the SEO fields in particular, and WooCommerce's own documentation confirms that the built-in product CSV importer cannot add or update alt text on product images. After the first import, sort the new store's products by empty search description and every blank shows up in a minute.

Rebuilding The Checkout, The Theme And Each App

No front-end code survives a platform change. Your theme gets rebuilt from scratch on the new platform. Custom checkout code written for your old platform has nowhere to run once you're on Shopify, and any changes you still want come back as checkout extensions.

Apps follow the same rule: each one is replaced or dropped. List every plugin on the old store with the job it does and the revenue it touches, then rebuild only the ones you'd pay for again today.

I treat a migration as the cheapest chance a store gets to cut app bloat. Every app adds scripts to every page, and plenty of slow new stores are carrying leftovers nobody needed. For a shorter list to start from, our guide to Shopify apps covers the few worth installing.

Settle The Maps, The Baseline And The Import Method Before Any Product Moves

Four decisions come before the first import, and every later step gets checked against them. Change the URL map after the rehearsal and every redirect check has to run again.

Draw The URL Map And The Data Map From The Old Store

A URL map is a spreadsheet with every old URL that earns clicks or links in one column and its new address in the next. Pull your pages from the Performance report in Google Search Console over the longest date range it offers, add the pages with backlinks from Ahrefs, and you have the list worth protecting.

Moving to Shopify changes almost all of them, because Shopify fixes products under /products/ and collections under /collections/ and lets you change neither folder.

A data map does the same job for information. List every field your old store holds, from short descriptions to plugin data. Beside each one, write where it will live on the new platform: a standard field, a metafield or an export you keep.

Any column the importer doesn't recognise is skipped by default, which is why every field needs a row on this sheet before the rehearsal.

Check The Platform Is What Is Costing You Sales

A move is worth its disruption when the platform's code, its app bloat or its limits are costing sales. When they aren't, a new theme is the cheaper fix for a store that only looks dated.

Magento stores often have a deadline on top, because several older Magento 2 versions have already come to the end of their extended support. Shopify and WooCommerce are the two platforms I recommend, and our post on choosing the platform goes through the decisions you can't undo later.

Take A 90-Day Revenue Baseline Before Work Starts

Export the last three months of organic revenue, organic sessions, conversion rate and indexed pages from your analytics and Search Console before anyone touches the store. Pull the same window from last year as well. A seasonal dip in the weeks after launch then shows up as seasonal instead of looking like a migration problem.

Organic revenue is the number I judge a move on, and rankings tell you where to look when it falls.

Pick The Import Method By What Has To Move

A clean catalogue moves well by CSV. Order history and anything stored in custom fields need a migration app or the API. Products with more than three options need one too, since Shopify drops the options on any product that comes in with a fourth.

Fix your option structure before the rehearsal.

Changing option values on a later re-import creates new variant IDs, and review widgets or shopping feeds tied to the old IDs stop matching their products.

Import Twice, Once To Rehearse And Once To Catch Up

Whatever you import in week one of an ecommerce migration is out of date by launch day, because the old store keeps trading while the new one is built. Plan for the data to move at least twice: a full rehearsal you can throw away, then a small final import of what changed since.

Rehearse The Import On A Store Nobody Can See

Run the full import into a development store that customers can't reach. Export the same tables from both stores once it's in and compare four things: record counts, the sum of paid order values, customer emails and SKUs.

Finding a mismatch now costs an afternoon, and an export that stopped short of your full order history only shows up when you compare.

Check a sample of awkward orders by hand, starting with partial refunds and subscriptions. Place test orders for a refund, a cancellation and a failed payment as well.

When anything is off, wipe the development store and run the import again.

Call the rehearsal finished when two runs in a row match.

Freeze Briefly, Import The Delta, Then Switch The Domain

For the final day, freeze stock edits and new products on the old store. Import only the records created or changed since the rehearsal, with overwrite switched off for products you've already edited on the new store, so your fixes survive.

Switch off notifications, fulfilment connections and marketing automations before the old orders arrive. Otherwise your warehouse app may try to ship a two-year-old parcel and customers may get a thank-you email for it.

Lower your domain's DNS TTL to five minutes the day before. The switch then spreads quickly and downtime runs to hours. Keep the old store on a read-only subdomain for a few months as your reference.

Keeping Search Rankings Through Launch Day And The Month After

A shopper clicking last month's Google result for an old URL should land on the matching product, so load the URL map as redirects before the domain moves. Our migration SEO checklist tests each one. Visits that dip after launch usually come back within a few weeks when every row is right, and what changing platform does to search traffic explains why.

Get The Search Side Of Your Migration Checked Before Launch

Your URL map is cheapest to fix while it is still a spreadsheet. A wrong row costs nothing to change before the import date and costs rankings once it is live.

Where the mapping and redirects need doing for you, our technical SEO work covers the search side of your ecommerce migration. That includes the URL map and the redirect plan for your target platform. Replatforming stores get that groundwork from us as an SEO agency for Shopify merchants moving their catalogue, whatever the destination.

Before you move, get a free SEO audit of your store and keep a record of where you stand. The two-page PDF comes the same day. It charts the last twelve months of organic traffic and lists your top keywords with their positions, so you have a baseline to judge the launch weeks against.