Move a GoDaddy Domain to Another Account Guide

You can move a domain from one GoDaddy account to another in under an hour if you prep correctly. The trick is protecting DNS, email, and SEO while you change ownership. This playbook shows business owners and marketing leads exactly how to do it without downtime, finger-pointing, or surprise locks.

Moving a domain to another GoDaddy account is not a registrar transfer. Think of it as an internal handoff: the domain stays at GoDaddy, but the legal owner and billing profile change to the recipient. No EPP or auth code. No unlock needed just to move inside GoDaddy. And if you keep the same nameservers, your website and email can keep running during the change.

Nameservers control where DNS lives. If the domain uses third-party nameservers, those continue to apply after the move. If it uses GoDaddy nameservers, the recipient can choose to keep the existing nameservers and copy the DNS zone or replace them with defaults. Copying keeps your live records intact.

Because you are changing ownership, ICANN rules can introduce a 60-day transfer lock if registrant contact information changes materially. You can usually avoid that by keeping current contact info during the move and updating later, if needed, once the dust settles.

There are legitimate reasons to move a domain without changing registrars. The most common are ownership alignment and financial housekeeping. If your brand or site is tied to an account you do not control, you will eventually hit permission and billing walls. Moving the domain to the correct account resolves that.

Common scenarios include an acquisition, where the brand and domains migrate to the parent company account; an agency-to-in-house transition, when the agency originally registered the domain; consolidating a portfolio into a single corporate account; and selling or assigning specific domains in a multi-brand group after a reorg.

Another good case: clean separation of assets when you spin out a product line. If a product earns its own P&L, you want the domain tied to that unit’s GoDaddy account for clear billing and fewer cross-team permissions.

Most transfer pain is avoidable with a 20-minute checklist. Do this before anyone pushes buttons. Confirm who owns the domain, who will receive it, and which sites and inboxes depend on that DNS. Capture exact DNS records so you can roll back instantly if needed.

Make a snapshot of all DNS records. Specifically, list A and AAAA records for web apps and subdomains, CNAMEs for CDN and app endpoints, MX for email, TXT records for SPF, DKIM, and DMARC, and any SRV or verification TXT records used by analytics, GSC, Firebase, CRM, or sender tools. If you use GoDaddy DNS, export the zone file or screenshot every record.

Reduce risk: lower TTL to 300 seconds a few hours before the move, schedule the change outside peak traffic, and ensure both sides can access the required emails to accept the move. If the registrant email is forwarding to a shared inbox, verify that forwarding works. If any part of your stack relies on TXT-based verification, be prepared to re-verify if a provider flags changes.

The sender kicks off the process. They must be logged into the account where the domain currently resides and have the recipient’s GoDaddy Customer Number and email address. Confirm those details over a secure channel and double-check the spelling. A typo here creates delays or moves the domain to the wrong person.

From the sender’s domain portfolio, select the domain and open the ownership or domain settings panel. Choose the option to move or transfer the domain to another GoDaddy account. Provide the recipient’s GoDaddy email and Customer Number. You will be asked about contact info: keep the current WHOIS contacts or let the recipient update after acceptance. To avoid an ICANN 60-day lock from a registrant change, keep the current contacts during the move when possible.

Nameservers: you will be prompted to keep existing nameservers or switch. Choose to keep existing nameservers when continuity matters. This preserves routing. Confirm and submit the move. The domain will enter a pending outbound state until the recipient accepts.

The recipient gets an email that an incoming account change is waiting. They should log in and find the pending change under incoming or pending account changes within their domain area. If they do not see it, check spam, verify the correct GoDaddy email, or wait a few minutes and refresh.

Open the pending change, review the domain, and confirm ownership details. If given a choice, select keep existing nameservers to maintain the current DNS. If your organization needs to update the registrant info, note that changing the registrant name, org, or email can trigger the ICANN 60-day transfer lock. If that lock would block near-term registrar transfers you plan to do, accept the move first, then change contacts later.

Complete the acceptance. The move usually completes quickly, often within minutes, though propagation and panel updates can take a bit longer. Once the domain lands, verify that auto-renew and domain protection preferences align with your policy.

Downtime happens when nameservers or zone files are changed without replicating the records. Your goal is to keep nameservers unchanged during the account move. If the domain is using GoDaddy DNS, ensure the zone is copied intact when the recipient accepts. If the domain is using third-party nameservers like Cloudflare or a hosting provider, nothing changes at the DNS level during the GoDaddy move.

After the move, test the live site, admin logins, and critical subdomains. Verify that A and CNAME records resolve the same as before, and that any CDN edge configuration is still serving. For complex stacks, use a script to query each record from multiple resolvers and compare against your snapshot.

Only when you have a reason to do so should you change nameservers. If you plan a DNS provider migration, decouple it from the account move: first move the domain ownership while keeping nameservers, then perform a controlled DNS migration with record import, validation, and a staged cutover over 24–48 hours.

Email breaks are painful and silent. Keep nameservers unchanged during the move to avoid changing MX records. After the move, confirm mail flow: send and receive from internal and external addresses, check spam placement, and run a quick SMTP test for any transactional senders.

Verify that SPF records still include all sending services, that DKIM remains valid for each domain or subdomain, and that DMARC is pointing to the right aggregate and forensic mailboxes. If you use Google Workspace or Microsoft 365, re-check domain verification and return-path settings. For marketing automation or CRM senders, confirm that their DNS-based verifications still show as authenticated.

If the recipient plans to consolidate DNS or change email providers soon, keep that as a separate, fully-scoped mini-project. Audit every sender path, update DNS with staged TTLs, and run parallel validation before making any MX changes.

ICANN policy can lock a domain for 60 days after a registrant change at the domain level. That lock prevents transfers to another registrar but does not block normal use. Many teams accidentally trigger this by editing the registrant name or email during an account move.

If you need near-term flexibility to move registrars later, avoid changing registrant fields during acceptance. Accept the move with existing contact info, then update contacts after you confirm you are not planning a registrar transfer this quarter. If privacy or compliance requires updating the organization field, plan for the 60-day window and document it so teams do not open tickets in week three asking why a registrar transfer is blocked.

Privacy services generally remain enabled after the move when kept at GoDaddy. Still, verify privacy settings and public WHOIS output post-move to ensure data exposure meets your policy and local legal requirements.

Domains carry their remaining registration term when moved. Billing methods do not. The recipient needs to enable auto-renew if your policy requires it and attach the correct payment method. Review renewal cadence, currency, and any recovery or protection add-ons you rely on.

Check that domain protection or ownership protection tiers are still applied as expected. Confirm contact email addresses used for renewal and ICANN notices route to a monitored inbox. If your finance team tracks assets, create or update the record in your asset register with the new account, renewal date, and responsible owner.

For portfolios, repeat this process in batches of 5–10 domains rather than moving dozens at once. After each batch, spot-check both web and email using your record snapshot plan and log anything that needs cleanup. Rinse and repeat.

Common failure modes are almost always administrative: the recipient typed the wrong Customer Number, the sender selected replace nameservers, the acceptance email went to an unmonitored inbox, or the registrant change triggered a lock that someone did not anticipate. Start there when debugging.

If the acceptance email does not arrive, verify the recipient email and check the incoming account changes section in their GoDaddy account. If a move appears stuck, ensure there is no outstanding domain contact verification or 2FA approval required by the sender. For expired domains or names in redemption, resolve status before attempting the move.

If DNS appears to have changed unexpectedly, compare live records against your snapshot. If the recipient replaced nameservers unintentionally, switch back or re-import the zone to the active DNS provider and wait for TTL expiry. For email deliverability dips after the move, re-check SPF alignment, DKIM keys, and DMARC policy alignment, then test again.

Since you are already touching core infrastructure, use the move as a trigger to clean up. Confirm that the apex and www variants both resolve correctly with a single canonical, that HSTS and HTTPS redirects are consistent, and that your sitemap and robots settings are correct. If you have a multi-region or subdomain-heavy setup, write out a compact routing map and validate each primary path.

In Google Search Console, verify the domain property in the recipient account if ownership changes. Keep historical data accessible by maintaining access to the old property until the new one is fully active. Re-test rich result eligibility, submit a fresh sitemap ping, and confirm that your top pages maintain stable impressions over the following week.

Use this window to address soft 404s, broken internal links, and redirect chains. These cost rankings and crawl budget. If organic growth is a priority post-move, consider a parallel content plan that scales quality pages fast. We have seen compounding gains when teams pair technical cleanup with high-cadence, useful content targeted to demand.

Most downtime happens at the seams between teams. An operator model keeps strategy and execution in one head - the person who plans the move also edits DNS, validates email auth, and checks Search Console. At Anton Chisliuk · AI Marketing Ops, one senior operator runs the whole stack: CRM, SEO, paid, outbound, and the plumbing under it. Proof matters: a B2B SaaS client grew from 0 to 80K organic visits per month and 2K inbound leads per month after we fixed technical debt and scaled content. If you want the philosophy behind this approach, learn more about the operator model on our about page.

Two small habits remove 90 percent of risk: dry runs and clear comms. For complex stacks, replicate the zone in a test domain and practice a provider switch. Publish test pages and test transactional email from that domain to shake out missing include mechanisms in SPF or unexpected CNAME chains.

Define a rollback: if site or email breaks, revert nameservers to previous values or restore the prior zone snapshot. Keep TTLs low during the maintenance window so recovery is fast. Assign one responsible person to own each step with a simple checklist. If a step fails, they decide immediately - proceed or roll back.

Communicate timelines to stakeholders. Tell sales about a five-minute DNS touch, warn support about possible email delays, and put a real person on watch during and after the move. This keeps escalations short and measured.

The account move itself is fast - commonly minutes after acceptance. Most of your time goes into prep and validation. Budget 20–30 minutes for the pre-flight, 10 minutes to initiate and accept, and 20–30 minutes for validation. If you also plan a DNS provider migration, book a separate window of 1–2 hours with a day of monitoring.

If you keep nameservers and copy the zone, users should not notice anything. If you change nameservers, expect normal DNS propagation behavior: many users switch within minutes when TTLs are low, but some resolvers can cache longer. That is why we lower TTL before the cutover.

When third parties are involved - a seller on a marketplace or a previous agency - factor in coordination time. Make it easy for them with exact instructions, the correct Customer Number, and your acceptance email.

Use this stripped-down list if you need to execute today and cannot afford mistakes.

- Snapshot current DNS: A, AAAA, CNAME, MX, TXT (SPF, DKIM, DMARC), SRV, and verifications.
- Lower TTL to 300 seconds several hours before the move.
- Confirm recipient email and Customer Number; decide to keep nameservers and contacts.
- Sender initiates the move; recipient accepts; keep nameservers unchanged.
- Validate site routes, APIs, and key inboxes; check SPF, DKIM, DMARC.
- Re-enable auto-renew and protection; document owner and renewal date.

If organic growth is a focus after the dust settles, connect the technical win to a content engine. Sustained visibility is earned by a clean stack plus compounding content. If you need a starting point for the content side, explore how we think about organic visibility at a systems level.

Technical reliability creates space for growth work. When infrastructure is solid, content and campaigns perform. Example: a B2B SaaS client went from zero to thousands of inbound leads per month while maintaining low paid CPL because technical and content systems were built together, not in silos. Want the deeper breakdown of that growth arc? Read the brief Cleverence case study.

If this move is tied to a site relaunch, DNS provider change, or email consolidation, get a second set of eyes. A 15-minute pre-flight review catches missing SPF includes, stale CNAMEs to old CDNs, and registry locks that block your plan. It is cheaper to prevent an outage than to spin up a war room mid-incident.

Moving a domain to another GoDaddy account is straightforward when you separate ownership from DNS, preserve nameservers, and validate email auth. Prep with a DNS snapshot and low TTLs, keep registrant contacts unchanged during the move if you want to avoid a 60-day lock, and validate everything right after acceptance.

If you want a checklist-driven partner to review your plan and help execute without downtime, book a free Growth Audit and we will walk your team through the exact steps and risks before you touch DNS.

Written by Anton Chisliuk - operator, not agency. Leads, sales, content, and systems - one senior operator.

- Do I need an auth code to move a domain between GoDaddy accounts?

No. An auth or EPP code is for registrar-to-registrar transfers. A move between GoDaddy accounts is an internal handoff and does not require an auth code.

- Should I unlock the domain before moving it to another GoDaddy account?

For an internal GoDaddy account move, you typically do not need to unlock the domain. The move can proceed while the domain remains locked for registrar transfers.

- Will my website or email go down during the account move?

They should not if you keep the existing nameservers and DNS zone. Downtime happens when nameservers change without copying the records. Keep nameservers as-is during the move, validate after.

- What is the ICANN 60-day lock and how do I avoid it?

Changing the registrant name, organization, or email can trigger a 60-day transfer lock that blocks registrar transfers. To avoid it, keep current contacts during the account move and update later if needed.

- Do DNS records copy automatically when I move a domain between GoDaddy accounts?

If the domain uses GoDaddy nameservers, you can keep the current nameservers and copy the zone. If you switch to default nameservers, you may lose custom records. If you use third-party DNS, nothing changes.

- How long does it take to move a domain to another GoDaddy account?

Once initiated, the recipient accepts and the move often completes within minutes. Allocate time for prep and validation to ensure zero downtime.

- Will auto-renew and billing move with the domain?

No. The domain’s remaining term moves, but payment methods and auto-renew settings do not. The recipient should enable auto-renew and set the correct payment method after acceptance.

- Can I move multiple domains at once?

Yes, but move in small batches, such as 5–10 domains, and validate web and email after each batch. This reduces blast radius if a setting is wrong.

- What should I test after the move?

Check that the site loads on apex and www, APIs and subdomains resolve, MX and DMARC pass, and transactional email works. Compare live DNS to your snapshot to confirm parity.

- What if the recipient does not receive the acceptance email?

Confirm the correct GoDaddy email address, check spam, and look for the request in their incoming or pending account changes area. If still missing, the sender can cancel and re-initiate with the verified details.