Migration · 7 min read
A server migration checklist for a safer cutover
A successful migration is planned around verification and rollback, not just copying files to a new machine.
Document the current service
List applications, domains, DNS records, certificates, databases, scheduled jobs, integrations, firewall rules, IP allowlists, mail routing, and monitoring. Record versions and configuration decisions that are easy to forget under pressure.
Build and test before switching traffic
Set up the target server, harden access, install dependencies, copy data, and test through a private hostname or hosts-file override. Verify background jobs, uploads, payment flows, email, performance, and observability before changing DNS.
Make backups and a rollback plan
Create a restorable backup before the final sync. Define the exact condition that triggers rollback, the person who can make that decision, and how you will return traffic to the original system. Keep the old server available until the new environment is stable.
Use a controlled cutover
Lower DNS TTL in advance where appropriate, schedule a maintenance window, perform a final data sync, and watch error rates after traffic moves. Monitor for at least one normal business cycle before declaring the migration complete.