Ecommerce Replatforming: How to Migrate Without Losing Revenue
Ecommerce replatforming puts years of rankings and revenue at risk. Learn how established stores plan the move, map redirects, and protect traffic at launch.
Zivojin SreckovicFounder and CEO
Ecommerce replatforming means moving your store from one commerce platform to another, such as Magento or WooCommerce to Shopify, or a Shopify theme to a headless frontend. You keep your rankings and revenue through the move by listing every URL that earns traffic, redirecting each one with a 301 to its closest match on the new site, launching in a quiet sales period, and watching Search Console for the first 60 days. Google's site move documentation confirms that 301 and other permanent redirects don't cause a loss in PageRank, so the traffic stores lose in a migration comes from how the move gets planned and executed.
For a store with years of organic traffic behind it, the stakes are concrete. A Search Engine Journal study of 892 domain migrations found that sites took 523 days on average to reach their old traffic levels, and 17% still hadn't recovered after 1,000 days. The fastest site recovered in 19 days.
The distance between 19 days and never comes down to preparation. Below is the process we follow when we move established stores onto new platforms, from the first URL export to the checks we run in the weeks after launch.

Key Takeaways
- Ecommerce replatforming moves your products, customers, order history and URLs to a new commerce platform.
- Google confirms 301 redirects don't lose PageRank, so traffic losses come from unmapped URLs and execution mistakes.
- Map every old URL to its closest match on the new site. Redirecting old pages to the homepage can count as a soft 404.
- Change one thing at a time, launch in a low-traffic period and keep redirects live for at least a year.
- A headless frontend can keep your existing URL structure, which cuts the number of redirects you need.
What Is Ecommerce Replatforming?
Ecommerce replatforming is the process of moving an online store's products, customers, order history, content and URLs from one commerce platform to another while keeping its search visibility and sales intact.
Teams often confuse it with two smaller projects. A redesign changes how the store looks and keeps the platform and URLs. A domain change keeps the platform and moves the address. A replatform touches the platform, the data and, in most projects, the URLs at the same time, which makes it the riskiest of the three. Shopify's enterprise replatforming guide draws the same line: migration moves data, URLs or infrastructure, while replatforming changes how the business runs.
The most common routes we see:
- Magento or Adobe Commerce to Shopify or Shopify Plus
- WooCommerce to Shopify
- Salesforce Commerce Cloud or a custom build to Shopify Plus
- A Shopify theme to a headless Shopify frontend built with Next.js

Signs Your Store Has Outgrown Its Platform
A replatform costs months of work, so the reason for it should be specific. These patterns justify the move for stores already doing serious revenue.
Your app stack slows the store down. Every review widget, upsell tool and bundle app loads its own scripts. Once your Core Web Vitals fail on mobile and the theme can't shed the weight, the platform itself has become the bottleneck.
Developers spend more time on upkeep than on features. Magento upgrades, security patches and plugin conflicts can eat a full development budget before anyone ships something customers notice.
Checkout and pricing logic have outgrown the platform. B2B price lists, subscriptions, custom checkout steps and loyalty rules often end up held together by workarounds.
New markets mean new storefronts. Selling in several languages and currencies from one catalog gets messy on platforms that weren't built for it.
If a slow theme is the main complaint, fixing the theme costs far less than moving platforms. If your peak season starts within three months, wait until it ends. Our breakdown of what an ecommerce website costs covers how migration shows up as its own line item in a quote.
Where Stores Lose Traffic During a Migration

Most traffic loss after a replatform traces back to a short list of avoidable mistakes, several of which Google's own site move documentation names.
Unmapped URLs
Old product, collection and blog URLs that return a 404 on the new site lose their ranking signals and the backlinks pointing at them. The losses hide in the long tail: discontinued products that still earn links, filter pages that rank for specific searches, and old campaign pages that still appear in emails and ads.
Redirecting everything to the homepage
Pointing hundreds of old URLs at the homepage feels like a safe fallback. Google advises against it, because a redirect to an irrelevant page confuses shoppers and Google may treat it as a soft 404. Send a discontinued product to its parent collection or its closest replacement instead.
Launching with staging blocks still in place
Developers often add a noindex tag or a robots.txt block to keep the staging site out of Google. Google lists leftover noindex and robots.txt rules among the most common site move errors. One forgotten line can drop the whole store out of search.
Changing everything at once
Google recommends changing one thing at a time. If you move platforms, rewrite product descriptions and restructure collections in the same week, you can't tell which change caused a ranking drop. Keep titles, descriptions and collection copy the same at launch, and improve them once traffic settles.
Losing what Google read on the old pages
Product structured data with price, availability and reviews, title tags, meta descriptions, canonical tags, hreflang and image alt text all need to carry over. Images count too. Google recommends including image and video URLs in your mapping, since they may already receive traffic from search.
How to Replatform an Ecommerce Store Step by Step

The order of these steps matters more than the tools you use. Skipping the first two is the most expensive shortcut in the project.
1. Record a baseline before you touch anything
Export at least 12 months of Search Console data: pages, queries, clicks and impressions. Pull revenue by landing page from your analytics, and record Core Web Vitals for each page template. Save rankings for the pages that bring in the most revenue.
Without this baseline, you can't tell a normal post-launch dip from a real loss, or a seasonal swing from migration damage.
2. Build a complete URL inventory
A crawl of the live site misses URLs that no internal link points to anymore. Google suggests combining several sources, and we use all of them:
- XML sitemaps from the current platform
- Server logs and analytics landing pages
- Search Console's links report and a backlink tool, to catch URLs other sites link to
- A full crawl of the live store
- Image, PDF and video URLs
The final list often ends up several times larger than your product count once collections, filters, paginated pages, images and old campaign pages join it.
3. Map every old URL to its new home
Put the map in a spreadsheet with one row per old URL: old address, new address, traffic, revenue and status. Sort by revenue so the pages that pay the bills get checked first.
A few rules keep the map clean:
- Products go to the same product on the new site
- Discontinued products go to their parent collection or closest replacement
- Merged collections go to the new combined collection
- Pages with no equivalent return a 404 or 410, which Google accepts for removed content
Use permanent server-side redirects (301 or 308), the type Google recommends for site moves.
4. Know your new platform's URL rules
Your new platform's URL rules decide how many redirects you need. Shopify fixes the first part of every path: products live under /products/, collections under /collections/ and pages under /pages/. You can edit the handle at the end, but not the structure.
A store moving from Magento URLs like /mens-running-shoes.html to Shopify will change every product and category address. Shopify's URL redirect tool handles the redirects in bulk, but every one of them needs to be correct in the map first.
5. Migrate the data, then check it
Products and variants with their SKUs, images and custom fields move first. Customers, order history, reviews, gift card balances and subscriptions follow. Support, returns, accounting and loyalty programs all depend on that order history.
Customer passwords don't transfer between platforms, since each one encrypts them its own way. Customers have to reactivate their accounts on the new store. Plan an activation email before launch and send it through your email marketing automation setup, so returning buyers aren't greeted by a failed login.
Once the data is in, compare record counts against the old platform and spot-check a sample of products by hand: price, variants, stock, images and descriptions.
6. Rebuild integrations and tracking
List every system the old store talks to: ERP, inventory, shipping, email, reviews, analytics and ad pixels. Each one needs reconnecting and testing on the new platform.
Keep product IDs in your Google Merchant Center feed the same where you can, since Shopping campaign history attaches to them.
7. Test on staging, then launch in a quiet window
Run your full redirect list against the staging site. Every old URL should reach a live page in one hop, with no chains. Then place real test orders with every payment method, shipping zone, tax setup and discount code you use.
Google recommends timing a move for a low-traffic period. For most stores, that rules out Q4, major sales events and product drops. On launch day, remove staging blocks, activate redirects and submit the new sitemap in Search Console. Submit a Change of Address request only if your domain changes as well.
The First 60 Days After Launch

Google says to expect temporary ranking fluctuations while it recrawls the store. A medium-sized site can take a few weeks before the new URLs replace the old ones in results, and large catalogs take longer.
Check daily for the first two weeks:
- 404 and redirect errors in Search Console and server logs
- Checkout conversion rate and order volume against your baseline
- Payment, shipping and tax errors reported by customers or support
Check weekly through day 60:
- Indexed pages: the old sitemap's count should fall as the new one rises
- Clicks and impressions for your top revenue pages
- Core Web Vitals for each page template
Compare by template, not just sitewide. A stable total can hide a sharp drop on collection pages that branded homepage traffic covers up. A short dip followed by gradual recovery is normal. A fall that keeps sliding past the second or third week, or top revenue pages vanishing from results, points to a broken redirect pattern or blocked indexing.
Keep redirects live for at least a year, which is Google's minimum recommendation, and longer if old links still send shoppers. Update internal links, ad destinations, email templates and social profiles to the new URLs so the redirects carry less weight over time. Hold back design and copy changes until traffic has settled.
Replatforming to Headless Without Changing Your URLs
Most of the risk in this guide comes from URLs changing. A headless setup removes much of it.
On a headless store, Shopify runs products, inventory and checkout while a Next.js frontend controls routing. That routing is custom code, so we can rebuild the storefront on the old URL structure even when the backend moves to Shopify. A product at /mens-running-shoes.html can keep that exact address.
Fewer changed URLs means fewer redirects to map, test and maintain, and fewer places for rankings to leak. You still get the speed gains of a rebuilt frontend, which feed into search rankings and conversion rates once the new store is live.
Keeping old URLs isn't always the right call. If the current structure carries session IDs, duplicate paths or deep folder nesting, a planned change can pay off. Google's guidance on ecommerce URL structure and our guide on planning a website structure help you decide pattern by pattern.
Questions to Ask Before You Hire a Migration Partner
- Is the redirect map in the quote, and do I keep it after launch?
- How do you build the URL inventory? A crawl on its own misses linked and logged URLs.
- How will you handle customer accounts and order history?
- What do you monitor after launch, and for how long?
- What is the rollback plan if checkout fails on launch day?
- Will you change content or design at the same time as the platform?
A partner who prices the build but gives vague answers on the redirect map has left the riskiest part of the project out of scope.
Protecting Revenue Through the Move
A replatform can leave your store faster and ready for new markets, or cost a year of organic growth. Stores that inventory every URL, redirect each one with care, change one thing at a time and watch the weeks after launch keep their traffic.
If your current platform is holding the store back, the redirect map and the baseline are where the work starts, long before design. We build headless ecommerce stores on Shopify and Next.js and can keep your existing URLs intact where it makes sense. Recent builds are in our portfolio. Tell us about your store and we'll reply within one business day with what a migration would involve for your catalog and traffic.
Frequently Asked Questions
How long does it take to recover traffic after an ecommerce migration?
A well-planned migration tends to stabilize within a few weeks, and Google notes that larger sites take longer to recrawl. Badly planned moves can take far longer: in Search Engine Journal's study of 892 domain migrations, the average recovery took 523 days, and 17% of sites hadn't recovered after 1,000 days.
Do customer passwords transfer to a new ecommerce platform?
No. Each platform encrypts passwords its own way, so they can't move between systems. Customer names, addresses and order history can migrate, and customers reactivate their accounts on the new store through an invite or password reset email.
When is the best time to replatform an ecommerce store?
Launch during your lowest-traffic period, away from Q4, major sales events and product drops. Leave at least a few weeks before your next peak season so you can fix issues before traffic and revenue climb.
Does replatforming hurt SEO?
Replatforming doesn't hurt SEO by itself. Google states that permanent redirects don't lose PageRank. Rankings drop when old URLs go unmapped, redirects point to irrelevant pages, staging blocks stay live, or content changes alongside the platform.

Zivojin Sreckovic · Founder and CEO
I help businesses grow with fast, high-converting websites and smart automation. From clean, responsive web design to AI chatbots and backend automations, I build systems that save time, improve user experience, and scale as you do.
View full profile