Website Migration Checklist: Before, During and After the Move

A bunch of wires that are connected to a server

A website migration is any substantial change to where or how a site is served: a new host, a new domain, a new platform, or a new structure after a redesign. Done carefully, visitors notice nothing. Done carelessly, traffic and email can disappear overnight. This checklist is organised into three phases: before, during and after the move.

Identify the type of migration

Different moves carry different risks. Tick all that apply.

  • Host change: same domain, same site, new server. Lowest risk.
  • Domain change: every address changes. Search visibility depends on redirects.
  • Platform change: new CMS or shop system. Addresses, templates and features all change.
  • Redesign or restructuring: new page structure and addresses on the same domain.
  • Protocol change: from http to https.

Avoid combining several of these at once if you can. When something goes wrong, you will want to know which change caused it.

Before the move

Planning

  • A date is chosen in a quiet period, not before a campaign or peak season.
  • One person is responsible for the migration.
  • A rollback plan exists: how to return to the old site if needed.
  • Everyone affected knows when a content freeze begins.

Record the current state

  • A full inventory of existing URLs is made. See the Website Content Inventory Template.
  • Current traffic, rankings for key queries and conversion figures are saved as a benchmark.
  • The pages with the most visits and incoming links are identified.
  • A crawl of the old site is saved.

Backups and access

  • A complete, tested backup of files and database exists. See How to Create a Basic Website Backup and Test a Restore.
  • You have login details for the old host, the new host, the domain registrar and DNS.
  • The complete DNS zone is copied or screenshotted, including MX and TXT records.
  • You know where email for the domain is hosted and whether it is affected.

Redirects

The new site

  • It is built on a staging environment that search engines cannot index.
  • All content has been transferred and checked.
  • Titles, meta descriptions, headings and alt texts are carried over.
  • Internal links point to the new addresses, not through redirects.
  • Canonical tags, structured data and hreflang are correct.
  • Forms, search, checkout and integrations have been tested.
  • Analytics and consent tools are installed.
  • The DNS TTL has been lowered a day in advance.

During the move

  • Content editing is frozen, or the old site is in maintenance mode, so nothing new is lost.
  • A final copy of the database and files is taken.
  • The new site is made live, or DNS is switched to the new server.
  • The SSL certificate is active on the new server.
  • Redirects are switched on.
  • The noindex setting and any password protection from staging are removed.
  • robots.txt allows crawling.
  • The old hosting remains active.

Immediately after

Check within the first hour.

  • The homepage and main pages load over HTTPS.
  • A sample of old addresses redirects correctly with a 301.
  • Forms deliver messages and a test order completes.
  • Email to and from the domain still works.
  • Analytics is recording visits.
  • No important page is set to noindex.
  • A crawl of the new site shows no broken links or unexpected errors.

In the first days

  • The new XML sitemap is submitted in Search Console.
  • For a domain change, the Change of Address tool in Search Console has been used, and the new domain is verified.
  • Key pages have been inspected with the URL inspection tool.
  • Links in business profiles, social accounts, email signatures and advertising point to the new addresses.
  • Owners of sites that link to your most important pages have been asked to update their links, where practical.

In the following weeks

  • The Page indexing report is checked weekly for not-found errors, and missing redirects are added.
  • Traffic, rankings and conversions are compared with the benchmark.
  • Server logs or error reports are reviewed for repeated 404s.
  • The DNS TTL is returned to its normal value.
  • The old hosting is cancelled only after one to two weeks of stable operation, and after a final backup.
  • For a domain change, the old domain stays registered and its redirects stay active for at least a year, preferably longer.

What to expect

Some fluctuation in search visibility is normal after a domain or platform change, and it can take a few weeks for search engines to process everything. A host change with unchanged addresses should cause little or none. A lasting drop usually points to missing redirects, lost content or pages blocked from indexing.

The mistakes that cause the most damage

  • No list of old addresses, so redirects are incomplete.
  • Redirecting everything to the homepage.
  • Leaving the staging noindex or robots.txt block in place after launch.
  • Losing email because MX records were not recreated.
  • Cancelling the old host too early.
  • Changing design, content, platform and domain all in one step.

Next step

For a host change on WordPress, follow the step-by-step method in How to Move a WordPress Site to a New Host: Migration Workflow.