A website migration is any change that moves your site’s content, data or addresses: a new CMS, a redesign with new URLs, a domain change, a move from a site builder to a custom application, or all of these at once. Done carefully, visitors barely notice. Done carelessly, links break, forms stop sending, data goes missing and search traffic drops.
This website migration checklist is organised into three phases: before, during and after. It draws on Google’s own guidance for site moves with URL changes, linked below, and on the practical steps that protect content, data and integrations. Use it as a working list with your developer.
Before you start: decide what kind of move this is
Different moves carry different risks. Write down which of these apply:
- Platform change: same URLs and domain, new system underneath.
- URL change: pages get new addresses, on the same domain or a new one.
- Domain change: the whole site moves to a new domain name.
- Design or content change: templates, navigation or page content are reworked.
- Data move: customer accounts, orders, records or form submissions move between systems.
Each extra item adds work and risk. Where you can, avoid changing everything at once. A platform change with unchanged URLs is easier to test and to roll back than a platform, domain and content change on the same day.
Phase 1: Inventory and planning
- Export a full list of current URLs from your sitemap, analytics, server logs and Google Search Console, including images, PDFs and other files people link to.
- Mark which pages bring traffic, enquiries or sales, so they get the most care.
- List every form, integration, tracking script and third-party service on the current site, and where its data goes.
- Record current settings that are easy to forget: redirects already in place, email routing, DNS records, cron jobs, payment webhooks.
- Decide what is not moving. Archive or remove outdated content on purpose, not by accident.
- Agree who owns the new domain, hosting and platform accounts, and who signs off the launch.
- Take a full backup of the current site, files and database, and confirm it can be restored.
Phase 2: Mapping URLs and data
This is the step that protects your existing links and search visibility.
- Build a redirect map: every old URL paired with its most relevant new URL.
- Avoid sending many old pages to the home page or another irrelevant page.
- Avoid redirect chains; point old URLs straight to their final destination.
- Plan to update internal links, canonical tags and hreflang annotations to the new URLs.
- Map data fields between the old and new systems: products, customers, posts, categories, media, metadata.
- Run a sample data import and check it by hand before importing everything.
Google recommends server-side permanent redirects (such as HTTP 301 or 308) where possible and keeping them in place for at least a year, and ideally indefinitely. Its guide to site moves with URL changes explains the reasoning in detail.
A migration is mostly a mapping exercise. Every old address needs a sensible new home.
— VSN Editorial
Worked example: a small redirect map
Here is what part of a redirect map might look like for a small service business moving from static pages to a CMS. The addresses are illustrative.
| Old URL | New URL | Why |
|---|---|---|
| /services.html | /services/ | Same page, new platform address |
| /web-design.html | /services/website-design/ | Content merged into a service sub-page |
| /blog/?p=123 | /blog/how-to-plan-a-website/ | Old query-string link moved to a readable slug |
| /offer-2022.html | /offers/ | Expired offer sent to the closest current page, not the home page |
| /files/brochure.pdf | /files/brochure-2026.pdf | A file other sites still link to |
| /old-team-page.html | None | Removed on purpose, with no close replacement |
Keep the real map in a shared spreadsheet with one row per old URL and columns for the new URL, redirect type, priority (from the traffic you marked in Phase 1) and a “tested” tick. The developer configures redirects from the same file, and whoever checks staging works down the rows.
The last row matters too. A page you remove on purpose, with no close equivalent, can simply return a 404 or 410 status rather than a misleading redirect. Google’s documentation on HTTP status codes and how Search handles them explains how both are treated.
Phase 3: Build and test on staging
Never test a migration on the live site. Build the new version on a staging environment that visitors and search engines cannot see, and test there.
- Staging is protected from indexing (password or equivalent), and that protection is on the list to remove at launch.
- Test the redirect map: a sample of old URLs, including the important ones, resolves to the right new pages in one hop.
- Every form submits and the message arrives where it should.
- Logins, accounts and passwords work as planned, or users know they must reset.
- Payments, bookings and integrations run end to end in test mode.
- Key pages work on the agreed browsers and devices.
- Analytics and tag tracking fire on the new templates.
- Page titles, descriptions and structured data carried over where intended.
Phase 4: Launch day
- Confirm a final backup of the old site and a written rollback plan.
- Freeze content changes on the old site, or plan a final content sync.
- Run the final data import and spot-check it.
- Switch DNS or deploy, then enable redirects.
- Remove staging protections, including any “noindex” settings, from the live site.
- Test the important paths again on the live domain: home page, top pages, forms, checkout or sign-in.
- Submit the new sitemap in Search Console. If the domain changed, verify both properties and consider Google’s Change of Address tool.
Phase 5: The first weeks after launch
Google notes that rankings can fluctuate temporarily during a move, and that larger sites take longer to settle. Monitoring helps you separate normal settling from real problems.
- Watch Search Console for crawl errors, 404s and indexing changes.
- Check server logs or analytics for old URLs that still receive visits but lack a redirect.
- Compare form submissions, sales or sign-ups with the weeks before launch.
- Fix broken internal links and update important external links you control, such as social profiles and directory listings.
- Keep the old domain registered and the redirects running.
- Keep the old site’s backup until you are confident nothing is missing.
Who does what during a migration
A migration touches several people’s work, so assign the roles explicitly before Phase 1 starts:
- Project owner: approves the scope, the redirect map and the go-live decision.
- Developer or agency: builds the new site, runs imports, configures redirects and manages staging.
- Content owner: checks that pages, media and metadata arrived correctly.
- Marketing or SEO lead: reviews the URL map, tracking and Search Console after launch.
- Account holders: whoever controls DNS, hosting, the domain registrar and third-party services must be available on launch day.
Mistakes this website migration checklist helps you avoid
- Launching with the staging “noindex” setting still switched on.
- Redirecting everything to the home page.
- Forgetting files and images that other sites link to.
- Losing form routing or email settings because they lived in the old platform’s configuration.
- Letting the old domain expire.
If the migration is part of a larger rebuild, our guide to web development mistakes covers the planning errors that tend to surface at the same time. If you are moving to a different type of platform, read CMS vs custom web application first.
Key takeaways
- Inventory every URL, form, integration and setting before you change anything.
- Map each old URL to its most relevant new page with permanent server-side redirects.
- Test on a protected staging site, then remove those protections at launch.
- Keep redirects and the old domain for at least a year, and ideally longer.
- Expect some temporary ranking movement and monitor closely for real errors.
Questions about website migrations
Will a website migration hurt my search rankings?
Google says rankings can fluctuate temporarily during a site move. Careful redirects, updated internal links and a submitted sitemap help search engines understand the change, but no one can guarantee rankings during or after a migration.
How long should redirects stay in place after a migration?
Google recommends keeping redirects for at least one year and suggests keeping them indefinitely where possible, because old links on other sites keep sending visitors.
Can we migrate customer accounts and passwords?
Account data can usually be migrated. Whether passwords carry over depends on how both systems store them. If they cannot, plan a clear password-reset message for users.
Should we redesign and migrate at the same time?
It is possible, but every additional change makes problems harder to trace. If timing allows, move the platform first with the same URLs and content, then redesign.
Do we need to tell Google if only the platform changes and the URLs stay the same?
There is no special notice for that. Check that each page keeps its content, title and status code, submit the sitemap and watch Search Console for errors. Google’s Change of Address tool is meant for moves to a new domain.
VSN plans migrations with content and data mapping, redirect maps, staging checks and client sign-off, while being clear that third-party and data-quality risks cannot be removed entirely. See our web development service or talk to us about your move.
Filed under Software



