Start with a complete URL inventory
A reliable migration starts with a complete picture of what already exists. Collect live pages, sitemap URLs, indexed URLs, campaign destinations, backlink targets and historical routes from analytics and Search Console. Then assign every meaningful URL a deliberate outcome: keep, improve, consolidate, redirect or retire. This prevents valuable content and hidden campaign pages from disappearing simply because they were not visible in the navigation.
Map every meaningful outcome
Retain pages that already serve customers or attract qualified visibility. Where several old pages compete for the same purpose, consolidate them into the strongest destination and use a relevant 301 redirect. Retire obsolete content intentionally with the correct status, and keep utility pages such as internal confirmations out of search. The goal is a cleaner website without breaking the routes people and search engines already trust.
Protect measurement
Measurement must be treated as launch-critical infrastructure. Verify analytics, tag management, consent behaviour, form events, call tracking, thank-you routes and campaign parameters before traffic moves. Test genuine submissions from multiple devices and confirm that the enquiry reaches the correct team. Without that verification, a successful launch can look like a performance collapse simply because the new site stopped recording the journey.
Test after launch
The first days after launch require active observation. Crawl the new site and redirect map, inspect status codes, confirm canonical tags, review robots directives and submit accurate sitemaps. Test forms, navigation and campaign pages again in production. Watch Search Console and analytics for unexpected losses, then investigate patterns quickly before they become prolonged visibility or revenue problems.
Why this matters commercially
A migration brings design, content, development, search and analytics into the same high-risk moment. The safest programmes treat launch as a controlled change, not a visual handover. Owners are assigned to redirects, forms, tracking, indexation and post-launch checks before the release date. That discipline protects both customer experience and the years of authority attached to the existing website.
Questions this should help you answer
Where should we start?+
Start with the customer decision and the commercial outcome, then identify the evidence, content and technical work required to support it.
What should we measure?+
Measure the action closest to business value, supported by diagnostic signals that explain why performance improves or declines.
When should we review the work?+
Review after implementation has collected enough representative data, then separate short-term noise from a pattern that requires action.