How to migrate a VPS without downtime
A step-by-step VPS migration plan using incremental synchronization, testing, DNS or proxy cutover, validation and rollback.
Updated 7/29/20264 min read
Preparation
Record services, versions, ports, scheduled jobs, secrets, disks and external dependencies. Lower DNS TTL ahead of time when the cutover depends on an address change.
- Verified backup
- Equivalent capacity
- Certificates and firewall
- Window and owners
Synchronization and testing
Copy static data first with rsync or an appropriate alternative. Use replication or a consistent backup for databases. Test with a temporary hostname or local hosts entry before sending public traffic.
Cutover and rollback
Pause writes or use a brief maintenance window, run the final sync and switch the proxy or DNS. Watch errors, latency and data. Revert traffic when a predefined acceptance criterion fails.
Frequently asked questions
Can zero downtime be guaranteed?
Not for every system. Replication and load balancing can avoid a visible interruption, while stateful applications or rigid dependencies may still need a brief window.
When can the old server be shut down?
After validating data, traffic, backups, scheduled tasks and stability for an agreed period. Keep it available while rollback is still required.