01What can you lose in a migration?

Organic traffic can drop if URLs change and are not redirected, if titles, descriptions, canonicals or structured data disappear, or if the new sitemap does not match the real addresses. Customer data, orders or stock can also be lost if the import is not reconciled, and integrations (payments, shipping, invoicing) can break if they are not reconnected before cutover.

None of that is inevitable. It is avoided with an inventory, a 301 table, a pilot import and tests — not by rushing on the day of the switch.

Fig. 1 · Before you migrate: inventory the platform, modules, integrations and indexed URLs

02Before you migrate: inventory the platform, modules, integrations and indexed URLs

Before touching the new store you need to know what the current one holds: platform and version, modules or apps, payments, carriers, invoicing, ERP or PIM, newsletter, consent, languages, and the list of URLs that are already indexed or that receive visits.

That inventory is the basis of the audit. Scope and risks come from it, in writing. Without it, any cutover date is a guess.

03The URL mapping table and the 301 redirects

Every important URL on the current store needs a destination on the new one. That mapping is written in a table and implemented as a 301, so people and search engines land on the equivalent page.

URLs that should no longer exist are handled separately, not sent to the home page in bulk. The table is kept after launch, as a record of what was redirected.

04Migrating the catalogue: products, variants, attributes, images, stock, customers and orders

The catalogue is not imported once, on the day of cutover. You run a pilot import, reconcile the counts (products, variants, images, stock, customers, orders) and fix what does not match before the final import.

If the source system has reviews or other records, the audit says whether they travel. That is not assumed.

05Integrations: payments, carriers, invoicing, ERP/PIM, newsletter and consent

A store does not open on the catalogue alone. Payments, shipping, invoicing, ERP or PIM, the newsletter and consent collection have to keep working on the new platform, or a replacement has to have been agreed.

What is reconnected, replaced or left out is written down before work starts, not on the day of cutover.

06Tests before cutover: trial orders, coupons, taxes, shipping, search, languages and mobile

Before the store the customer sees is switched, you run trial orders, coupons, taxes, shipping, internal search, languages and mobile navigation. If something fails, cutover waits.

Fig. 2 · Cutover day: how to keep selling until the last minute

07Cutover day: how to keep selling until the last minute

The old store keeps selling until the new one is ready. You switch when the tests pass, not on a date set before seeing the work. At that point the redirects go live, the domain points to the new store, and you check that orders arrive where they should.

08Afterwards: what to watch in Search Console in the first weeks

After cutover you watch Search Console: crawl errors, coverage, pages affected by the redirects, and whether the new sitemaps are being read. If an error appears, you correct it. There is no number of weeks that fits every store; the watch lasts until the change has been recognised.

09A checklist for an online store migration

This list sums up the work. It does not replace an audit of your store, but it stops a step being skipped.

  • Inventory the current platform, modules and integrations
  • Export indexed URLs and URLs that receive visits
  • Build the mapping table and the 301 redirects
  • Decide what to do with URLs that have no equivalent, without sending them all home
  • Keep titles, descriptions, canonicals and structured data
  • Generate a sitemap that matches the new URLs
  • Run a pilot catalogue import (products, variants, attributes, images, stock)
  • Reconcile counts for the catalogue, customers and orders
  • Include reviews or other records only if the audit lists them
  • Reconnect payments, carriers, invoicing, ERP or PIM, newsletter and consent
  • Test orders, coupons, taxes, shipping, search, languages and mobile
  • Keep the old store selling until cutover
  • Switch when the tests pass, not before
  • Turn on the 301s and check that orders arrive in the new store
  • Submit the new sitemap and watch Search Console
  • Fix crawl or coverage errors when they appear

This checklist is the one I follow in the website and e-commerce migrations service.

If the change also involves design or architecture, read how to decide whether to redesign your website or build a new one.