A website migration is never just "putting the new site online". The real job is to keep what already works: URLs, SEO traffic, conversions, tracking, forms, media, performance, access, and the ability to roll back if something critical breaks after launch.
Use this checklist as a working document before a redesign, a CMS change, a hosting migration, an e-commerce rebuild or a technical takeover. The boxes you tick are saved in this browser, so you can pick up the preparation later.
Start with sections 2 and 3 before you set a launch date. If a checklist is still incomplete, the migration stays in staging.
01 / 07
The 4 areas to lock down before any migration
If any of these areas is unclear, the launch stays in staging. The priority is still to protect the pages that bring in traffic and conversions.
Redirects
Export the old URLs, map them to the new ones and test the 301s before go-live.
Indexing
Check titles, canonicals, robots rules, the sitemap, pagination and your key pages.
Tracking
Verify analytics, consent, forms, pixels and the events that actually matter.
Rollback
Know what to restore, who makes the call and how long the risk window stays open.

02 / 07
Before the migration: define the real scope
A migration often touches content, SEO, forms, measurement, speed, third-party scripts and transactional emails. Before you move anything, list the pages that really matter.
Preparation inventory
0of 6 checked
03 / 07
The redirect plan: the file that saves your traffic
The redirect plan must connect every important URL on the old site to a relevant destination on the new one. Redirecting to the homepage rarely helps a page that served a specific intent.
Old URLs
A full export from your crawl, CMS, Search Console and historical sitemap.
Risk: useful pages returning 404 after launch.
Mapping
A logical new destination for each important page, not an automatic redirect to the homepage.
Risk: lost relevance and a poor user signal.
Chains
Avoid multiple hops from old to intermediate to final. The old URL should point straight to its destination.
Risk: slower loading and wasted crawl.
Tests
Check status codes in staging, then right after launch, on your priority pages.
Risk: finding broken key pages too late.
Never sign off without a control crawl
A mapping sheet is worthless until it is tested. Before launch, check your important old URLs, the pages with backlinks and your conversion paths.
04 / 07
Launch day: publish, test, fix fast
You don't publish and "see what happens". Prepare a short sequence and separate blocking tests from secondary tweaks.
Immediate actions at cutover
0of 3 checked
05 / 07
After the migration: watch for weak signals
Day one can look like a success while problems only show up a week later. Some errors appear after a recrawl, a cache purge or an e-commerce scenario being triggered.
Checks at day 1, day 7 and day 30
0of 5 checked
06 / 07
Common mistakes to avoid
Most failed migrations come from simple oversights: a noindex left in place, a missing redirect, an untested form, or an old business page treated as secondary.
Changing every URL without a precise mapping
The main risk is turning a migration into a mass deletion of pages. Every useful URL needs a logical destination.
Forgetting forms and events
The site looks live, but leads no longer come through. Test forms with real submissions.
Launching when nobody can fix things
A sensitive migration should go live when the engineering, SEO and business teams can make decisions quickly.
07 / 07
Frequently asked questions
Resources




