Moving a VPS: A checklist for minimal downtime

Inventory comes before copying

List domains, services, ports, scheduled jobs, databases, users, certificates and external dependencies. Record which applications modify files and which data lives in a database. This inventory becomes your acceptance checklist. A working login does not prove that a background job or webhook moved correctly.

Prepare the new server in parallel

Install supported operating-system and package versions, configure users and the firewall, then transfer an initial copy of the data. Keep credentials in a secret store or tightly permissioned configuration files, not shell history. Test through a local hosts-file entry or temporary subdomain before sending public traffic to the new machine.

Switch DNS and changing data carefully

Lower the DNS TTL well before the move. Near cutover, put write-heavy applications into maintenance mode where possible, synchronize changes since the initial copy and export the database again. Then update the DNS records. Keep the old environment available during propagation but prevent it from accepting new writes.

Verify the service, not just the homepage

• Test login, uploads, email delivery and important background jobs.
• Review logs for missing files, connection errors and old paths.
• Move TLS renewal, backups and monitoring to the new target.
• Retire the old server only after DNS caches expire and data is verified.

Rollback belongs in the plan

Decide in advance which failures trigger a rollback and which writes could be lost. A snapshot immediately before cutover can shorten recovery, but it is not a replacement for an external backup. Schedule the move for a quiet period and communicate it early.

Use a test server to rehearse the migration or choose a destination from our server packages.