Transferring a domain moves the registration from one registrar to another. The operational sequence is fixed: unlock → Auth/EPP code → initiate at the gaining registrar → approve the email → settle nameservers. This guide is that procedure on EuroVDC. Transfer-lock semantics live in a separate lock article; day-of mistake lists live in the checklist post—here we walk the how-to only.
Start the move on domain transfer. Verify status beforehand with Whois lookup.
Prerequisites before you unlock
- Registrant/admin email still works and is monitored.
- Domain is not inside a 60-day lock after create or a prior transfer (many gTLDs).
- Expiry is comfortable; renew first if the term is nearly over.
- DNS export or screenshot of current NS/records exists.
- No registry holds or pendingDelete in Whois.
Lower TTL a day ahead if you will also change nameservers after the transfer completes.
Step 1 — Unlock at the losing registrar
Disable the transfer lock so Whois no longer shows clientTransferProhibited (or the local equivalent). Wait for registry sync—do not spam Auth codes into multiple gaining accounts while status still shows locked.
Step 2 — Request the Auth / EPP code
Ask the losing registrar for a fresh Auth/EPP code. Treat it like a one-time password: copy once, paste once into EuroVDC, do not paste into chat tools or email threads. If the code expires or was shared, request a new one.
Step 3 — Initiate at EuroVDC
- Open domain transfer.
- Enter the domain and Auth code.
- Confirm registrant data and payment for the transfer term (transfers usually add a year on eligible gTLDs—confirm for your TLD).
- Submit and watch for FOA / approval messages.
Step 4 — Approve promptly
Approve the losing-registrar and/or gaining-registrar confirmation emails without delay. Missed FOA is the most common silent stall. Do not change unrelated contacts mid-flight unless support instructs you.
Step 5 — Nameservers after completion
When the transfer completes, re-enable the lock, confirm auto-renew, and set or keep nameservers. Pointing NS to Sofia web hosting is optional but keeps DNS and registration in one EU account. Changing NS is independent of the registrar move—plan it deliberately.
Procedure vs lock article vs checklist
Use this page as the ordered runbook. Open the lock article when you need to understand clientTransferProhibited. Use the checklist when you want a mistakes/TTL punch list beside the steps. Product path stays domain transfer + Whois verification.
Frequently asked questions
How long does a domain transfer take?
Often hours to a few days after approvals, depending on TLD and registrar response. FOA delays stretch it.
Will my website go down during transfer?
Not if nameservers stay the same. Downtime risk comes from NS/DNS changes, not from the registrar move itself.
What if Whois still shows clientTransferProhibited?
Unlock did not sync yet, or a server-side status blocks you. Wait or contact the losing registrar—do not keep retrying Auth elsewhere.
Do country TLDs work the same way?
Core idea yes; portals and documents differ for .tr, .bg, .eu and others. Follow that registry’s transfer rules.
Should I unlock permanently?
No. Unlock for the move, then lock again when EuroVDC shows the domain as transferred.
How do I start on EuroVDC?
Verify with Whois lookup, unlock and fetch Auth at the losing registrar, then submit on domain transfer.
