Ecommerce replatforming without losing SEO: the complete migration checklist

Few projects make an ecommerce team as nervous as replatforming. The reasons to move are usually good: the old platform is slow, expensive to maintain, missing integrations, or simply cannot keep up with how you sell today. But the risk is real. Every store owner has heard a story about a migration that went live on a Friday and lost a large share of its organic traffic by the following week.

The good news is that search engines do not punish a store for changing platforms. They react to what changes on the URLs they already know: pages that disappear, content that gets thinner, redirects that point to the wrong place. Control those, and a migration can be close to invisible in your traffic reports. This checklist walks through the work in the order it should happen.

Why stores lose traffic when they replatform

Before the checklist, it helps to understand what actually goes wrong. In almost every case, the loss comes from one of these:

• Missing redirects: Old product and category URLs return a 404 error. All the links and ranking history attached to them are lost.
• Wrong redirects: Old URLs all point to the homepage or to a generic category, which search engines tend to treat like a missing page.
• Lost content: Category descriptions, product copy, custom page titles and meta descriptions are not migrated, so the new pages are thinner than the old ones.
• Changed internal linking: Navigation, filters and breadcrumbs change, and important pages end up buried several clicks deep.
• Technical defaults: The new site launches with a noindex tag left over from staging, a blocked robots.txt, or duplicate URLs created by filters.
• Slower pages: Heavier themes or unoptimized images make the new store slower, especially on mobile.

None of these are caused by the platform you move to. They are caused by the migration process.

Phase 1: Take a complete inventory of the old store

You cannot redirect what you do not know exists. Start by building a single spreadsheet of every URL that matters.

1. Crawl the current site with an SEO crawler to collect every indexable URL: products, variants with their own URLs, categories, filtered pages that rank, blog posts, CMS pages and image URLs.
2. Export your top pages from Google Search Console (Performance report, Pages tab). This shows which URLs actually earn clicks and impressions, including ones your crawler may miss.
3. Export pages from your analytics tool that receive organic or referral traffic.
4. Check your backlinks. Pages that other sites link to carry authority. Your crawler or backlink tool can list them; Search Console's Links report is a free starting point.
5. Export the XML sitemap from the current store.

Combine these into one list and remove duplicates. For each URL, record its type (product, category, page, post), its traffic and whether it has backlinks. This becomes your master URL list, and it is the single most important document of the project.

Phase 2: Map every old URL to its new home

Now decide where each old URL will live on the new platform. This is slow, detailed work, and it is where migrations succeed or fail.

• Same item, new URL: A product or category that exists on both sites gets a one-to-one 301 redirect.
• Same item, same URL: If the new platform lets you keep the old URL path, keep it. No redirect is needed, which is always the safest option.
• Discontinued products: Redirect to the replacement product if there is one, otherwise to the closest parent category. Do not redirect everything to the homepage.
• Merged categories: Redirect each old category to the new category that now contains its products.
• Pages with no equivalent: If a page truly has no replacement and no value, a 404 or 410 is acceptable. Reserve this for pages with no traffic and no backlinks.

Write the mapping as two columns, old path and new path, in a format your new platform can import in bulk. Pay attention to the details that break redirects in practice: trailing slashes, uppercase letters, URL-encoded characters and query parameters.

Phase 3: Move the content, not just the catalog

Product data is the obvious part of a migration. The ranking signals often sit elsewhere. Make sure each of these comes across:

• Page titles and meta descriptions for products, categories and pages. If you wrote them by hand on the old platform, do not let the new one fall back to defaults.
• Category descriptions and any introductory or buying-guide copy on category pages.
• Product descriptions, including specification tables, size information and FAQs.
• Image alt text and file names, plus images in a size and format that loads quickly.
• Customer reviews, with their dates and ratings. Reviews are content, and losing them makes product pages weaker for shoppers and search engines.
• Blog posts and guides, with their original publish dates.
• Structured data: product markup with price and availability, breadcrumbs, and organization details.
• Hreflang and language-specific URLs, if you sell in more than one language.

Phase 4: Migrate the data your business runs on

Search traffic is only half of the migration. Customers who return after launch expect the store to remember them.

1. Products and variants: SKUs, barcodes, prices, stock, weights and variant options. Check that variant combinations (size and color, for example) map correctly.
2. Customers: Accounts, addresses and marketing consent. Consent records matter: only carry over subscribers who actually opted in.
3. Order history: So customers can see past orders and your team can handle returns for orders placed before the move.
4. Gift cards, store credit and discount codes that are still active.
5. Integrations: Payment providers, shipping carriers, marketplaces, accounting and email tools all need to be reconnected and tested.

Phase 5: Prepare the new store before launch

While the new store is in staging, keep it out of search results, then make sure everything that blocks search engines is removed at launch.

• Protect staging with a password or a noindex tag, and write down every place you added one so you can remove it.
• Check robots.txt on the new platform: it should not block products, categories or important resources.
• Make sure each product has one canonical URL, and that filter and sort parameters do not generate thousands of indexable duplicates.
• Test page speed on mobile with Google's free PageSpeed Insights for a product page, a category page and the homepage, and compare them with the old site.
• Review the main navigation: your most important categories should stay within a click or two of the homepage.
• Prepare the new XML sitemap and confirm it lists only live, indexable URLs.

Launch day: test, then test again

Pick a quiet day for your business, not the start of a sale or a holiday season, and make sure the people who can fix problems are available for the next few days.

For the redirect test, feed your full list of old URLs into a crawler in list mode. Every row should show one 301 hop and a final 200 status. Fix any chains (redirects that point to other redirects), loops and 404s before you do anything else.

After launch: what to monitor and for how long

The first weeks after launch are when you catch problems while they are still small.

1. Search Console, daily: Watch the Pages report for rising "Not found (404)" and "Page with redirect" counts, and check that the new sitemap is being processed.
2. Organic traffic by page type: Compare products, categories and blog posts with the same period before launch. A drop concentrated in one page type usually points to a specific issue, such as category copy that did not migrate.
3. Top landing pages: Take your top organic pages from the inventory and check each one by hand.
4. Server and 404 logs: Old URLs you did not know about will appear here. Add redirects for any that receive visits.
5. Conversion rate and checkout errors: Traffic is only useful if checkout works. Watch for payment failures and abandoned checkouts after launch.

Keep the old platform's export and your crawl data for months. They are the only way to answer questions like "what did this page say before?" when an unexpected issue appears.

Example scenario: a home fragrance brand changes platforms

Here is a hypothetical example. A small brand selling candles and diffusers runs its store on a self-hosted system that has become slow and hard to update. Most of its sales start with organic search, so the team treats the migration as an SEO project first.

• Inventory: The team crawls the site and finds several hundred URLs: products, scent-based categories, gift guides and blog posts, plus old seasonal collection pages that still have backlinks.
• Mapping: Products keep their names but get new URL paths on the new platform, so each gets a one-to-one redirect. Discontinued seasonal scents redirect to the closest current scent, and old seasonal collections redirect to the main gift category.
• Content: Category descriptions and the gift guides are copied over, with their titles and meta descriptions. Reviews are imported with their original dates.
• Launch: The store goes live on a quiet weekday. A crawl of the old URL list shows a handful of redirect chains caused by trailing slashes; they are fixed the same afternoon.
• Monitoring: In the following weeks, Search Console shows a few 404s from old campaign URLs that were never in the sitemap. The team adds redirects for them.

The lesson is simple: the brand did not avoid problems, it found them early because it knew what the old site looked like and checked the new one against it.

How Shopiyz handles platform migration

Shopiyz is a hosted ecommerce platform, so the servers, security updates and performance work are handled for you. When you migrate to Shopiyz:

• Data import: Import tools help you move products, customers and order data from your previous platform, and bulk CSV import and export is available for products. Our technical support team guides you through the migration.
• SEO controls: Manage titles, meta descriptions, URLs, redirect rules and sitemap settings in one place, so your redirect map is part of the launch rather than an afterthought.
• Multiple languages: If you sell internationally, each language gets its own SEO settings. Our multilingual store checklist covers the details.
• Channels: Reconnect payment, shipping and marketplace integrations from one panel instead of separate plugins.

You can start on the free plan and build your new store in parallel with the old one, then go live when your redirect map and checks are ready. If you would like to plan a migration with us, get in touch.