Transferring a .au Domain Between Registrars, Step by Step

Staying with a bad registrar is one of the most common — and least necessary — frustrations in managing .au domains. People endure surprise renewal pricing, clunky control panels, and unreachable support for years because they assume moving a domain is risky, technical, or will take their website down.

It is none of those things, if you do it in the right order. A .au registrar transfer is a well-defined process with strong registrant protections built into auDA’s rules: the losing registrar must let you go, must give you the domain password, and cannot charge you an exit fee for the transfer itself. I have moved everything from single family-business domains to whole portfolios between registrars, and the process below is the one that produces zero downtime, every time.

Key takeaways

A registrar transfer changes who manages your domain, not who holds it — your licence, registrant details, and expiry date stay the same.

You need two things: access to the registrant contact email, and the domain password (EPP/auth code) from your current registrar — which they are obliged to provide free of charge.

A .au transfer does not add a year to your licence (unlike .com transfers), and transferring close to expiry is the classic trap — renew first if you are inside the final weeks.

DNS is the downtime risk, not the transfer itself: replicate your DNS records at the new provider before you move, and your site and email never blink.

First, understand what is actually moving

Three roles sit behind every .au domain, and a transfer only touches one of them:

The registry operates the .au database itself (under contract to auDA). Your domain’s actual record lives here, always, regardless of registrar.
The registrar is your service window to that registry — the company you pay renewals to, whose control panel you log into.
The registrant is you, the licence holder.

A registrar transfer repoints your service window. The domain record, your identity as registrant, your eligibility basis, and your expiry date are untouched. This is also why the transfer itself is not a security event: nobody can use the process to take the domain from you, because the registrant does not change.

(Changing the registrant — selling the domain or moving it to a new entity — is a different process with different rules, covered briefly at the end.)

One critical .au quirk: no bonus year, so mind the expiry

If you have transferred .com domains, unlearn one habit: gTLD transfers typically add a year to the registration as part of the transfer fee. .au transfers do not work that way. The transfer moves the domain with its existing expiry date intact, and the new registrar may charge nothing at all for the incoming transfer, or a fee that may bundle a renewal — terms vary, so read them.

The consequence: transferring a domain that is about to expire is the classic self-inflicted wound. If the domain expires mid-process, you are suddenly dealing with the suspended-domain grace period (see what happens when a .au domain expires) instead of a routine transfer. The safe rule I give everyone: if expiry is within about 30 days, renew at the current registrar first, then transfer at leisure. A year’s renewal costs a fraction of what an expiry accident does.

Pre-flight checklist

Fifteen minutes of preparation makes the transfer boring, which is the goal.

Confirm you control the registrant email. The transfer confirmation goes to the registrant contact recorded for the domain. Check it on the auDA WHOIS (whois.auda.org.au) and at your current registrar. If it points to a dead mailbox or an ex-employee, fix that first — at the current registrar — before starting anything.
Check the expiry date. More than 30 days out? Proceed. Less? Renew first (see above).
Export your DNS records. From the current registrar or DNS host’s control panel, copy every record: A, AAAA, CNAME, MX, TXT (including SPF, DKIM, DMARC), SRV — all of it. Screenshot or export to a file. This list is your insurance against the only real downtime risk in the whole process.
Choose the destination registrar deliberately. Since you are moving anyway, move somewhere worth being — transparent renewal pricing, proper DNS control, two-factor authentication. Our guide to choosing a .au registrar covers the criteria.
Note where your DNS is actually hosted. If your nameservers point to your web host or a third-party DNS provider (not the registrar), the transfer will not disturb DNS at all — the risk section below mostly evaporates. If the registrar hosts your DNS, plan the DNS move explicitly (step 4 below).

The transfer, step by step

Step 1: Get the domain password (EPP/auth code)

Every .au domain has a domain password — also called an EPP code, auth code, or authinfo code — that authorises a transfer. Request it from your current registrar; most control panels have a button for it, and it is typically emailed to the registrant contact.

Two protections worth knowing, both from auDA’s rules: the registrar must provide the password to the registrant promptly and free of charge, and cannot obstruct the transfer because you owe them nothing beyond already-billed services. A registrar that stonewalls a password request is breaking the rules — mention auDA’s complaints process and the conversation usually shortens. If the registrar is unresponsive or defunct, the registry operator provides a recovery path for registrants to obtain the password directly; auda.org.au has the current details.

Also check the domain is not transfer-locked in the current control panel (a theft-protection setting some registrars apply) — unlock it before proceeding.

Step 2: Start the transfer at the new registrar

At the gaining registrar, choose “transfer a domain”, enter the domain name and the password, and pay whatever their incoming-transfer terms specify. You will create or use an account there — set it up properly from the start: strong password, two-factor authentication, correct billing details.

Step 3: Approve the confirmation

The gaining registrar sends a confirmation request to the registrant contact email. Click it. This is the step that dies quietly when the registrant email is stale — which is why it was pre-flight item one. Once approved, the transfer completes quickly: .au transfers are typically done within hours, not the multi-day waits common with gTLDs.

Step 4: Deal with DNS — the part that actually causes outages

The transfer moves registrar management; what happens to DNS depends on where it was hosted:

DNS hosted elsewhere (your web host, a cloud DNS provider): nothing changes. Your nameservers still point where they pointed. Done.
DNS hosted at the old registrar: this is the danger case. Some registrars decommission DNS zones for domains that leave. The safe sequence: before initiating the transfer, recreate every DNS record (from your pre-flight export) at the new provider — new registrar’s DNS or a standalone DNS host — then update the domain’s nameservers to the new provider, wait for that to propagate and verify the site and mail still work, and then transfer the registrar. DNS keeps resolving from the new provider throughout, and the registrar move becomes a non-event.

If you only remember one technical thing from this article: replicate DNS before you move, and nameserver changes before registrar changes. Every “the transfer broke our website” story I have ever investigated was actually “the old registrar’s DNS was switched off and nobody had copied the records”.

Step 5: Verify, then tidy up

After completion:

Check the domain’s registrar and status on the auDA WHOIS.
Confirm the website loads and — critically — send and receive a test email on the domain. MX, SPF, DKIM, and DMARC records are the ones most often missed in a DNS re-creation, and broken email is quieter than a broken website.
Confirm the expiry date carried over as expected, and set your renewal reminders at the new registrar (calendar entry included — see our expiry guide for why the calendar matters).
Re-apply the transfer lock, and close the old registrar account once nothing else depends on it.

Troubleshooting the common snags

The password doesn’t work. Codes can be time-limited and are easy to mangle in copy-paste (trailing spaces are the classic). Request a fresh one and paste it directly.

The confirmation email never arrives. Check spam first, then check which address the registrant contact actually is — nine times out of ten it is going to an old mailbox. Correct the contact at the current registrar, then restart.

The old registrar is dragging its feet. Put the password request in writing, cite the domain name, and state that under auDA’s registrar transfer policy the password must be provided to the registrant promptly and without charge. Escalate to auDA’s complaints process (auda.org.au) if genuinely stuck.

The domain expired mid-transfer. Stop, renew it (grace-period renewal at the old registrar), let it return to active status, then run the transfer again. This is the scenario the 30-day rule exists to prevent.

How long does it all take?

Reasonable expectations for planning purposes, assuming no snags:

Password request: minutes to a day, depending on the registrar’s process. Automated control-panel retrieval is instant; emailed codes usually arrive within the hour.
The transfer itself: once the confirmation is approved, .au transfers typically complete within hours — the .au registry processes them quickly, without the five-to-seven-day pending windows gTLD transfers are known for.
DNS propagation: if you moved DNS hosting, allow up to 24–48 hours for old nameserver records to age out of caches worldwide, though most resolvers pick up changes much sooner. Lowering TTLs a day or two in advance shrinks this window dramatically.
End-to-end, done carefully: a single domain is comfortably a same-day job — most of it waiting, not working.

Moving a whole portfolio

Transferring one domain is a checklist; transferring twenty is a project, and the failure mode changes from “missed step” to “lost track”. What works:

Spreadsheet first. Every domain, its expiry date, its registrant contact email, where its DNS is hosted, and whether anything (email, subdomains, third-party services) depends on it. The audit alone usually surfaces a stale contact or a domain nobody remembers registering.
Triage by expiry. Renew anything inside the 30-day danger zone before touching it. Transfer the long-dated names first while renewals process.
Batch by DNS situation. Domains with externally hosted DNS can move in bulk with near-zero risk; domains using the old registrar’s DNS each need the replicate-then-move treatment, so schedule them deliberately.
Verify each landing. Tick off registrar, expiry, nameservers, and a test email per domain as they arrive. The gaining registrar’s bulk-import tooling (worth checking for in advance — see our registrar criteria) makes this far less tedious.

Consolidating a scattered portfolio into one well-secured account is the biggest single manageability upgrade available to a domain holder, and it is precisely the job people defer for years because it feels risky. Done in the order above, it is just admin.

Registrar transfer vs registrant transfer

One final distinction, because the words are confusingly similar:

Registrar transfer — everything above. Same holder, new management company. Free of exit fees, keeps the expiry date.
Registrant transfer — a change in who holds the licence: selling the domain, moving it from your sole-trader ABN to your new company, business sale, restructure. This is a formal process in which the new registrant must meet the .au eligibility rules in their own right, and it typically involves a new licence (and fee) in the new registrant’s name. If you are doing both — selling a domain and the buyer wants their own registrar — do the registrant transfer first, cleanly, and let the buyer move registrars afterwards.

A .au transfer done in the order above — contact email verified, expiry checked, DNS replicated, password in hand — takes under an hour of actual work and carries essentially no risk. Which means the real decision is not “dare we move?” but “is our current registrar worth staying for?” If you have read this far, you probably already know the answer.

Transfer rules summarised from auDA policy — check auda.org.au for the current .au Licensing Rules and registrar transfer requirements.