Website migration is a high-risk SEO and revenue operation, especially for eCommerce stores where organic traffic directly impacts sales.
Even if your domain stays the same, a platform migration can quietly break what already works. URLs change, internal links shift, metadata disappears, and search engines start reevaluating your pages.
This guide is a practical checklist for migrating an eCommerce website to a new platform while preserving organic traffic. Keeping your existing SEO value intact, avoiding common pitfalls, and making sure nothing critical gets lost during the transition.
If you approach migration as a structured process and not a redesign, you can move to a new platform without sacrificing performance.
Prerequisites
Before going into the checklist, it is important to clearly define the scenario. Website migration can mean very different things, and the risks depend on what exactly is changing.
What this checklist assumes
This guide is built for a specific type of migration:
The domain remains the same
You are moving to a different eCommerce platform
Your product catalog largely stays the same
Some URL changes may happen due to platform differences
This is a common situation when moving between platforms like Magento, Shopify, WooCommerce, or a custom solution.
This checklist does not cover migrations that involve a domain change.
What can go wrong
A common expectation is that keeping the same domain helps preserve SEO performance during migration. In reality, search engines rely on much more than just the domain name.
Traffic can drop even without a domain change if:
URLs change without proper redirects
Internal linking structure is altered
Metadata is lost or overwritten
Important pages are removed or become inaccessible
Indexing signals are disrupted
In other words, SEO performance is tied to the structure and consistency of your website, not just the domain.
eCommerce specific complexity
eCommerce websites add an extra layer of difficulty compared to content sites:
A large number of pages, such as products, categories, and filters
Dynamic URLs and faceted navigation
Strong dependence on category structure
Revenue tied directly to organic landing pages
Because of this, even small mistakes during migration can have a measurable impact on both traffic and sales.
Before Migration
1. Document current traffic
Start with a clear baseline of performance. It is important to record current traffic levels, revenue, and key landing pages before any changes are made.
2. Crawl the current website
A full crawl provides a complete view of the existing website.
Using Screaming Frog SEO Spider allows extraction of:
full list of URLs
status codes
internal linking
canonical tags
duplicate and parameter URLs
meta tags and headings
This ensures that no part of the site structure is overlooked.
I recommend crawling with predefined segments to simplify analysis later, such as:
product pages
category pages
brand pages
location pages
filter pages
blog pages
other pages, such as About or Contact
To build a complete dataset, combine multiple sources:
sitemap.xml
list of visited pages from Google Analytics
indexed pages from Google Search Console
This approach provides the most accurate inventory of the current website.
3. Identify what needs to be preserved
This step focuses on understanding what drives traffic and revenue.
Analyze performance over the past year across channels:
organic traffic to preserve rankings
direct and referral traffic to ensure proper redirection
Break down organic traffic by page type to understand contribution:
product detail pages
category pages
blog content
location pages
Analytics platforms provide insight into:
which pages receive traffic
how much traffic they generate
which pages contribute to revenue
key organic landing pages
This helps prioritize what must be preserved.
As a general rule, it is best to retain all pages and content. In practice, pages with no traffic and no revenue contribution can be removed if necessary.
4. Map old URLs to new URLs
Every existing URL should have a defined destination on the new platform.
Create clear mapping rules for each page type. For example, category pages may follow this pattern:
