Downtime during a migration usually happens when the domain is pointed at the new server before the new server is ready. The fix is to copy everything first, test it, and switch DNS last.
Prepare the New Account First
- Set up your new cPanel account and recreate the site there while the old site stays live.
- Upload all files and import databases without touching your domain's DNS.
- Create matching email accounts on the new server.
Test Before Switching
Preview the migrated site using its temporary URL or by editing your local hosts file so only your computer sees the new server. This lets you verify the site without affecting visitors.
# Example hosts entry for previewing
203.0.113.10 example.co.ke www.example.co.ke
Lower TTL Ahead of Time
A day or two before the cutover, reduce your domain's DNS TTL (time to live) to a low value such as 300 seconds. A lower TTL means resolvers refresh records faster, shrinking the window where some visitors hit the old server.
Switch DNS and Monitor
- Update your nameservers to ns1.nairohost.site and ns2.nairohost.site, or update A records to the new IP.
- Keep the old hosting active for at least 48 hours so anyone still on cached DNS sees a working site.
- Watch for broken links, missing images, and email delivery on the new server.
Avoid Data Loss During Cutover
If your site collects new data such as orders or form submissions, freeze content changes during the switch or export and re-import any records added after the initial copy. This prevents new entries from being stranded on the old server.
With both servers serving the same content during propagation, visitors experience no interruption regardless of which server their DNS resolves to.