Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Migration

VPS migration checklist: move a server without losing the rollback path

Published August 2026 · 2 min read · Updated 2026-09-05

A VPS migration checklist should describe the server as a set of services and state, not a disk image. The destination must reproduce networking, users, packages, application processes, data, scheduled jobs, DNS, certificates, and recovery behavior before public traffic moves.

Inventory services and dependencies

List listening ports, systemd units, containers, databases, users, cron/timers, firewall rules, mounts, attached storage, TLS certificates, DNS records, reverse DNS, external APIs, secrets, and outgoing mail identity. Record versions for anything with compatibility risk.

Find hard-coded IP addresses and provider-specific metadata before they silently fail at the destination.

Build the destination without changing traffic

Install the target operating system and packages, restore configuration and data, recreate users and keys, apply firewall policy, and test via a temporary hostname or hosts-file mapping. Verify application writes and background jobs, not only the homepage.

Keep the old VPS running while the new environment is still being proven.

Plan the final data synchronization

Databases, uploads, queues, and mail can change after the first copy. Decide on replication, a maintenance window, read-only mode, or a final sync so writes are not silently left behind.

Lower DNS TTL before cutover when appropriate, but remember TTL does not synchronize application data.

Cut over with rollback criteria

Change the minimum DNS or routing needed, monitor both environments, test from external networks, and keep the source until traffic, writes, scheduled jobs, and logs confirm the destination is healthy.

  • Inventory all services and state.
  • Test destination privately.
  • Synchronize changing data.
  • Retain source until verification.

Next step

Plan a VPS move across data sync, IP and DNS changes, certificates, services, validation and rollback so cutover does not depend on memory or luck.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move