Moving a website: a practical migration checklist
Updated: Oct 21
Plan a website move around content, URLs, domain access, email, redirects and testing, with a rollback route before launch.

Know what is moving
Changing hosting is different from changing platforms, domains or page URLs. List the pages, files, forms, products, integrations and accounts involved. Check who controls the domain, DNS and email before any change. A hosted builder may require a rebuild rather than a simple file-and-database transfer.
Create an inventory and recovery plan
Record important URLs and any available search or analytics data. Save the content and assets you are entitled to retain, and arrange platform-appropriate backups or exports. Test how recovery would work. Agree who can make changes and when the old setup may safely be retired.
Map URLs and protect working journeys
Where URLs must change, map each important old address to the relevant new page and plan permanent redirects. Update internal links and avoid sending every old page to the homepage. Preserve useful case studies, testimonials and articles. Google advises preparing and testing the new site before a URL move.
Prepare the new site before switching
Check mobile layouts, forms, confirmation messages, key integrations and HTTPS. Review titles, canonicals and temporary indexing restrictions. Plan domain or DNS changes with the person responsible for email so website work does not accidentally interrupt mail. Keep a record of the original settings.
Launch, monitor and retain a rollback route
After the switch, test the public URLs and enquiry process again. Check redirects, sitemap availability and Search Console issues over time. A move can affect crawling and rankings; immediate stability is not guaranteed. Keep the recovery plan and old account until the agreed checks are complete.
Reviewed and updated 21 October 2026. The original publication date is retained.




Comments