Migrating your VPS with zero downtime: the complete guide
Every week, dozens of customers join us from other providers. Here is the method our support team uses for cutover-free migrations, refined over more than 3,000 assisted migrations.
Step 1 — Provision and cold-sync
Deploy the new VPS with the same OS version. Sync data a first time while the service is still live on the old server:
rsync -avz --delete --exclude=/proc --exclude=/sys \
-e ssh / old-server:/backup/Step 2 — Lower the DNS TTL
48 hours before cutover, drop your record TTL to 300 seconds. It's the most underestimated lever of a clean migration.
Step 3 — Hot sync and cutover
1. Switch the application to read-only (or maintenance) on the old server. 2. Final sync: rsync plus final database replication (pg_basebackup, mysqldump --single-transaction, or primary/replica replication). 3. Flip the DNS. With the low TTL, 95% of clients reach the new server within 5 minutes. 4. Keep the old server read-only for 48 hours as a safety net.
Classic pitfalls
- TLS certificates: reissue them on the new server before cutover.
- Message queues: drain or migrate them last — they're volatile.
- Outbound IPs: if partners whitelist your IP, warn them ahead of time.
Need a hand?
Our team performs migrations free of charge on Quantum and Singularity plans. Reach out via the contact page.