Website migration checklist: protect content, functions, URLs and search visibility

A website migration is more than a transfer of pages. A company site may also receive enquiries, take bookings, send notifications and pass information to other systems. A useful checklist starts with what visitors and staff do today, then tests those journeys on the replacement before the release. Include the less visible administration tasks that keep these services working.

1. Inventory the existing site

Export or record every important page, article, file and image, including its current URL, language, owner and destination. Note pages reached from search or external links, even if they are absent from the main menu. Decide what to keep, update, combine or retire. Check who can edit content and whether the new system needs the same permissions and approval steps.

2. Map the working journeys

List each enquiry form, booking flow, confirmation message and integration. Record where submissions go, who receives notifications, what counts as a successful outcome and how errors appear to users. Test representative journeys in staging, including mobile and keyboard use. If email or external systems are involved, coordinate safe test arrangements with their owners rather than treating an on-screen success message as proof of delivery.

3. Prepare URLs and technical SEO

Keep valuable URLs when practical. For changed URLs, prepare a one-to-one redirect map to the most relevant new page, avoiding a blanket redirect to the homepage. Carry over useful page titles, descriptions, headings and internal links, then check canonical URLs, language links, crawl settings and the sitemap in the new environment. These steps help search engines understand the change; they cannot guarantee a particular ranking.

4. Rehearse the launch and recovery

• Take a usable backup and check that the team knows how to restore it.

• Agree who changes the domain and DNS, and preserve required email records.

• Check redirects, key pages, forms, booking paths and integrations on the live domain.

• Review server errors, missing pages, search indexing and user reports after launch.

The checks should match the site's actual functions and the agreed scope. If you are still deciding whether to upgrade, move hosting or rebuild, read our comparison guide. To map your site's requirements, request a website assessment.