VPS Migration Guide: Moving Your Server with Zero Downtime

Moving a VPS to another server — to switch providers, increase capacity, or switch to a modern panel setup — is a delicate task. If planned incorrectly, it will lead to hours of downtime and data loss. When planned correctly, total downtime decreases to less than 5 minutes and the return path always remains open.

In this guide; We will explain the steps of taking inventory, parallel running, DNS TTL planning, database export/import, SSL automation and rollback in order. The entire flow is illustrated through migration to new VPS with VDS Panel installed, but the method is general.

Preparation: inventory of the current installation

List all resources on the current server before migration. If you miss something, you will experience the surprise “the site is opening but X is broken” after the transition.

• Projects / Sites: What works in which domains? WordPress, static site, Spring Boot, Node.js service, Docker container?
• Databases: PostgreSQL, MySQL, MongoDB, Redis. Version, size and affiliated projects.
• Cron / scheduled tasks: P0 or systemd timers.
• DNS records: A, AAAA, CNAME, MX, TXT, SRV. Export from existing DNS provider.
• SSL certificates: Which domains, Let’s Encrypt or paid?
• Env variables: API key, secret, third party credentials.
• Backup jobs: existing automations such as pg_dump, mysqldump, rsync.

Strategy: parallel execution vs big-bang

You can make the transition in two ways. parallel operation is always recommended.

In the parallel method, two servers work together for a short time. You test the new server on your own while broadcast traffic continues to arrive at the old server. You only change the DNS to the new IP when everything is fine.

Step by step transition

1. 01
   Prepare the new VPS

   Ubuntu 22.04 or 24.04 LTS is a clean server. Minimum 2 CPU, 4 GB RAM. Install VDS Panel with a single command.
2. 02
   Take backup from old server

   Database backup with pg_dump, mysqldump or mongodump. tar or rsync for application files. Cron job list and env variables.
3. 03
   Import databases to the new panel

   VDS Panel generates separate DB + user + password for each project. Import the existing SQL dump with the panel restore tool.
4. 04
   Introduce the code to the new panel

   The cleanest way is to move your projects to the git repository and add them to the panel. Build, env inject, nginx config — all automatic.
5. 05
   Lower DNS TTL

   Reduce the TTL of all A/CNAME records to 300 seconds 24 hours before migration. If this step is skipped, DNS propagation may take up to 24 hours.
6. 06
   Test with hosts file

   Before changing DNS, write the new server IP to local /etc/hosts. Verify all critical flows (login, payment, form submission).
7. 07
   Switch DNS A records to new server

   Point all domains' A records to the new VPS IP. Thanks to the low TTL, it spreads in 5-15 minutes.
8. 08
   Keep old server up for 14 days

   Have the option to roll back DNS if problems arise. You can cancel the old server after 14 days without any problems.

Database migration

VDS Panel offers built-in import support for each database engine:

• PostgreSQL: Take a special format backup with P0, upload it to the panel restore tool. For large tables, pgBouncer connection pool is set up automatically.
• MySQL/MariaDB: Back up with P1, install from the “SQL Import” tab on the panel.
• MongoDB: With P2, bson dump is run through the P3 panel.
• Redis: Usually initialized empty on migration; If there is permanent data, P5 is copied after P4.

Redeploy applications

The cleanest way to move manually installed applications on the old server to VDS Panel is to switch to git push flow:

P0

Then give the GitHub repo URL to VDS Panel. The panel installs the webhook, creates the build pipeline, and asks for env variables. Each subsequent P0 is automatically deployed.

P1

For Java/Spring Boot, JAR upload or Maven/Gradle build options are selected from the panel interface.

SSL certificates

You don’t need to move your old certificates. VDS Panel automatically obtains the new Let’s Encrypt certificate for each domain:

• When the DNS A record points to the new server, the panel starts the HTTP-01 challenge
• Certificate ready in 15 seconds, HSTS and HTTPS redirect automatically
• Automatically renews 30 days before, done without logging in

DNS scheduling

The key to approaching zero downtime is TTL planning.

1. Reduce the TTL of all A/CNAME records from 3600 to 300 24-48 hours before migration.
2. After the entire old TTL period has passed (i.e. 1 hour), the DNS provider will already be replying with the new TTL.
3. Change the A record to the new IP at migration time. In 5 minutes, 95% of the traffic is directed to the new server.
4. If you want to increase the TTL back to 3600 after the migration, wait 14 days (it is important to keep it low during the rollback window).

Rollback plan

Do not turn off your old server for the first 14 days. If a critical problem occurs on the new server:

1. Change A record in DNS back to old server IP
2. Since TTL is 300 seconds, it spreads in 5 minutes
3. Investigate the issue on the new server during this time
4. Fix it and migrate it back to the new server

two-way synchronization for the database is complicated; If you are going to rollback, either do it within the migration window or plan for acceptable data loss. Our article VPS backup strategy helps in RTO/RPO planning.

Post migration checklist

Open the panel on the new server, the old server is still standing:

• All projects are working (HTTP 200, correct content)
• Database connections are active, data is consistent
• SSL certificates green (valid, HSTS on)
• Cron / scheduled jobs have been redefined
• Backup plan active (panel daily encrypted backup)
• Logs are written to the new server
• Pentest scanning is scheduled to run weekly
• Monitoring and alert integration tested

Conclusion

VPS migration is not as difficult a task as it seems; With proper planning total downtime is less than 5 minutes. Parallel execution strategy, low TTL scheduling and 14-day rollback window make migration safe. VDS Panel’s built-in import tools (DB restore, git deploy, automatic SSL) reduce manual steps that can take hours to minutes.

Our contact form is open to discuss your transition scenario. Let us understand your current infrastructure and prepare a special migration plan for you together.