Skip to main content
FHAVI

Free resource

What to check before switching a store to a new platform

Migrations fail in three quiet ways: links that 404 after the switch, a Merchant Center account that no longer recognises the site, and tracking that keeps firing into a void. None of them show up in a test until real traffic arrives.

Read this first

The migration is not the launch — it is the week after

A store moves in an afternoon. What determines whether the move costs you a month of revenue is what happens to the three systems outside the store: Google's index, Google's product feed and your ad platforms' event history.

Each of those depends on something that is easy to overwrite in a migration: URLs, the feed's references to them, and the identifiers your tracking uses to join browser and server events.

Work through this before the switch, keep the sheet open during it, and do not close the old site until every item is confirmed after it.

Before the switch

Export and record what you cannot recreate

01

URLs and redirects

  1. A full crawl of the current site exported to a URL list — products, collections, pages, blog posts, not just the home page.
  2. A redirect map written before the move, mapping every old URL to the closest equivalent new URL, in one file.
  3. Decision recorded for URLs with no equivalent: redirect to the nearest parent category, not to the home page.
  4. Trailing-slash, case and www/non-www behaviour noted for the old site so the redirects match what was indexed.
  5. A list of externally linked URLs — press, affiliates, marketplace listings — so those are checked separately after the switch.
02

Feed and Merchant Center

  1. Product IDs preserved where possible. Changing ids starts every item's history over and can force a re-review.
  2. Feed link and image link patterns written down, so the new site can be checked against them item by item.
  3. Merchant Center account access confirmed for whoever is doing the migration — not only the departing agency.
  4. The current disapproval and suspension state recorded, so a post-migration problem is not mistaken for a new one.
03

Tracking

  1. Every live tag, pixel and container id documented with where it is installed.
  2. The server-side forwarder and its credentials noted, including where the token is stored.
  3. A baseline captured before the move: last 7 and 28 days of events, so post-move numbers can be compared to something real.
  4. Consent and cookie behaviour recorded, because a new platform's default is rarely the old one's.

During the switch

The order that avoids two invisible failures

04

Sequence

  1. Put the new site on a staging domain and crawl it — confirm every page types, loads and is reachable without a login.
  2. Import the redirect map and test a random sample of twenty old URLs for a single hop to the right destination.
  3. Keep the old site reachable until DNS has propagated fully, then remove it only after a week of clean logs.
  4. Switch DNS once, at a low-traffic hour, and do not modify redirects and DNS in the same hour.
  5. Re-submit the sitemap in Search Console and request indexing for the twenty most commercially important URLs.
05

What to leave alone

The instinct to rebuild everything at once is the most expensive one.

  1. Do not redesign the checkout in the same release as the platform move — you will not know which change caused a drop.
  2. Do not change the tracking architecture mid-migration; carry it across first, improve it after the data is stable.
  3. Do not change prices or catalogue structure in the same week, or a feed disagreement becomes impossible to attribute.

After the switch

The checks nobody schedules

06

Within 24 hours

  1. Every tracked event still fires: page view, product view, add to cart, checkout, purchase — on the new domain.
  2. Purchase is still sent from the server, with the same event id pairing to the browser event.
  3. Merchant Center still recognises the site: no new domain-verification or claim warnings.
  4. No redirect loops and no chains longer than one hop on the sample of twenty URLs.
  5. The 404 rate in server logs is at or below its pre-migration level.
07

Within a week

  1. Search Console coverage report shows no new spike in excluded or 404 URLs.
  2. Feed item count matches the new catalogue, with no silent drop in approved items.
  3. Ad platform conversion counts match order counts within the ratio you saw before the move.
  4. Revenue per session and conversion rate are within normal range for the season — if they are not, the candidate is speed, checkout or missing collections, in that order.
  5. The redirect map is kept, not deleted. You will need it again for the next move.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Moving platforms and want the continuity handled?

Tell us what you are moving from and to. We will scope the redirect, feed and tracking work separately so the cutover is one job, not three.

Prefer email? Write to md@fhavi.com