Can I move my domain from GoDaddy to Cloudflare?

Moving a domain that your whole business depends on can feel like handing over the keys to your storefront. The fear isn’t just technical—it’s about downtime, lost customers, and breaking something that’s already working. But a domain transfer isn’t about changing your website or disrupting your online presence. It’s simply moving your domain registration from one company to another, like switching your phone carrier while keeping the same number.

What owners often overlook is that the transfer process itself is straightforward when you know the steps. At GoDaddy, you’ll need to disable Domain Privacy and Domain Protection, unlock the domain, and turn off DNSSEC before obtaining the authorization code. Cloudflare requires the domain to first be active on its network with nameservers pointing to its DNS—a prerequisite that ensures your site benefits from Cloudflare’s performance and security from the moment the transfer begins. Only then can you enter the auth code and confirm the transfer through both registrars.

The active work involved is minimal: about 30 minutes of preparation and confirmation steps. After submitting the transfer request, most gTLD domains like .com or .net complete within 3–5 business days, though some TLDs such as .mx can take up to 10 days. Importantly, transfers typically include a one-year registration extension at cost, meaning you’re not paying extra for the move itself—just renewing your domain at wholesale pricing with no markup fees, as Cloudflare offers domains at-cost.

During onboarding, AI Business Sites handles domain setup by ensuring your domain is properly configured to work with the platform’s hosting and DNS requirements, guiding you through any necessary updates so your site launches smoothly and remains fully under your control. Whether you’re transferring to Cloudflare or keeping your current registrar, the focus stays on maintaining ownership and continuity—because your domain isn’t just an address; it’s the foundation of your business online.

Before you touch a single setting in your GoDaddy account, know this: a handful of rules can stop a domain transfer cold, and most of them are invisible until you're already mid-process. Checking them first saves you days of frustration and a support ticket or two.

The biggest blocker comes from ICANN. Under its rules, a domain cannot be transferred if it was registered or previously transferred within the last 60 days. The same lock applies if you changed the WHOIS registrant contact information — name, organization, or email — within that window, per Cloudflare's transfer documentation. So if you just registered the domain last month or recently updated the owner email, the transfer simply cannot proceed yet.

GoDaddy adds its own gotchas on top of the ICANN rules. The most common one trips up people who never touched a privacy setting consciously:

• Domain Privacy and Domain Protection must be fully disabled — GoDaddy may reject the transfer outright if either is still active, according to Cloudflare's troubleshooting guide.
• DNSSEC must be turned off, and the DS record TTL (usually 24 hours) must expire before Cloudflare will accept the transfer.
• The domain must be unlocked, though note that lock-status changes can take up to 5 hours to propagate in WHOIS — and some registrars take up to 24 hours.

Two timing traps deserve special attention. First, the renewal-within-45-days trap: if you renewed your domain within 45 days of its expiration date and then transfer it, the transfer adds another year — meaning you pay twice for the same registration year. ICANN rules entitle you to a refund from the previous registrar, but you have to know to ask.

Second, watch your registrant email. ICANN requires registrant email verification within 15 days of a change, or a hold gets placed on the domain — and a held domain cannot move anywhere.

If all of this sounds like paperwork you'd rather not babysit, that's exactly why services like AI Business Sites handle domain setup as part of onboarding — registering the domain in your name and configuring DNS, nameservers, and Google Search Console so the technical prerequisites are simply handled. Whether you transfer yourself or have a team do it, the eligibility rules above apply equally, so run through them before you start.

Moving a domain from GoDaddy to Cloudflare isn't complicated, but it does require a specific sequence — skip a step and the transfer stalls. The good news: about 30 minutes of active work gets the process started, and most generic top-level domains come with a one-year registration extension at cost when the transfer completes.

Before you begin, verify the domain is eligible. ICANN rules block transfers within 60 days of registration or a previous transfer, and any registrant contact change (name, organization, or email) in the last 60 days triggers the same lock. At GoDaddy, you'll need to disable Domain Privacy and Domain Protection entirely — GoDaddy may reject the transfer if either remains active — then turn off DNSSEC, unlock the domain, and grab the authorization code.

Cloudflare's process differs from other registrars: you must add the domain to Cloudflare first, point the nameservers to Cloudflare's authoritative DNS, and wait for the zone to show "Active" status. Only then can you enter the auth code on Cloudflare's Transfer Domains page. After that, approve the confirmation emails from both Cloudflare and GoDaddy. The previous registrar has up to five business days to release the domain, though some TLDs (like .mx) can take up to 10 days.

• Disable Domain Privacy and Domain Protection at GoDaddy
• Turn off DNSSEC and unlock the domain
• Add the domain to Cloudflare and update nameservers
• Wait for "Active" status, then enter the auth code
• Approve both confirmation emails

Country-code domains follow different rules: .uk family domains use an IPS tag instead of an auth code and don't receive the extra year. Once the transfer finishes, DNSSEC can be re-enabled in Cloudflare with one click. For businesses using platforms like Wix or Shopify that act as both host and registrar, an intermediate transfer step is required first — those platforms typically block nameserver changes while the domain stays with them.

At AI Business Sites, we handle domain configuration during onboarding so clients don't have to navigate registrar settings themselves. Whether you're pointing an existing domain or registering a new one, the setup is included in the 7-day build — your site launches with DNS, SSL, and Google Search Console already connected.

The transfer confirmation email arrives, you celebrate — and then the real work of living with your new registrar begins. Cloudflare runs its registrar differently than GoDaddy, and a few of those differences catch new arrivals by surprise.

The biggest change: once your domain is registered with Cloudflare, you must use Cloudflare's nameservers exclusively. As Cloudflare's own documentation puts it, you "cannot use another DNS provider while registered with Cloudflare Registrar," because the registrar was built specifically for customers using other Cloudflare products. If you currently manage DNS elsewhere — Route 53, NS1, or any third-party provider — that arrangement ends the day your transfer completes.

Here's what else to expect after the move:

• DNSSEC needs re-enabling. You disabled it before the transfer, but once it completes, you can turn it back on through Cloudflare with one click.
• Nameserver propagation takes time. Registrars can take up to 24 hours to process nameserver updates, so don't panic if your site behaves oddly for a day.
• Your registration gains a year. Most gTLD transfers (.com, .net, .org) include a one-year extension from your current expiration date, paid at cost.

One trap deserves special attention: the platform lock-in. If your domain is registered through a site builder like Wix or Shopify, those platforms act as both your hosting provider and registrar — and they typically don't allow nameserver changes while the domain lives with them. Since Cloudflare requires your nameservers to point to its network before a transfer can begin, a direct transfer is impossible. The workaround is a two-step dance: transfer to an intermediate registrar first, wait out the 60-day ICANN lock that applies after any transfer, then move to Cloudflare.

That 60-day rule is worth internalizing regardless of your situation. ICANN prohibits transfers within 60 days of registration, a previous transfer, or even changes to your WHOIS registrant contact information — so update your contact details at GoDaddy only after the move, not before.

This is also why ownership structure matters so much when someone else sets up your domain. When a service like AI Business Sites registers a domain during onboarding, it's registered in the client's name — meaning you can move it, transfer it, or point it wherever your business needs take you, without asking permission. If a provider ever insists on holding your domain in their account with nameservers you can't change, that's the platform trap in miniature — and a 60-day wait to escape it.

If reading about 60-day ICANN locks, DNSSEC records, and nameserver propagation made your eyes glaze over, that's the point — most business owners have better things to do than manage registrar settings. A domain transfer takes about 30 minutes of active work and up to 10 days to complete, according to Cloudflare's own documentation, and that assumes nothing goes wrong.

Here's the thing: if you're getting a new website built anyway, you shouldn't be touching any of this. The whole reason registrar transfers feel intimidating is that they're presented as your job. But domain configuration is setup work — and setup work is exactly what a done-for-you service exists to handle.

With AI Business Sites, your domain is registered in your name from day one. You own it — not us, not a platform holding it hostage. During onboarding, we handle the technical layer that most owners never want to see:

• Domain registration and DNS configuration, done during the build
• Google Search Console and Bing setup, sitemaps included
• Your Google Business Profile, connected and verified
• Launch — everything live and working within 7 days of kickoff

This matters more than it might seem. Some site-building platforms act as both your hosting provider and your registrar, and they typically don't allow nameserver changes while the domain is registered with them — which, as Cloudflare's transfer guide notes, makes moving your domain elsewhere impossible without an intermediate registrar and another 60-day wait. Ownership isn't just a nice word; it's the difference between a website you control and one you're renting.

Everything goes with you. Your domain, your code, your content, your lead data — all of it. We push your complete website to a GitHub repo in your name and provide a full database export. The site is built on standard React/Next.js, so any developer can pick it up. There's no long-term contract either — month-to-month, with 30 days' notice.

That's the arrangement in one sentence: you own everything, and we keep you by doing the work. The domain question that started this article — "can I move it?" — only becomes stressful when you don't truly own the thing you're moving. When the registration is in your name and the exit door is clearly marked, the question answers itself.

The alternative is spending an afternoon disabling privacy protection and hunting for authorization codes, only to discover that registrars can take up to 24 hours to process nameserver updates. Your time is worth more than a Tuesday spent in registrar settings.

If you'd rather hand the whole thing — domain, DNS, Google setup, launch — to a team that does this every day, book a free strategy call. Thirty minutes, no obligation, no sales pitch. Just a conversation about your business and what it needs online.