How to Transfer Your Domain from GoDaddy to Cloudflare
GoDaddy is the world’s biggest registrar — and one of the most expensive to stay with. If you’re moving to Cloudflare Registrar, you’re trading GoDaddy’s renewal prices and upsell maze for domains sold at wholesale cost. The catch: Cloudflare requires your DNS to run through them first. Here’s the full process, in order.
Before you start
- Your domain must be older than 60 days, and not transferred in the last 60 days. This is an ICANN rule that applies to every registrar — no exceptions.
- You need access to your GoDaddy account. If you’ve lost access, recover it first. You can’t transfer a domain you can’t log into.
- Plan for the DNS move. Unlike a Porkbun transfer, Cloudflare won’t take your domain until your DNS is already on Cloudflare. Budget an extra day for nameserver propagation.
Step 1: Deal with GoDaddy’s protection add-ons
This is the step that trips people up. GoDaddy sells tiered “Domain Protection” plans — Basic (free privacy), Deluxe, and Ultimate. The paid tiers add ownership protection and security features, and they can block or complicate transfers.
- Log into GoDaddy → My Products → Domains → click your domain.
- Open Domain Settings and look at your protection plan.
- If you’re on a paid protection plan, downgrade to Basic (free) before attempting the transfer. The ownership-protection features on higher tiers can hold up the auth-code process.
- While you’re here, cancel any add-ons you don’t want renewing — email forwarding bundles, “Website Protection,” anything attached to the domain.
You don’t need to cancel the domain itself. Just strip it down to a plain domain with basic privacy.
Step 2: Unlock the domain
- In the same Domain Settings page, find Domain lock.
- Toggle it OFF. GoDaddy may ask you to confirm — do it.
A locked domain can’t be transferred anywhere. This takes effect immediately.
Step 3: Get your authorization code
- In Domain Settings, look for Get authorization code (sometimes labeled “Transfer domain away from GoDaddy”).
- GoDaddy emails the code to the registrant contact on file. Check that the email address on your domain is one you can access — if it’s an old address, update it first and wait for the change to settle.
- Copy the code when it arrives. It usually lands within minutes, but can take up to a few hours.
If WHOIS privacy is enabled, the code goes to the underlying registrant email, not the privacy proxy. If the email never arrives, that’s usually why — disable privacy temporarily and request again. You can re-enable it at Cloudflare (it’s free there).
Step 4: Move your DNS to Cloudflare
This is the part unique to Cloudflare. Do it before starting the transfer.
- Create a free Cloudflare account (if you don’t have one) and click Add domain.
- Enter your domain name. Cloudflare scans your current DNS records automatically — review every record carefully before continuing. This scan is usually accurate, but check MX records (email) and any TXT records (verification, SPF/DKIM) manually.
- Cloudflare gives you two nameservers. Go back to GoDaddy → Domain Settings → Nameservers → Change → enter Cloudflare’s nameservers.
- Wait for the nameservers to propagate. Cloudflare shows your domain as “Active” when it’s done — typically minutes, occasionally up to 24 hours.
- Test everything: load your site, send yourself a test email. DNS is now live on Cloudflare regardless of where the domain is registered.
Nothing breaks during this step as long as the DNS records are correct. Your site stays up; only the nameserver delegation changes.
Step 5: Start the transfer at Cloudflare
- In Cloudflare: Domain Registration → Transfer Domains.
- Enter your domain name and the auth code from Step 3.
- Pay the transfer fee — around $10 for a .com at wholesale cost. One year of registration is included, so you’re prepaying next year at cost, not paying a penalty.
Step 6: Approve at GoDaddy
GoDaddy emails you to confirm the transfer. Approve it to skip most of the 5-day ICANN waiting period. If you ignore the email, the transfer auto-completes after 5 days.
Step 7: Verify
- Your domain appears under Cloudflare’s Domain Registration within 5 days (usually faster if you approved).
- Re-enable WHOIS privacy — free at Cloudflare.
- Confirm your DNS is untouched from Step 4. Since DNS was already on Cloudflare, nothing changes — your site and email keep working without interruption.
Timeline: what to expect
| Step | Time |
|---|---|
| Downgrade protection, unlock, request auth code | 15 minutes |
| Auth code email arrives | Minutes to a few hours |
| DNS migration to Cloudflare (nameserver propagation) | Minutes to 24 hours |
| Transfer initiation at Cloudflare | 10 minutes |
| GoDaddy approval → domain appears at Cloudflare | 1–5 days |
Realistic total: start to finish in under a week, with about 30 minutes of your active time. The DNS move (Step 4) is the only part that requires patience — don’t start the transfer until Cloudflare shows the domain as Active.
Troubleshooting
The auth code never arrives. Check the registrant email on the domain — GoDaddy sends it there, and if WHOIS privacy is on, it goes to the underlying address, not the proxy. Update the email, wait an hour, request again. Also check spam.
Transfer shows as “pending” for days. You probably didn’t approve GoDaddy’s confirmation email. Search your inbox for it — approving cuts the wait from 5 days to 1–2.
Cloudflare says the domain isn’t eligible. Two common causes: the domain is under 60 days old (or transferred within 60 days), or DNS isn’t on Cloudflare yet. Fix whichever applies and retry.
Site or email broke after the DNS move. A DNS record didn’t carry over in Step 4. Compare Cloudflare’s DNS tab against GoDaddy’s old zone (screenshot it before changing nameservers — future you says thanks). MX records for email are the usual casualty.
What about GoDaddy email and hosting?
If your email runs through GoDaddy (Microsoft 365 resold, or Workspace Email), the domain transfer doesn’t touch it — but the DNS move in Step 4 does. Cloudflare’s auto-scan usually picks up MX records correctly; verify them manually before flipping nameservers.
If your site is hosted at GoDaddy too, consider whether the hosting moves as well. There’s no technical requirement — DNS can point anywhere regardless of registrar — but if you’re leaving GoDaddy over trust or pricing, the hosting renewal prices deserve the same scrutiny as the domains. Our hosting migration guide covers that move.
What this costs
A .com transfer to Cloudflare runs about $10 at wholesale — and includes a one-year renewal. Compare that to GoDaddy’s renewal pricing, which runs well over $20/year for .com after the intro deal expires. The transfer pays for itself the first year.
After the move: locking it down
Once the domain is at Cloudflare, take five minutes on security hygiene:
- Enable two-factor authentication on your Cloudflare account (TOTP app, not SMS).
- Confirm the registrar lock is on — Cloudflare enables transfer lock by default; verify it in Domain Registration settings.
- Check auto-renew is enabled so you never face the expiry timeline.
- Save the auth code process for later: Cloudflare generates transfer-out codes on request, so leaving is as easy as arriving — no dark patterns in reverse.
Then close the GoDaddy account’s payment methods if nothing else lives there. Domains have a way of quietly renewing at bad registrars years after you thought you left.
Why Cloudflare over Porkbun
Both are honest. Pick Cloudflare if your DNS is already there (or you’re happy moving it, per Step 4) — you get the cheapest possible price and one dashboard for DNS and domains. Pick Porkbun if you’d rather skip the DNS prerequisite and use a traditional registrar control panel. Either way, you’re out of GoDaddy’s renewal trap — see our GoDaddy → Porkbun guide for that route.
GoDaddy hosting renewals are priced like their domains. If you're consolidating away from GoDaddy, move the hosting in the same project.
See Hostinger plans