How to Transfer Your Domain to a New Host Without Downtime

Moving your domain or website to a new host sounds risky — nobody wants their site or email to go dark during the switch. The good news: with the right order of operations, you can transfer with zero downtime. The whole trick is preparing everything on the new host before you flip the switch, so visitors never hit an empty server. This guide walks through the safe sequence step by step.

We'll cover two related but separate things people often confuse: transferring your hosting (where your website files live) and transferring your domain registration (who your domain is registered with). You can do either or both.

Planning a move to BabalCloud? Our domain transfer process includes a free 1-year extension and is designed for a clean, no-downtime cutover.

First, understand what you're actually transferring

Two different things live under "moving my website," and mixing them up is where downtime happens:

• Hosting migration — copying your website's files and databases from the old server to the new one, then pointing your domain at the new server.
• Domain registrar transfer — moving the domain registration itself from one company to another (e.g. from GoDaddy to a new registrar). This changes who you renew with, not where your site is hosted.

Most "transfers" are really hosting migrations — you keep your domain where it is and just change hosts. We'll cover both, starting with the one that carries downtime risk.

The golden rule for zero downtime

Never delete or cancel anything on the old host until the new host is fully live and tested. Set up the new server completely, verify it works, then switch DNS, then (days later) cancel the old account. Keep both running in parallel during the cutover. This single principle prevents almost all transfer downtime.

Part 1: Migrating your hosting with no downtime

Step 1 — Set up your site fully on the new host first

Before touching DNS, get your website working on the new server:

1. Copy all files (via cPanel's Backup Wizard, FTP, or a migration tool) to the new host.
2. Export your database from the old host and import it on the new one.
3. Recreate email accounts on the new host if you host email there.
4. Update any config files (like WordPress's wp-config.php or Laravel's .env) with the new database credentials.

Many hosts, including BabalCloud, offer free migration and will move a cPanel account for you — ask before doing it manually.

Step 2 — Test on the new server before switching

Preview your site on the new host without changing DNS by editing your computer's hosts file to point your domain at the new server's IP. Load the site, click through pages, test forms and logins. Fix anything broken now, while the public still sees the old site.

Step 3 — Lower your DNS TTL in advance

A day or two before the switch, log in to wherever your DNS is managed and lower the TTL (time to live) on your records to 300 seconds (5 minutes). This makes the eventual change propagate fast instead of taking hours. Raise it back afterward.

Step 4 — Point DNS at the new host

Now update your domain's DNS — either change the nameservers to your new host's, or update the A record to the new server's IP. Because both servers are running identical sites, visitors seamlessly land on whichever they resolve to during propagation. No blank pages, no downtime.

Step 5 — Wait, verify, then decommission

DNS propagation typically completes within minutes to a few hours (thanks to the lowered TTL). Confirm the new server is serving traffic, then wait a few days before canceling the old account — just in case. Only cancel once you're certain everything, including email, works on the new host.

Part 2: Transferring the domain registration

If you also want to move the domain registration to a new registrar, here's the standard process. This does not affect your live website as long as DNS stays configured correctly.

1. Unlock the domain at your current registrar (remove the "transfer lock"/"registrar lock").
2. Get the EPP/Auth code (also called the transfer key or authorization code) from your current registrar.
3. Disable WHOIS privacy temporarily if it blocks the transfer.
4. Start the transfer at the new registrar and enter the EPP code.
5. Approve the transfer — you'll get a confirmation email; approving it speeds things up.
6. Wait — registrar transfers can take up to 5–7 days by design (an ICANN safeguard). Your site stays online the whole time as long as DNS is unchanged.

Important: before transferring a registration, note down all your current DNS records. Some transfers can reset DNS to registrar defaults, which would cause downtime — so have your records saved to re-enter if needed.

.com.np domains work differently: the registration stays with Nepal's registry (register.com.np). You don't transfer the registration — you just repoint the nameservers to your new host, which is the Part 1 process above.

Don't forget email

Email is the most commonly forgotten casualty of a transfer. If you use domain email ([email protected]):

• Recreate all mailboxes on the new host before switching DNS.
• Download or migrate existing mail so nothing is lost.
• After the DNS switch, confirm your MX records point to the correct mail server.
• Send a test email in and out once the cutover completes.

Losing email access mid-transfer is worse than a few minutes of website downtime — plan for it explicitly.

Frequently asked questions

Will my website go down during a domain transfer?

Not if you do it in the right order. Set up and test the site on the new host first, keep the old one running, then switch DNS. Because both serve the same content during propagation, visitors experience no downtime.

How long does a domain transfer take?

Repointing DNS to a new host takes minutes to a few hours. Transferring a domain registration between registrars can take up to 5–7 days due to ICANN rules — but your site stays online throughout if DNS is unchanged.

What is an EPP code?

An EPP (or Auth) code is a password from your current registrar that authorizes moving your domain registration to a new one. You get it from your existing registrar and enter it at the new one.

Do I lose my emails when I switch hosts?

Only if you don't plan for it. Recreate mailboxes and migrate existing mail to the new host before switching DNS, then verify your MX records point to the right server.

Can I transfer hosting without transferring the domain?

Yes — and it's the most common case. You keep your domain where it's registered and simply update its DNS/nameservers to point at the new host.

How do I move a .com.np domain to a new host?

You don't transfer the registration (it stays with register.com.np). You just log in there and repoint the nameservers to your new host, then follow the zero-downtime migration steps above.

Summary

Zero-downtime transfers come down to one habit: build and verify on the new host before you switch DNS, and keep the old host running until you're sure. Lower your TTL ahead of time, don't forget email, and remember that hosting migration and registrar transfer are two separate things.

If you'd rather not manage it yourself, BabalCloud's transfer service handles the migration for you — with a free 1-year extension and a cutover designed to keep your site and email online the entire time.