Post-Migration Checklist
The data migration is complete — now it's time to bring the target server into production, verify all services, and make the switch seamless for your users.
Follow these steps in the order listed. Only update DNS records once the target server is fully tested — this prevents downtime for your users.
Phase 1: Test the target server (before DNS change)
Test everything via the target server's IP address before making any DNS changes:
☐
Web server accessible
Open
http://TARGET_SERVER_IP in a browser and verify your websites load correctly.☐
Database connection works
Check that applications connect to the database correctly — watch for connection errors in the logs.
☐
Email sending and receiving
Send a test email and verify it is delivered correctly.
☐
Cron jobs and scheduled tasks
Verify all cron jobs (Linux) and scheduled tasks (Windows) are configured correctly and running.
☐
SSL certificates
Verify certificates are installed correctly. Let's Encrypt certificates need to be reissued after migration.
☐
Firewall rules
Verify all required ports are open and no unintended ports are publicly accessible.
Phase 2: Update DNS
Once the target server is fully tested, update your DNS records:
☐
Update A record to new IP
Change the A record for your domain to the target server's IP. With a low TTL the change takes effect within minutes.
☐
Check MX records
If email runs on the new server, update MX records accordingly.
☐
Update reverse DNS (PTR)
Set the PTR record for the new IP in the PowerPanel — important for email deliverability.
☐
Wait for DNS propagation
Wait for DNS changes to fully propagate — depending on TTL this can take from a few minutes up to 48 hours.
Phase 3: Renew SSL certificates
After the DNS change, Let's Encrypt certificates need to be reissued as they depend on domain reachability:
Terminal
certbot renew --force-renewal
For Plesk: certificates can be reissued in the Plesk panel under Websites & Domains → SSL/TLS Certificates.
Phase 4: Decommission the old server
Keep the old server running for a few days before cancelling or wiping it:
☐
Create a final backup of the old server
Make one last complete backup of the source server before deleting it.
☐
Monitor for at least 3–5 days
Keep the old server as a fallback option until you are confident everything on the new server is working correctly.
☐
Cancel or reinstall the old server
Cancel the old server in the PowerPanel or reinstall it for another purpose.