Migration Checklist

Moving a site is mostly careful bookkeeping. Tick items off as you go; your progress is saved in this browser.

• Inventory everything. Sites, databases, cron jobs, mail accounts, subdomains, redirects, SSL certificates. Write it down in one list. This is the step that prevents most surprises.
• Note current DNS records and TTL values. Export the zone if your provider lets you, or take screenshots. You will want to recreate or compare.
• Lower the TTL. Set it to 300 seconds on the records you will change, at least a day before the move, so the switch takes effect quickly.
• Take a full backup. Files and databases both, and store one copy somewhere other than the old server.
• Check the new environment. PHP version, extensions, memory and upload limits, and database version should match what the site needs.
• Copy files and import databases. Use SFTP, rsync or the host's migration tool. For large databases, command-line import is more reliable than a web interface.
• Update configuration. Database credentials, file paths and, if the domain changes, the site URLs inside the database.
• Test the new copy. Edit your hosts file so your computer sees the new server while everyone else still sees the old one. Click through the whole site, including forms and logins.
• Install the SSL certificate. Do this on the new host before switching, or visitors will see warnings the moment DNS changes.
• Recreate mail accounts. If mail moves, create mailboxes first and copy existing messages with an IMAP sync tool before changing MX records.
• Freeze content changes. Tell editors and shoppers when the switch will happen. For busy sites, plan a final sync of changes.
• Switch DNS. Change the A and AAAA records, and MX if mail is moving. Leave other records alone.
• Watch both servers. Check logs on the old and new host for the next day or so. You will see traffic shifting.
• Test what happens on a timer. Scheduled posts, order emails, invoice runs, backups.
• Check redirects and search tools. Verify old URLs still lead somewhere useful and look for crawl errors in Search Console.
• Keep the old hosting for a week. Do not cancel the moment things look fine. Problems often show up days later.
• Raise the TTL again. Back to something like 3600 once you are sure.
• Run a fresh backup on the new host. And try restoring it. Now you know the new setup works end to end.