This website migration checklist lists every step of a host move in the right order. Most migration problems come from something forgotten, such as a cron job, a TXT record or mail that arrived mid-move, rather than from the copy itself. Work through the list and tick items off.
Before you start
- Access to the old host (control panel, SSH or FTP) and the domain registrar or DNS provider.
- A new hosting account, for example MdmHost cPanel hosting.
- A quiet time window for the final switch.
Inventory checklist
- Domains, addon domains, subdomains and redirects.
- Databases and the config file that uses each one.
- Email accounts, forwarders, autoresponders, filters and mailing lists.
- Cron jobs and their commands.
- DNS records: A, AAAA, MX, CNAME, TXT (SPF, DKIM, DMARC, verification), SRV, CAA.
- PHP version, PHP extensions and custom
php.inivalues. - SSL certificates (paid certificates need reissuing or moving).
- Third-party integrations that whitelist the server IP (payment gateways, APIs, SMTP relays).
Backup checklist
- A full backup downloaded to your own computer or storage, not only kept on the old host: website backups explained.
- Separate database dumps.
- An export of the DNS zone (copy the records into a text file).
Website migration checklist for the move itself
- Lower DNS TTLs to 300 seconds 24–48 hours before: TTL strategy.
- Restore files and databases on the new host and update config files.
- Create email accounts and run a first IMAP sync.
- Test through a hosts-file entry; fix errors before anyone sees them.
- Freeze content changes, take a final database dump and import it.
- Switch DNS records or nameservers.
- Run a second IMAP sync to catch late mail.
Post-migration checks
- The site loads over HTTPS with a valid certificate. AutoSSL issues it once DNS points to MdmHost; run it from cPanel → Security → SSL/TLS Status if needed.
- Forms, logins, checkouts and uploads work, and there are no database connection errors.
- Sending and receiving email works from webmail and from your mail client, and SPF/DKIM pass in cPanel → Email → Email Deliverability.
- Cron jobs are recreated under cPanel → Advanced → Cron Jobs with the new paths (
/home/username/…). - The PHP version in cPanel → Software → MultiPHP Manager matches what the old server used.
- Search Console and analytics still report traffic; the sitemap loads.
- Redirects and canonical URLs behave as before.
When to cancel the old host
Wait at least 7 days after the switch, confirm no traffic or mail still reaches the old server (check its access logs), download one last backup and then cancel.
FAQ
How much downtime should a migration cause?
Done in this order, usually none: the old and new copies both work while DNS propagates.
Should I move the domain at the same time?
Better not. Move hosting first, then the domain later if you want, so only one thing changes at a time.
What gets forgotten most often?
Cron jobs, TXT verification records and email forwarders.