A dedicated server migration differs from a cloud move in three ways: the new machine has a new IP address, copying hundreds of gigabytes takes real time, and hardware details such as disks and remote management must be set up from scratch. The sequence below keeps the old server serving until the new one has been tested.
Before you order the new server
- List software versions, services, cron jobs, firewall rules, IP-based allowlists and reverse DNS entries.
- Measure the data size. On a fully used 1 Gbit/s link one terabyte takes about two and a quarter hours in theory; plan for several times that.
- Decide the disk layout and RAID level for the new machine.
Runbook
- Install and secure. Operating system, SSH keys, firewall, updates. See the first 24 hours.
- Lower the DNS TTL a day before the cutover.
- Initial copy.
rsyncthe data and load the database while the old server keeps serving. - Test on the new IP. Use the hosts file, run login, checkout and background jobs.
- Update IP-bound items. Firewall allowlists at partners, payment provider callbacks, mail server reverse DNS and SPF if the sending IP changes.
- Freeze and final copy. Pause writes briefly, repeat the sync and the database copy.
- Switch DNS. Change A and AAAA records and watch both servers’ logs.
- Parallel run. Keep the old server online one to two days, with its cron jobs stopped.
- Decommission. Wipe disks securely before the old hardware is returned or reused.
What is special about dedicated hardware
| Item | Why it matters |
|---|---|
| New IP address | Everything bound to the old IP must be updated |
| Reverse DNS and mail | A new sending IP needs rDNS and a matching SPF record |
| Remote management | Set it up and secure it before you need it |
| Disks and RAID | Check health and layout before data lands on them |
| Secure wipe | Customer data must not leave on returned hardware |
The same ideas for virtual servers are in cloud migration with zero downtime. Choose the target in dedicated server vs cloud server and compare machines on the dedicated server page.
Frequently asked questions
Can I keep the old IP?
Usually not between machines. Plan for a new IP and update everything that depends on the old one.
How long does the copy take?
It depends on data size and link speed. Measure a sample transfer and extrapolate, then add margin.
What about email?
If mail runs on the server, move it deliberately and update rDNS and SPF. If it runs elsewhere, leave MX alone.
When can I cancel the old server?
After one to two days of clean logs and a verified backup of the new one.
