Move a website to a new VPS: migration checklist

The one principle: DNS flips last

Before moving traffic, test the new site and plan a final data sync. A rollback must preserve any writes received after the switch.

Step 1 — Build the new server completely

Test the new site with a local hosts-file entry before changing public DNS. The new IP is still public; restrict access to unfinished applications.

Create the new VPS in the region you actually want (this is the moment to fix that, not after). Install the stack — for common setups the one-click apps shortcut the boring half — then copy the data: rsync for files, a dump-and-restore for the database.

Step 2 — Lower the TTL a day ahead

Review all DNS records before changing nameservers. Automatic discovery may miss records; keep a copy of the current zone and check website and email after the switch.

Step 3 — Freeze, final sync, flip

Freeze writes on the old site, sync files and restore the final database, then switch DNS. Plan a maintenance window for dynamic sites; DNS caches may still send visitors to the old server.

Step 4 — Watch, then decommission

Monitor both servers after the switch. Reconcile new orders and uploads before rollback or deletion, and keep a tested backup of the final data.

We help you choose, launch and migrate your project. Send us your current setup and requirements; we agree the scope and cost before work starts.