Host migration checklist

The checklist, in order

A host migration is a copy of files and database to a new server, a config change, and a DNS cutover. In that order only does it stay quiet. Everything below assumes you keep the same domain and protocol.

Before you start

1. Back up everything: full file export plus the database dump. Confirm you can restore from it before touching anything; a test restore on the destination host is the strongest proof. (The WordPress restore order generalizes to any CMS.)
2. Inventory the site: platform, CMS, hardcoded URLs, cron, email accounts, SSL certificates, the content and the features that live in services (CDN, form endpoints, queues, scheduled emails).
3. Set up the destination host and confirm PHP/DB versions match or are upgraded safely.
4. Reduce DNS TTL to a low value (300 seconds for A records) at least 24 hours before cutover so the final change propagates fast. See DNS TTL for the mechanics.
5. Choose a cutover window: low traffic, preferably with the ability to stay up with the old host for a day.

The cutover order

1. Copy files and database to the new server (rsync or a full tarball transfer; do not install over a live database).
2. Point the site configuration at the new database and re-test local or private-host behavior (a hosts-file entry lets the new server answer the domain on your own machine before DNS).
3. Update the DNS records at the registrar or DNS provider to the new host IP. Then wait for propagation; the flapping period is normal, and a TTL-reduced record makes it short.
4. Switch SSL: the certificate on the new host must match the domain before search engines or browsers trust it. The SSL and certificate article covers the renewal mechanics.

After the cutover

• Verify locally: site loads on the public domain, private window, both http and https, and the old host is no longer being asked by new visitors (check the log for the drop).
• Check integrations, cron, email, CDN, backup jobs and external tools still write to the new host.
• Re-examine Search Console: the property does not need re-verification if the DNS TXT is intact, but the sitemap URL and the certificate health should be re-tested; the submit a sitemap guide covers the confirmation step.
• Keep the old host up for 7 to 14 days as a rollback option. Content on the old host only needs a 301 to the new site if the URL structure changed; see URL migration planning.

Something without a checklist most moves forget: the manual record of what came from where. The old host's panes (email accounts, mailbox settings, DNS extras, subdomains) live outside the website folder. Write them down during step two, not when the old panel is frozen.