The idea
Downtime during a move happens when the old server is switched off before the new one is ready, or when visitors are sent to the new server before it works. The fix is simple: run both side by side. Copy everything to the new host, test it privately, and only then point your domain at it. Until DNS changes, visitors keep using the old server; afterwards, they get the new one. Nobody sees a gap.
Before you start
Make a list
Write down everything the site depends on, so nothing is forgotten:
- domains, subdomains and add-on domains;
- databases and the users that access them;
- email accounts, forwarders and autoresponders;
- cron jobs, PHP version and any custom PHP settings;
- DNS records that aren't for the website: MX, SPF, DKIM, verification TXT records.
Lower the DNS TTL
TTL (time to live) tells the internet how long to cache your DNS records. A day or two before the move, lower the TTL on your website and mail records to 300 seconds (5 minutes). When you switch, the change then reaches everyone within minutes instead of hours.
Don't cancel the old hosting yet
Keep it running until at least a week after the switch. It's your safety net.
Copy the site
If both hosts use cPanel, this is the easy part: download a full cPanel backup from the old host, which includes files, databases, email and settings, and restore it on the new one. Otherwise, copy the files over SFTP or with rsync, export each database (mysqldump or phpMyAdmin) and import it on the new server, then recreate the database users with the same passwords.
Match the PHP version and important settings like memory_limit to what the site used before. Upgrade PHP after the move, not during it.
Test before you switch
You can open the site on the new server before DNS changes by editing your computer's hosts file. Add a line with the new server's IP address and your domain:
203.0.113.10 yourdomain.in www.yourdomain.in
(The hosts file is C:\Windows\System32\drivers\etc\hosts on Windows and /etc/hosts on macOS and Linux. Use the real IP from your welcome email.) Now only your computer sees the new server. Click through the important pages, log in to the admin area, submit the contact form and place a test order. Remove the line when you're done.
Switch DNS
When everything works, point the domain at the new host: either change the nameservers at your registrar to the new host's, or keep your current DNS and change the A record to the new IP. If you change nameservers, recreate every non-website record (MX, SPF, DKIM, TXT) at the new host first, or email will break.
Thanks to the low TTL, most visitors reach the new server within minutes; some networks can take a few hours. Because the old server is still running, both groups see a working site.
After the switch
- Check that a free SSL certificate has been issued for the domain on the new host, and that the site opens on https://.
- Recreate cron jobs and check that scheduled tasks run.
- Send test emails in both directions.
- Watch the new server's error logs for a day or two.
- In Google Search Console, check for crawl errors in the following days.
- Once everything has been quiet for a week, cancel the old hosting.
Online stores and email: the final sync
A brochure site doesn't change during the move, but a shop does: new orders and customers keep arriving on the old server. For WooCommerce and other stores, copy the database one last time just before the DNS switch, or briefly put the store into maintenance mode while you do. For email, sync each mailbox again right before switching (tools like imapsync copy only new messages), so nothing received in between is lost.
We migrate websites, WordPress sites and cPanel accounts to RapidServer for free. We copy everything, send you a preview link to check, and switch with you when you're happy.
Request a free migration