Low-Cost VPS Migration: Moving Hosts for Under $5 Without Downtime

Migrating to a cheaper VPS is usually a $0–$5 project if you avoid managed migration services that charge $30–$100 per site. The entire cost is optional: a second IP address for DNS testing, or a short overlap period where you run two plans at once. This tutorial walks through a migration that keeps your site online the whole time, using free tooling.

The zero-downtime principle

Downtime happens when you move DNS before the new server is ready, or when you copy data while users are still writing to the old one. Solve both by lowering DNS TTL a day early and copying data twice — once to prime, once to sync the delta. The final switch then takes minutes, not hours.

Step 1: Prepare DNS (24–48 hours ahead)

• Lower your A record TTL to 300 seconds (5 minutes) at least a day before the move.
• Note current IPs, MX records, and any TXT records for verification.
• If your plan includes a free IP on the new host, you do not need to buy anything yet.

Step 2: Prime the new server

Install the same stack on the destination, then transfer data synchronously. rsync is the right tool because it copies only changes on later runs:

• rsync -avz --delete /var/www/ user@new-host:/var/www/ for files.
• mysqldump --single-transaction db | gzip > db.sql.gz then pipe it over SSH, or use the same rsync route.
• Copy config files, cron jobs (crontab -l) and systemd units explicitly — these are the most commonly forgotten items.

Step 3: Test before switching

Do not cut over on hope. Verify the new box responds correctly on its temporary IP by overriding DNS locally:

• Add a line to your local /etc/hosts mapping your domain to the new IP.
• Walk through your key pages, forms and logins.
• Check curl -I https://yourdomain for the correct TLS certificate before DNS changes.
• Confirm email still sends (if you host it) so the new IP is not on a blacklist.

Step 4: Final sync and DNS switch

1. Put the old site in read-only mode or briefly pause writes.
2. Run the rsync and database copy one final time — only the delta, so it is fast.
3. Update the A record to the new IP.
4. Watch traffic arrive on the new server via access logs.
5. Keep the old server running for 48–72 hours as a rollback path.

What it actually costs

Item	Typical cost	Necessary?
Managed migration service	$30–100	No
Extra IPv4 for testing	$0–2/mo	Optional
Overlap period (two servers)	One plan’s monthly cost	Recommended, 3 days
rsync / mysqldump	$0	Yes
DNS changes	$0	Yes

A three-day overlap on a $5 plan costs about $0.50. That is the entire realistic budget for a zero-downtime move, provided you skip the paid migration add-on. If your destination provider bundles free migration assistance anyway, take it — but you rarely need it.

Common migration mistakes

• Moving DNS too early. Users hit a half-configured server and see errors.
• Forgetting cron and systemd. Backups and scheduled tasks silently stop.
• Ignoring file permissions. rsync as root can carry ownership your web user cannot read.
• Skipping the delta copy. Any content written between the first copy and the switch is lost.
• Cancelling the old plan too soon. Keep it 48–72 hours as insurance.

Done in this order, a host change is a routine maintenance task rather than a risky weekend project. The savings compound too: moving from a $12 plan to a $5 plan with equivalent specs saves $84 a year. To find a destination with comparable resources at a lower renewal rate, review the budget VPS plans and their included specs here, and check the renewal pricing overview before you commit so the saving survives year two.

Verifying the move succeeded

After 72 hours, confirm the old server received no traffic, that backups on the new host are running, and that your monitoring still reports green. Then cancel the old plan. A migration is only finished when the rollback path is no longer needed — and when the monthly bill reflects the cheaper plan you actually wanted.