Skip to content

Moving from a VPS to a dedicated server: a migration checklist

Plan it, build it, copy it, switch it, and keep the old server until you're sure. A practical checklist for a move with minimal downtime.

HQserv teamPublished 2 min read

Migrating to a dedicated server sounds risky, but most of the work happens before your visitors notice anything. The trick is to build and test the new server while the old one is still live, then switch over in a few minutes.

1. Take stock of what you run

  • List every website, application, database, cron job and background worker.
  • Note software versions: operating system, web server, PHP or other runtime, and database.
  • Record your DNS records, SSL certificates and email settings.
  • Write down current resource use so you can size the new server. Our guide to choosing dedicated server specs helps here.

2. Lower your DNS TTL

Ahead of the move, lower the TTL on the DNS records you'll change, for example to 300 seconds. Do it at least one full old-TTL period in advance; a day or two before is usually safe.

When you switch, visitors will reach the new server within minutes instead of hours.

3. Set up and harden the new server

  • Install the operating system and updates. With IPMI you can do this remotely, even before networking is configured.
  • Create user accounts with SSH keys and disable password logins for root.
  • Configure the firewall to allow only the ports you need.
  • Install the same software versions you run today. Upgrade later, not during the move.
  • Set up monitoring and backups before anything goes live.

4. Copy your data

Make an initial full copy while the old server is still serving traffic. For files, rsync is the usual tool: run it once to copy everything, then again later to transfer only what has changed.

For databases, take a consistent dump, or set up replication so the new server stays in sync until you cut over.

5. Test before you switch

Point your own computer at the new server by editing your hosts file. You can then browse the real sites on the new server without changing public DNS.

Check logins, forms, payments, outgoing email, scheduled tasks and file uploads.

6. Cut over

  1. Put the site into maintenance mode, or pause writes on the old server.
  2. Run a final rsync and database sync.
  3. Update your DNS records to the new IP addresses.
  4. Watch the logs and monitoring on both servers as traffic moves across.

With a low TTL and a final sync that only moves recent changes, downtime is usually measured in minutes.

7. Keep a way back

Don't cancel the old server on migration day. Keep it running for at least a week, so you can point DNS back if something unexpected turns up. Once you're confident, take a final backup and decommission it.

Moving to HQserv

HQserv dedicated servers are online within 24 hours of purchase and come with IPMI for remote installs. If you get stuck partway through, our engineers are available 24/7. Talk to us about your migration.

All articles