Server Migration Checklist: Websites, Databases, DNS and Email
List websites, databases, PHP versions, cron jobs, SSL certificates, DNS zones, email accounts, forwarding rules, storage usage, application dependencies and control-panel settings. Migrations fail when hidden dependencies are discovered too late.
1. Inventory the Existing Environment
List websites, databases, PHP versions, cron jobs, SSL certificates, DNS zones, email accounts, forwarding rules, storage usage, application dependencies and control-panel settings. Migrations fail when hidden dependencies are discovered too late.
2. Create and Verify Backups
Take current backups before changing production systems. For critical workloads, verify that backups can actually be read or restored. A backup that has never been tested should not be treated as a guaranteed recovery plan.
3. Prepare the Destination Server
Configure the operating system, web server, PHP/runtime versions, database server, security controls, control panel and required extensions before moving production data. Common environments may use cPanel/WHM, Plesk, DirectAdmin, CyberPanel, CWP or a manually managed stack.
4. Transfer Websites and Databases
Move files and databases while preserving permissions, ownership and configuration. Large or frequently changing applications may require a final synchronization or maintenance window to avoid losing changes made during the migration.
5. Plan Email Migration
If email is hosted on the same infrastructure, inventory mailboxes, aliases, forwarders, quotas and DNS authentication. SMTP, IMAP, MX, SPF, DKIM and DMARC settings may need to be recreated or updated. Email should be tested independently from the website.
6. Update Domains and DNS Carefully
Review nameservers and individual records before changing them. Lowering TTL in advance can help some migrations, but DNS propagation is not instantaneous or identical for every resolver. Keep the old server available during the transition where practical.
7. Verify SSL and Application Configuration
Issue or install certificates, confirm HTTPS redirects, update environment variables and test database/API connections. Check hard-coded URLs, filesystem paths and allowed IP addresses that may still reference the old environment.
8. Post-Migration Verification
Test public pages, forms, logins, dashboards, scheduled tasks, outgoing email, incoming email, APIs, payment flows and backups. Monitor logs, resource usage and uptime before decommissioning the old server.
