How Long Does a Domain Transfer Take?
Typically 5–7 days from the moment you initiate it, and sometimes much faster if your current registrar lets you approve the transfer early. The wait is a built-in approval window at the losing registrar, not processing time — and your site and email run normally through all of it.
This is the most-asked question before anyone hits the transfer button, and the honest answer has two halves: the prep you control (minutes, with automation) and the wait you don't (days, by design). Here's the whole timeline, what each stage is actually doing, and what can stretch it.
The timeline, stage by stage
| Stage | Typical duration | What's happening |
|---|---|---|
| Prep: DNS replicated at destination | Minutes (automated) to hours (manual) | Records exported and rebuilt at the new provider; nameservers switched and verified |
| Prep: unlock + auth code | Minutes | Transfer lock off, WHOIS privacy off if required, EPP/auth code retrieved |
| Initiate at the new registrar | Minutes | Enter the auth code, pay (which typically adds a year of registration) |
| Losing registrar's approval window | Up to ~5 days | The old registrar confirms or simply lets the window lapse into auto-approval |
| Completion | Hours | Registry updates the registrar of record; you re-enable lock and privacy |
Add it up and "5–7 days end to end" is the realistic promise, with the approval window as the dominant term. Some registrars — GoDaddy included — expose a control to approve an outbound transfer from your account dashboard, which can collapse the multi-day wait to hours. Worth checking before you settle in to wait.
Why does the wait exist at all?
Security, genuinely. The approval window exists so a hijacked domain can't be whisked to another registrar before the real owner notices. The same logic drives the related locks worth knowing about before you plan a move:
- 60 days after initial registration — ICANN rules block transfers of brand-new domains.
- 60 days after a completed transfer — same idea; you can't chain moves.
- After registrant contact changes — many registrars apply a 60-day transfer lock when you change the owner's name, organization, or email. If you're planning to move a domain, move it first, update contacts after.
What can slow a transfer down?
- Wrong or expired auth code — the transfer fails quietly and you restart. Automated retrieval (the export skill grabs codes for every domain in one pass) removes the typo class of failure.
- Transfer lock still on — the request bounces immediately. Easy to miss when doing twenty domains by hand.
- Unverified or stale registrant email — approval notices can route to the registrant contact; if that inbox is dead, things stall. (One more reason the registrant contact should be a monitored role address — see how to secure a domain.)
- Domain inside one of the 60-day windows — nothing to do but wait it out.
- Expiry mid-transfer — the avoidable nightmare. Renew first if the date is close.
Does anything go offline during those 5–7 days?
No — provided you did the move in the right order. The pending transfer changes which company manages the registration; it does not touch which nameservers answer for your domain. If DNS was replicated and switched to the destination before initiating (the whole method is in how to transfer a domain without downtime), visitors and email flow identically on day 1, day 4, and day 7. Most owners' honest experience of the wait: they forget it's happening until the completion email arrives.
What should you do while the transfer is pending?
Almost nothing — which is the point — but three small disciplines make the week clean. First, watch the registrant inbox: any approval or verification email that does arrive is usually the fastest path to early completion, and the same inbox is where a failure notice would land. Second, don't touch registrant contact details or nameservers mid-flight; changes during a pending transfer are how edge cases happen. Third, when the completion email arrives, finish the job: re-enable the transfer lock, re-enable WHOIS privacy, confirm auto-renew is on at the new registrar, and check that the expiry date reflects your carried-over time plus the added year. The transfer isn't done when it completes — it's done when the locks are back on.
Does the timeline change for 20 domains instead of 1?
Barely — because transfers run in parallel. Twenty initiated transfers all sit in their approval windows simultaneously, so the calendar time for a whole portfolio is roughly the same 5–7 days as for one domain. What multiplies with portfolio size is the prep: exports, imports, unlocks, auth codes, times twenty. That's the part the Migration Kit automates into a single run — the batching strategy is covered in how to consolidate scattered domains.
FAQ
Can I speed up a domain transfer?
Sometimes. The multi-day wait is the losing registrar's approval window, and some registrars offer a way to approve or release the transfer early from your account dashboard. If yours does, using it can shrink the wait from days to hours. If not, the auto-approval window runs its course.
Is my website down while the transfer is pending?
No. The transfer moves the registration between registrars; it doesn't touch DNS resolution. If your DNS is already set up at the destination before you initiate — the recommended order — your site and email run normally through the entire pending period.
Why can't I transfer a domain I just registered?
ICANN rules lock a domain against transfers for 60 days after initial registration, and a similar lock typically applies after a completed transfer. Registrars may also apply a 60-day lock after changes to registrant contact information. Plan moves outside those windows.
What happens to my expiration date after a transfer?
You keep your remaining registration time, and the transfer payment typically adds one year on top of it. A domain expiring next March that transfers today will generally expire the following March after the move completes.