How to Transfer a Domain to a New Registrar

“Transfer a domain” gets used for two genuinely different processes. Mixing them up is the single most common reason a domain move takes far longer than it should. One moves a name between registrars while the same business keeps holding it. The other changes who holds the licence at all. They need different things from you, and only one of them is quick.

How to transfer domain registration between registrars, same registrant (a domain name transfer)

This is the process most people mean by “transfer” — moving an existing domain from one registrar to another, without changing who the licence belongs to. In general terms it requires the domain to be unlocked at the losing registrar, and an authorisation code or password obtained from that registrar. It also requires confirmation through the registrant contact email address. That is why keeping that address current matters well beyond receiving renewal notices. Handled correctly, this is usually a matter of days. It should never require the losing registrar’s active cooperation beyond issuing the code. A registrar refusing to release a domain the registrant is entitled to move is a genuine complaint, not a negotiation.

Changing the registrant at your current registrar — a different registrar move, and a harder thing

Changing who the licence itself belongs to is not a transfer between registrars at all. It is a change to the licence. The incoming registrant has to independently satisfy the eligibility rules covered in .com.au versus .au versus .com and Australian domain eligibility. This is the process that actually matters when parting ways with a supplier who registered a name in their own name rather than the business’s. It depends entirely on either that supplier’s cooperation or a formal dispute process, because nobody else can simply reassign a licence on your behalf.

The four things you need for transferring domains before either process can start

Whichever one applies, transferring domains requires the same four things. They are the registrar’s name (which may not be the reseller you dealt with), and working login credentials to the account. Add control of the registrant contact email address, and the domain’s authorisation code or password, obtained from the losing registrar. Confirm you have all four while the relationship with a current supplier is still good. This is the single most useful piece of preventative work a business can do about its own domain. It costs nothing.

What commonly goes wrong with a domain name transfer

A locked domain is one common problem — most registrars lock a name against transfer by default, and it needs to be explicitly unlocked before an authorisation code will work. Another is a registrant contact email nobody at the business actually monitors, so the confirmation step silently fails. A third is a supplier’s name sitting in the registrant field, discovered only once the relationship has already soured, turning a routine transfer into the harder registrant-change process described above. And a fourth is a domain still within a post-registration lock period some registries apply, which simply has to be waited out.

What it does not require

A transfer between registrars, correctly executed, does not require the website or email to go down. DNS records can, and generally should, be copied to the new registrar or a chosen DNS provider before the transfer completes. That way, nothing currently pointing at the domain notices the change at all. The mechanics of that sequencing are the same ones covered in moving hosts without downtime, which is worth reading alongside this if a hosting move is happening at the same time.

Why an unlock request should never be refused indefinitely

A registrar delaying or refusing to unlock a domain the registrant is entitled to move, beyond any standard post-registration lock period, is a legitimate complaint to escalate. Escalate first to the registrar directly, and if that fails, to the wider dispute processes available through the relevant registry. A brief administrative delay is normal. An indefinite refusal is not, and registrants are not without recourse when it happens.

The paperwork worth keeping regardless of whether transferring domain registration is planned

A simple record of which registrar currently holds a domain, the account login, and the registrant contact email is worth keeping, reviewed at least annually. That means a transfer — planned or urgently needed — never starts from a standing start of first having to rediscover this information under time pressure.

Timing a transfer around a wider migration

Where a domain transfer is happening alongside a hosting or platform migration, sequencing genuinely matters. Completing the domain transfer first, once DNS is confirmed correctly pointed, tends to produce fewer surprises than attempting all three changes simultaneously.

Confirming the domain transfer actually completed

A transfer is not finished simply because a confirmation email arrived. Check the domain’s registrant and registrar through a public WHOIS lookup a day or two afterwards to confirm the change genuinely took effect. Do not assume an email notification is the final word on the matter.

What to do next

Confirm the four items above today, regardless of whether a move is planned. If a transfer is genuinely underway, unlock the domain first, and obtain the authorisation code. Then confirm the registrant contact email is one someone at the business actually reads, before starting anything else. Where the domain has already lapsed rather than being actively moved, the relevant process is different again, and is covered in domain expiry and renewal. A transfer sometimes happens as part of a wider technical handover from one developer to another. Web development services sets out what a competent handover should include beyond the domain itself.