People ask “how many days does a domain transfer take?” expecting a single number. Reality is a timeline with approval gates—and a short list of places the process silently stalls. This article is about duration and stuck points only. The ordered how-to, the day-of mistakes checklist and the transfer-lock semantics live in separate EuroVDC posts. When you are ready to move registration, start on domain transfer.
EuroVDC operates in Sofia (EU). Transferring the registrar does not by itself move your website; DNS and hosting stay until you change them on purpose.
Typical timeline (gTLDs)
| Phase | Often lasts | What “done” looks like |
|---|---|---|
| Unlock + Auth/EPP issued | Minutes to a few hours | Whois no longer transfer-prohibited; code in hand |
| Initiate at gaining registrar | Minutes | Order accepted, FOA/emails queued |
| FOA / email approvals | Minutes to days | Losing and/or gaining confirmations clicked |
| Registry processing | Hours to ~5–7 days | Whois shows new registrar |
| Post-complete hygiene | Same day | Lock back on, NS confirmed, auto-renew set |
Many transfers finish in well under a week when approvals are prompt. “Five to seven days” is a planning ceiling for common gTLDs—not a promise that every case needs the full window. ccTLDs and special registries can differ; read the TLD rules before you commit a cutover date.
Where transfers get stuck
- Still locked: Initiate while clientTransferProhibited (or equivalent) remains—Auth codes bounce or orders sit.
- Stale Auth/EPP: Expired or regenerated code after you copied an old one.
- Unread FOA mailbox: The admin/registrant inbox is full, filtered or abandoned—the #1 silent stall.
- 60-day create/transfer lock: Registry policy blocks another move too soon after create or a prior transfer.
- Expiry cliff: Domain near delete/redemption; renew first, then transfer.
- Payment or data hold at gaining side: Incomplete registrant fields or unpaid transfer term.
- Changing contacts mid-flight: Updating emails while FOA is pending orphans the approval chain.
What duration is not
Duration is not the how-to runbook (unlock → code → initiate → approve → NS). It is not the lock deep-dive. It is not the punch-list of TTL mistakes. Use those sister articles for procedure; use this page to set expectations and debug stalls. Product path remains domain transfer.
Planning tips for Sofia-hosted sites
If the site already runs on EuroVDC web hosting or cloud, you can often keep nameservers unchanged through the registrar move—site uptime and transfer clock are independent. Lower DNS TTL only if you will also change NS after completion. Do not schedule a marketing launch that assumes “transfer finishes tomorrow” unless FOA mailboxes are proven live.
When stuck: verify lock status, request a fresh Auth code, dig FOA spam folders, and confirm you are outside any 60-day window before opening tickets. Most “broken” transfers are waiting on an unread email.
Frequently asked questions
Is every transfer five to seven days?
No. Many finish faster after approvals. Plan for up to about a week on common gTLDs; check ccTLD rules separately.
What usually causes multi-day delays?
Missed FOA/approval emails, still-locked status, or registry 60-day restrictions after create/prior transfer.
Does transfer downtime equal transfer duration?
No. DNS can keep the site online while the registrar changes—if you do not break nameservers mid-move.
How is this different from the how-to article?
How-to is the ordered procedure. This page explains clocks and stall points so you can set realistic dates.
When should I unlock?
Shortly before you initiate—not weeks early—then re-lock after Whois shows the new registrar.
Where do I start the move?
Open domain transfer with a fresh Auth code after unlock and mailbox checks.
