How to Replatform Your Ecommerce Store Without Losing SEO (2026)

Most store owners do not replatform for fun. You move because WooCommerce plugins keep breaking, Magento upgrades cost too much, Wix or Squarespace cannot handle your catalog, or you have outgrown a basic Shopify theme and want a faster headless storefront. The new platform is usually the easy part. The part that keeps owners awake is the question every one of them asks us on the first call: will I lose my Google traffic?

The honest answer is that a migration puts your rankings at risk, and a planned migration keeps almost all of that risk under control. This guide is the plan. It is written for US store owners moving to Shopify, Shopify Plus, BigCommerce or a headless Next.js storefront, but the same steps apply to any platform change.

Quick vocabulary, once. Replatforming means moving your store from one ecommerce system to another. A 301 redirect is a permanent forwarding rule that sends visitors and Google from an old page address to a new one. Staging is a private copy of the new store used for testing before launch. Structured data is code that tells search engines a page is a product, with a price, stock level and reviews. Search Consoleis Google's free dashboard for how your site shows up in search. That is the whole glossary.

Why rankings drop after a replatform

Google does not punish you for changing platforms. It ranks pages, and a migration changes the pages. When traffic falls after a move, it almost always comes down to one of these six causes. Each one is preventable.

1. Old URLs stop working. Your product and category pages earned rankings and backlinks at their old addresses. If those addresses show a 404 error after launch, that value is gone. This is the single biggest cause of post-migration traffic loss.
2. Redirects are the wrong type or go to the wrong place. A temporary 302 instead of a permanent 301, a chain of several redirects in a row, or thousands of pages all pointed at the homepage. Each one leaks ranking value.
3. Content does not come across. Product descriptions get shortened in the import, category intro text is dropped, the blog is left behind, or reviews stay in the old plugin. Less text on a page means less for Google to rank.
4. Titles, meta descriptions and headings reset. Many imports bring over product names but not the custom page titles and descriptions you wrote for search. The new platform fills in defaults, and click-through from Google falls.
5. Technical signals break. Missing product structured data, wrong canonical tags (the tag that tells Google which version of a page is the main one), a slower theme, or a headless storefront that builds pages only in the browser.
6. The staging block is left on. A noindex tag or robots.txt rule meant to hide the unfinished site is still there at launch, telling Google to drop the whole store.

What changes when you move from each platform

Every platform has its own URL pattern. When the pattern changes, every product and category URL changes with it, which is why the redirect map matters so much. Here is what typically changes on the most common US moves.

If your move is one of these, we have written platform-specific pages for WooCommerce to Shopify, Magento to Shopify, BigCommerce to Shopify Plus, Wix to Shopify and Squarespace to Shopify. Magento stores should also read our Magento to Shopify Plus migration checklist.

The seven-phase migration plan

This is the order we run migrations in. The first four phases happen before anyone touches your domain settings, and that is on purpose. Almost every SEO problem after launch traces back to something skipped here.

Phase 1: Benchmark what you have

Before anything changes, record where you stand. Export the last 12 months of pages and search queries from Search Console, your top landing pages from analytics, and your current rankings for the terms that bring in sales. Save it. After launch, this is the only way to tell a normal wobble from a real drop, and to see exactly which pages lost traffic.

Phase 2: Find every URL

Google recommends building your list of old URLs from sitemaps, server logs and analytics together (Google Search Central, site moves with URL changes). Add a full crawl of your current store and the list of pages that other websites link to. Each source catches pages the others miss: old product pages that still get visits from Pinterest, a discontinued collection with a strong backlink, a landing page from a past campaign.

Phase 3: Build the redirect map

The redirect map is a spreadsheet with one row per old URL and the single new URL it should point to. Match like with like: product to product, category to collection, blog post to blog post. If a product is gone for good, point it to the closest category, not the homepage. Mark which rows carry the most traffic and backlinks, so those get tested first. This spreadsheet is the most valuable document in the whole project.

Phase 4: Carry over content and metadata

Move the full product descriptions, category intro text, blog posts, image alt text, custom page titles and meta descriptions. Bring reviews across through the new review app, so the text and star ratings stay on the right products. Check that the new theme outputs product structured data (name, price, availability, reviews) and correct canonical tags. If you are also redesigning, keep the words close to the old site at launch and improve them later.

Phase 5: Test on staging

Import the redirects on the staging store and test them with a crawler. Every old URL should return one permanent 301 and land on a working page. No chains of two or three redirects, no loops, no 302s. Google explains that permanent redirects tell it the new page should become the main version, while temporary 302 and 307 redirects do not (Google Search Central, redirects and Google Search). Also run the key product and collection pages through Google's Rich Results Test and a speed test.

Phase 6: Launch day

Point the domain, remove the staging noindex, confirm robots.txt allows crawling, switch on the redirects, and submit the new XML sitemap in Search Console. Then spot-check your top 50 old URLs by hand. The full list is in the launch-day checklist below.

Phase 7: Monitor for 90 days

Watch Search Console, analytics and the 404 report daily for the first two weeks, then weekly. Fix broken redirects the day you find them. Google says a medium-sized site can take a few weeks or more to settle, so the job is not done at launch. This is where many agencies step away, and it is where most preventable losses happen.

Shopify redirect rules you need to know

Most US replatforming projects land on Shopify or Shopify Plus, and Shopify handles redirects in its own way. Three rules, straight from Shopify's help center (Shopify Help Center, URL redirects), shape how your redirect map gets built:

• Redirects only fire from broken URLs. A redirect works only when the old address shows a 404 on the new store. You cannot redirect away from a page that still exists, so old URLs that happen to match a live Shopify page need a different fix.
• There is a cap. Stores can hold up to 100,000 URL redirects, or 20,000,000 on Shopify Plus. That is plenty for most catalogs, but a Magento store with years of indexed filter URLs can get close, which is one reason to redirect filter pages by pattern and priority rather than one by one.
• Some paths are fixed. Products always live under /products/ and collections under /collections/. Your old URL structure cannot be copied exactly, so the goal is a clean one-to-one map, not identical addresses.

Redirects can be added one at a time or imported as a CSV file of old and new paths. Build the CSV from your redirect map, import it on staging first, and test it before launch.

12 things to check on launch day

Print this. Tick each one off before you announce the new store.

1. The staging noindex tag is removed from every template.
2. robots.txt allows crawling of products, collections and blog pages.
3. All redirects are imported and live on the production store.
4. Your top 50 old URLs by traffic each return a single 301 to the right page.
5. No redirect chains or loops (old URL to new URL in one step).
6. Canonical tags point to the live domain, not the staging address.
7. Product structured data passes Google's Rich Results Test.
8. Page titles and meta descriptions on top pages match what you approved.
9. The new XML sitemap is submitted in Search Console and the old one removed.
10. Analytics and conversion tracking fire on product, cart and checkout pages.
11. A test order goes through checkout, payment and the confirmation email.
12. The customer account invite email is ready, if accounts moved across.

The first 90 days after launch

Some movement is normal. Google says to expect ranking fluctuations while it recrawls and reindexes the site, and to keep redirects in place for at least a year so it can move all the signals from old URLs to new ones. What matters is the direction of travel.

If clicks are still sliding after two or three months, do not wait it out. Pull the list of pages that lost the most traffic against your benchmark, and check each one for a missing redirect, a noindex tag, thin text or a changed title. The cause is almost always on that list. Our ecommerce SEO team runs exactly this review for stores that migrated with another provider.

What drives the cost and timeline of a migration

A migration is priced on data and change, not on how the new site looks. Two stores with the same design can be very different projects. These are the things that move the scope:

On timing, here is what our builds take. A platform store with a custom theme takes 3 to 5 weeks. An advanced store with subscriptions, B2B pricing or a larger migration takes 5 to 8 weeks. A headless Next.js storefront or custom platform runs 8 to 14 weeks. The migration and SEO work sit inside those timelines, not on top of them.

We do not publish a fixed migration price, because the drivers above change the scope too much for one number to be honest. We quote after a short discovery call. If you want to understand the wider cost picture first, read our guides to ecommerce website cost and Shopify development cost.

What to ask a migration agency before you hire them

Plenty of agencies can build a new store. Fewer can move an old one without losing its traffic. These questions separate the two quickly.

For the wider hiring checklist, see our guide on how to choose an ecommerce development agency.

How we run migrations at FactoryJet

We are a registered Shopify Partner and we design, build and support stores on Shopify, Shopify Plus, BigCommerce, WooCommerce and headless Next.js. On a migration, we build the redirect map before we touch your domain, carry over your content and structured data, test every redirect on staging, and handle launch day with you. Then we stay on after launch to watch Search Console and fix what comes up, because the weeks after go-live are when a migration either holds its rankings or loses them. You own the store, the code and the data from day one. See the full scope on our replatforming and migration page.