On this page
Domain Management
A Domain Transfer Moves Registration, Not Your Whole Website
A domain transfer is the process of moving a domain name from one registrar or provider account to another. It changes who manages the registration and renewal of the domain, but it does not automatically move your website, DNS records, email hosting or online store. That distinction matters because many website and email outages happen when a domain transfer is treated as a simple admin task rather than a planned infrastructure change.
- The domain registration can move while your website and email stay where they are.
- DNS records must be checked before, during and after the transfer.
- Registrar and registry rules affect timing, approval steps and transfer eligibility.
Definition
A domain transfer moves the registration of a domain name from one registrar or provider account to another. It usually requires access to the current registrar, an unlocked domain, an authorisation code and approval from the registered domain holder.
A domain transfer is not the same as moving website hosting, changing DNS records or migrating business email. Those services may be connected to the domain, but they are managed separately.
Key Points Before You Transfer a Domain
- Your domain name is your digital foundation, so transfer planning should include DNS, email, website hosting and renewal control.
- A registrar transfer usually does not change where your website or email points unless nameservers or DNS records are changed.
- The safest transfers start with an audit of ownership, access, expiry dates, nameservers and all active DNS records.
The Basics
What Actually Moves During a Domain Transfer?
Domain Transfer Terms Worth Knowing
These terms appear often during domain transfers. Knowing the difference helps you avoid confusing domain registration, DNS and hosting.
- Registrar
- The provider that manages the domain registration, renewal and transfer process. Registrars operate under registry rules for each domain extension.
- Authorisation Code
- A transfer code, sometimes called an EPP code or AuthInfo code, used to approve a domain transfer. The exact name depends on the domain extension and registrar.
- Nameservers
- The servers that tell the internet where to find the DNS records for your domain. Changing nameservers can affect websites, email and connected services.
Process
How a Domain Transfer Usually Works
The exact steps depend on the domain extension and registrar, but most business domain transfers follow the same broad flow.
-
Confirm Ownership, Access and Eligibility
Before anything is moved, confirm who the registered holder is, which registrar controls the domain, whether the domain is active, and whether transfer restrictions apply. For some domains, recent registration, recent transfer, expiry status or registry policy may affect eligibility.
-
Prepare the Domain and Start the Transfer
The current registrar may need to unlock the domain and issue an authorisation code. The transfer is then started with the new registrar, using the correct domain details and code. The registered contact may need to approve the request.
-
Monitor Completion and Check Connected Services
Once the transfer is complete, confirm the domain is in the correct account, renewal details are correct, nameservers are unchanged or intentionally updated, and website, email, SSL and third-party records still work.
Do Not Assume DNS Will Be Copied Automatically
Business Impact
How Domain Transfers Affect Websites, Email and DNS
Domain Transfer vs DNS Change
These two actions are often confused, but they solve different problems and carry different risks.
| Area | Domain Transfer | DNS Change |
|---|---|---|
| What Changes | The registrar or provider account that manages the domain registration and renewal. | The records that tell traffic where to go for websites, email and connected services. |
| Main Risk | Loss of access, failed approval, transfer lock, expiry issues or poor renewal management. | Website outages, email disruption, SSL validation issues or broken third-party integrations. |
| Business Impact | Usually administrative unless DNS or nameservers are changed as part of the move. | Can affect live services quickly if important records are missing or incorrect. |
Pre-Transfer Domain Checklist
Before transferring a business domain, check the information that could affect continuity, renewal control and connected services.
-
Confirm who owns and controls the domain
Check the registered holder, administrative contact, registrar account access and expiry date. For .au domains, ownership remains with the registered client, even when a provider manages the registration on their behalf.
-
Document nameservers and DNS records
Record A, CNAME, MX, SPF, DKIM, DMARC, TXT and verification records before making changes. This is especially important when the current registrar also hosts DNS.
-
Plan the timing with website and email providers
Avoid transferring a domain during a busy trading period, major campaign, website launch or email migration unless there is a clear plan and the required access is available.
Common Domain Transfer Mistakes
Most transfer problems are preventable. They usually come from missing access, undocumented DNS or assumptions about what the transfer will do.
Starting the transfer without checking DNS
Do this instead
Audit the current DNS zone first. If the old registrar hosts DNS, make sure the records can be recreated before the transfer or nameserver change.
Using an old staff member or agency email for approval
Do this instead
Update the registered contact details where appropriate before transfer planning. Approval emails and transfer notices must reach someone authorised to act.
Moving the domain and website at the same time without a cutover plan
Do this instead
Separate the steps where practical. Prepare hosting, backups, DNS records and testing before changing nameservers or pointing the domain to a new website.
Why a Domain Transfer May Fail or Cause Problems
If a transfer stalls or services stop working, the cause is usually related to access, registrar policy or DNS configuration.
The transfer request is rejected
Likely cause
The domain may be locked, the authorisation code may be incorrect, the registered contact may not have approved the request, or registry rules may prevent transfer at that time.
Solution
Check the current registrar status, request a fresh authorisation code and confirm that the registered holder or authorised contact can receive transfer approval messages.
The website stops loading after transfer
Likely cause
Nameservers may have changed, DNS records may not have been copied, or the previous DNS provider may no longer be serving the zone.
Solution
Compare the current DNS against the pre-transfer record list. Restore the correct A, CNAME and related records, then allow for DNS propagation.
Email stops sending or receiving properly
Likely cause
MX records or email authentication records may be missing or incorrect. SPF, DKIM and DMARC settings may also have been disrupted.
Solution
Review MX, SPF, DKIM and DMARC records against the email provider’s requirements. If Microsoft 365 or another provider is used, follow that provider’s current DNS instructions.
Professional Support
Can You Transfer a Domain Yourself?
Our Approach
How We Approach Domain Transfers and DNS Management
Domain Transfer FAQs
These answers cover common concerns about domain transfers, DNS and business continuity.
Will my website go down during a domain transfer?
Does transferring a domain move my email?
How long does a domain transfer take?
Need Help Reviewing or Transferring a Business Domain?
If your domain supports a live website, business email or important third-party tools, it is worth checking the setup before making changes. We can review ownership, DNS, hosting and email dependencies, then plan a transfer that aims to minimise disruption. Start a conversation online or call us on +61 4 23 016 104.