- Checked
- 2026-11-14
Moving a website to a new server, in a safe order
A move goes wrong in the same few places: DNS that takes a day to change, a database copied while people were still writing to it, mail records forgotten, and an old server switched off too early. Do it in this order and each of those is handled before it can bite.
Before anything moves
Write down what runs where: the web server and its config, the language runtime and its version, the database, scheduled jobs, files users have uploaded, and where mail for the domain is handled. A cron job nobody listed is the thing that silently stops after the move.
Lower the DNS TTL a day ahead
The TTL on the domain's A record says how long resolvers keep the old address. If it is a day, some visitors will see the old server for a day after you switch. Lower it to five minutes at least a day before the move, so the switch takes minutes.
Copy, then test before the switch
Copy the files and a dump of the database to the new server and set it up there. Then test it without touching DNS: put the new address for your domain in your own computer's hosts file and browse the site as if it were live. Log in, submit a form, check a page that writes to the database.
The switch
- Stop writes on the old server, with a maintenance page or by making the app read-only.
- Copy the database and the uploaded files one last time.
- Change the DNS record to the new server.
- Watch the new server's logs as traffic arrives, and check the certificate is issued for the domain there.
- Raise the TTL again once everything is settled.
After the move
Keep the old server running, unchanged, for a week. If something was missed, it is still there to copy. Check that mail still flows if the domain's MX or SPF records named the old server, and that scheduled jobs and backups now run on the new one.
Having it done
Our server migration is a fixed $109 for one site or one app: planned in order, tested on the new server before the switch, switched over and verified. A move with several apps, databases, DNS and mail together is the complex migration at $259. Minimal downtime means as little as the move can be done in, not a promise of zero.
Questions people ask
- Can a website be moved with zero downtime?
- A static site can, nearly. A site with a database usually needs a short pause in writes for the final copy. Lowering the DNS TTL a day ahead keeps that pause to minutes.
- Will moving servers affect my email?
- Only if mail runs on the old server or the domain's MX or SPF records point at it. Check those records before the move, and move or update them on purpose.
- How long should I keep the old server?
- A week, unchanged. It costs little and it is the only copy of anything the move missed.
- What does a server migration cost?
- $109 for one site or app, $259 for a move with several apps, databases, DNS and mail. Fixed, and confirmed with the scope before work starts.
More server help
- DNS not resolving or still on the old server
- Renewing a Let's Encrypt certificate
- 403 Forbidden on nginx or Apache
- Error establishing a database connection
- Server down: what to check first
- 502 Bad Gateway on nginx
- 504 Gateway Timeout
- WordPress white screen or critical error
- Too many redirects
- Disk full: no space left on device
- SSL certificate expired: the fix
- Email from the server going to spam
- Website hacked: the first steps
- Linux server hardening checklist
- All server help guides
