Will my website or email go down during the transfer?

Not if you move DNS to Cloudflare first and copy every record, especially MX and email-auth TXT records, accurately. Because Cloudflare is already serving your zone before the registration transfer begins, only ownership changes hands; resolution never lapses.

Why won't Cloudflare let me transfer my GoDaddy domain?

The two usual blocks are the 60-day ICANN lock after a recent registration or transfer, and the domain still being active-required on Cloudflare's nameservers. Cloudflare Registrar only accepts domains already using Cloudflare DNS, so complete the nameserver switch first.

Do I lose the time left on my current GoDaddy registration?

No. Cloudflare adds one year to your existing expiry date rather than resetting it, so any remaining time you paid GoDaddy for is preserved. Verify the new expiry date once the transfer completes.

How to Transfer a Domain from GoDaddy to Cloudflare

VigilDog Team · September 30, 2026 · 6 min read

Moving a domain off GoDaddy to Cloudflare Registrar gets you at-cost renewals and a cleaner DNS panel, but the order of operations matters, and doing it wrong means downtime or a stuck transfer. The key thing most guides skip: to transfer GoDaddy to Cloudflare, your domain has to be running on Cloudflare's DNS first. Here's the sequence that keeps email and websites live the whole way through.

Before you start: three things that block transfers

A domain transfer can be refused for reasons that have nothing to do with the steps below, so clear these first. ICANN imposes a 60-day lock after a domain is first registered or after any previous registrar transfer, if you just bought or moved this domain, you have to wait it out.

Second, your domain must be unlocked and free of privacy-related contact problems. Third, and easy to forget: the transfer approval email goes to the registrant contact address in WHOIS. If that address is stale or points at an old mailbox, fix it at GoDaddy before you begin, or you'll never see the confirmation link.

Step 1: Move DNS to Cloudflare first

Cloudflare Registrar only accepts domains that are already active on Cloudflare's nameservers. So the real migration starts with DNS, not the registration. In the Cloudflare dashboard, add your site; Cloudflare scans your existing zone and imports the records it can see.

That scan is a best-effort copy, not gospel. Carefully compare the imported records against your live GoDaddy zone, especially MX records and any SPF, DKIM, and DMARC TXT records, which keep your email flowing. A single missing MX record here is how people take their own mail down mid-transfer.

How a domain name resolves to a server

Step 2: Point nameservers and wait for "Active"

Cloudflare gives you two assigned nameservers. Log into GoDaddy, open the domain's DNS/nameserver settings, and replace GoDaddy's nameservers with the Cloudflare pair. This is the moment resolution starts moving to Cloudflare; because you copied the records faithfully in Step 1, visitors and email see no change.

Nameserver changes propagate on their own schedule, usually minutes to a couple of hours, sometimes longer. Cloudflare emails you when the zone flips to "Active." Confirm records are resolving from the new nameservers with an independent DNS checker before moving on. Don't start the registration transfer until the zone is genuinely active.

Step 3: Unlock and grab the authorization code at GoDaddy

Back in GoDaddy, open the domain settings and turn off the domain lock (sometimes labeled "Transfer Lock"). Then request the authorization code, also called the EPP code or transfer key. GoDaddy typically emails it or shows it after a short delay.

If GoDaddy applied domain privacy, some transfers go smoother with privacy temporarily disabled, because it exposes the registrant email the approval flow relies on. Copy the auth code exactly; it's case- and character-sensitive, and a stray space is a common reason a transfer request is rejected as invalid.

Step 4: Initiate the transfer in Cloudflare

In the Cloudflare dashboard, go to Registrar for your (now active) domain and start the transfer. Paste the authorization code from GoDaddy and confirm the contact details. Cloudflare charges one year of registration at wholesale cost, and, importantly, that year is added on top of your current expiry, so you don't lose the time you already paid GoDaddy for.

After you submit, watch for the approval email at the registrant address and click through to authorize it. Transfers can complete quickly but ICANN allows the losing registrar up to five days, so don't panic if it isn't instant. During this window your site and email keep working, because DNS is already served by Cloudflare, only the registration ownership is changing hands.

After the transfer: verify and re-arm renewals

Once Cloudflare shows the domain as transferred, do a final pass. Confirm every record survived, re-check MX and your email-auth TXT records against a DNS records reference if anything looks off, and confirm the new expiry date reflects the extra year. Then set auto-renew and a valid payment method in Cloudflare, since renewal settings do not carry over from GoDaddy.

The quiet risk after any registrar move is that a renewal or expiry slips through the cracks while your attention is elsewhere. VigilDog's domain and DNS monitoring tracks expiry dates and watches for unexpected DNS drift across every domain you manage, so a botched auto-renew or a dropped MX record pages you instead of surprising you. You can also spot-check the new expiry any time with our domain expiry checker.