MOVE WITHOUT GUESSWORK

Website migration checklist

A safer website move separates copying the application from switching live traffic. Build and test the new environment first, then change DNS only when you have a way back.

1. Record the current ownership and DNS

Write down the registrar, nameservers, hosting provider, email provider and current DNS records. Export the zone where possible.

2. Take a restorable backup

For WordPress, the official documentation is explicit that a typical full backup needs both the files and the database. Downloading the WordPress directory alone normally does not contain the database. See WordPress backup guidance.

3. Build the new site before changing DNS

Copy files, import the database, set environment variables and configure the correct runtime versions. Use a temporary hostname or local hosts-file override where appropriate.

4. Test application behaviour

Check forms, logins, scheduled jobs, uploads, database writes, redirects, images, search and external integrations. Do not test only the homepage.

5. Confirm HTTPS

Make sure the new environment can serve the real hostname securely before or immediately as traffic moves.

6. Change the minimum DNS needed

Update the records that route web traffic. Do not overwrite MX, TXT or other unrelated records just because the hosting provider gave you a new DNS template.

7. Keep the old hosting temporarily

Leave the previous environment available long enough to confirm that traffic and data are reaching the new host correctly. Dynamic sites may need a content freeze or final database sync to avoid two diverging copies.

8. Verify backups again after the move

The backup job may have been tied to the old host. Confirm that the new production system is actually being backed up and that you know how to restore it.

Also read moving a domain without moving the website.