How to Migrate a cPanel Website Without Downtime

Why migrations cause downtime (and how to avoid it)

Downtime during a host move almost never comes from copying files. It comes from switching DNS too early or without planning. People change their domain's records to point at a half-finished new server, or they change DNS and then discover a stale TTL keeps sending visitors to the old box for hours. Both are avoidable.

The no-downtime approach rests on two ideas:

• Build in parallel. The new server is fully prepared and tested while the old server keeps serving every visitor. Nothing is switched until the new site is proven.
• Make the switch fast. By lowering DNS TTL ahead of time, the final cutover reaches all visitors within minutes instead of hours, so the handoff is effectively seamless.

The step-by-step method

1. Lower your DNS TTL

   A few days before the move, drop the TTL on your domain's A record (and MX records for mail) to 300 seconds. TTL tells the internet how long to cache your DNS. A low TTL set in advance means that when you finally switch records, the change propagates in minutes. Do this first, because the old (high) TTL has to expire from caches before the low value takes effect.

2. Copy files and database to the new host

   Create the account on the new cPanel server and copy the website files and databases while the old site stays live and untouched. A cPanel-to-cPanel transfer or a full cPanel backup restore preserves file permissions, databases, cron jobs, and email structure in one move.

3. Recreate email accounts and forwarders

   Recreate every mailbox, forwarder, and autoresponder on the new server before cutover, matching passwords where possible so mail clients keep working. Email is where most migrations lose data, so treat it as carefully as the website itself.

4. Preview on a temporary URL

   Before touching DNS, load the site on the new server using a temporary URL or a local hosts-file entry that points the domain to the new server's IP for you only. Click through pages, forms, logins, and checkout. Fix anything broken now, while real visitors are still safely on the old server.

5. Do a final sync

   Just before cutover, sync anything that changed since the first copy: new orders, new blog posts, new uploads, and recent mail. For a busy site, briefly pausing new writes (or putting the site in maintenance mode on the old server for a few minutes) guarantees the two copies match.

6. Switch DNS to the new server

   Point the A record (and MX records) at the new server. Because the TTL is low, visitors move across within minutes. Leave the old account running: during propagation, some requests still resolve to it, and you want those served correctly rather than failing.

7. Monitor, then decommission

   Watch traffic, mail, and error logs on both servers for 24 to 72 hours. Once everything has moved and nothing is hitting the old server, restore the TTL to a normal value and decommission the old account. Keep a backup as a rollback option until you are completely confident.

Email migration: the part people underestimate

Websites are stateless and easy to copy. Mailboxes are live and keep receiving messages throughout the move. Two rules keep email safe: recreate all accounts on the new server before cutover, and run both servers in parallel during propagation so a message delivered to either one is captured. After DNS has fully moved, do a final IMAP sync to copy any messages that landed on the old server during the transition.

Validation and rollback

Before you call the migration done, validate the essentials on the new host: the homepage and key pages load, forms and logins work, SSL is valid (no certificate warnings), email sends and receives, and scheduled tasks (cron) still run. Because the old account stays live and untouched until you decommission it, rollback is always one low-TTL DNS change away. That safety net is the whole point of building in parallel.

How Ultra does it for you, free

Free website migration is included with annual and longer plans at Ultra Web Hosting. Our technicians run exactly this method: they copy your cPanel account to our servers, recreate mail, plan the TTL, test on a temporary URL, and coordinate the cutover, so you get a no-downtime move without doing the work yourself. You can start a free migration or read how our free transfer works.