How to Migrate Your Website to a New Host Without Downtime

Before You Migrate: Back Everything Up

Before touching anything, back up your website files, your database (if your site uses one), and export your email accounts and their mail. This is your safety net if anything on the new host doesn't behave as expected.

Step 1: Set Up the New Hosting Account First

Create your new cPanelA popular web-hosting control panel for managing sites, email, databases, and files through the browser. account before you touch DNSThe Domain Name System — the internet's directory that translates domain names into the IP addresses of servers. at all. See our hosting page for plan options. Keeping the old host live throughout this process is what makes a zero-downtime migration possible.

Step 2: Move Files and the Database

Upload your website files to the new account and import your database if you have one. Check for any hardcoded URLs or configuration values that reference the old server, and update them to match the new environment.

Step 3: Test on a Temporary URL

Most hosts provide a temporary domain, or you can edit your local hosts file, to preview the site on the new server before it's publicly live. Confirm everything works: pages load, forms submit, and images display, before moving on.

Step 4: Move Email

Recreate your mailboxes on the new host and import the mail you exported earlier. Do this before cutover so mail isn't lost in transit once DNS changes.

Step 5: Switch DNS Last

Only point your domain's DNS at the new host once everything above is verified working. DNS changes can take a few hours to propagate fully, so expect a short window where some visitors still reach the old server, which is exactly why keeping the old host running until propagation finishes matters.

Understanding DNS Propagation

DNS records are cached, not looked up fresh every time. Internet service providers and individual devices store, or "cacheA temporary store of already-fetched data, kept so it can be reused quickly instead of fetched again.," a domain's DNS answer for a period set by its TTLTime To Live — how long, in seconds, a DNS record may be cached before it's looked up fresh again. (time to live) value, often anywhere from a few minutes to 48 hours depending on how it's configured. That's why a domain doesn't switch hosts instantly everywhere at once: some visitors see the new site right away, while others keep reaching the old one until their cached record expires.

A practical trick: lower your DNS TTL to a short value, like 5 or 10 minutes, a day or two before a planned migration. Once the old, longer TTL has expired everywhere, the actual cutover propagates far faster, often within minutes instead of hours. See our full guide to DNS propagation for more on how to check its progress and what to do if a domain still isn't resolving correctly after the expected window.

After Migration: What to Check

Once DNS has switched, verify the essentials before considering the migration finished:

• The site loads correctly for visitors on different networks, not just your own.
• Forms submit successfully, since a hardcoded URL from the old server is a common thing to miss.
• Email sends and receives normally on the new host.
• Old hosting stays active for a few more days as a safety net, even after everything above checks out.

Once you're confident everything has fully switched over, and it's stayed that way for a few days, it's safe to cancel the old hosting account.