Transfer a domain without losing business email: what must stay connected

First identify what the word transfer means

People say they are "moving the domain" when they mean very different jobs: transferring registration to another provider, changing nameservers, connecting a new website or moving email mailboxes. Write down exactly which of those is happening. A new website does not automatically require a new email provider, and a registrar transfer is not the same as migrating a mailbox.

Ask the current provider whether email or DNS is bundled with a service you intend to cancel. Even if the website no longer uses that hosting, its account may still run mailboxes or the DNS zone. Keeping the domain name itself does not keep those separate services alive if their subscription is closed.

• Changing the website domain name itself?

Map the mail service before changing DNS

Identify the active email provider and the person who administers it. Record the existing DNS configuration securely, including MX records that direct incoming mail and the authentication records used by authorised senders. Your website form or invoicing system may send through a different service from staff email.

If nameservers will change, ask the person doing the work to recreate all required records at the new DNS host before the switch. Do not copy only the website address and assume the rest is optional. Have that person check provider instructions for the specific domain rather than pasting generic values from an unrelated tutorial.

Keep a website change smaller when email works

For a website-only change, it may be sufficient to update the required website records at the existing DNS host. Leave working mail records alone unless a separate, understood change is necessary. If a registrar transfer will retain nameservers, confirm that the existing DNS service remains available after the old arrangement ends. A .au registrar transfer uses a domain-specific EPP authInfo code, not your account password. Confirm the registrant contact can receive the code through the provider’s official process before scheduling the move.

If mailboxes genuinely need moving, plan it as an email project. Agree account creation, historical mail migration, aliases, shared mailboxes, devices and the switch in delivery. A domain registration transfer does not copy old messages or configure staff phones. Ask who is responsible for those tasks and what evidence will show the move worked.

Test more than an email sent to yourself

Before and after the change, send from an external mailbox into the business and reply to it. Test aliases, shared addresses and website-generated messages through their actual routes. A message between two staff accounts may not exercise external delivery. The form-delivery guide explains how to trace a missing notification.

Keep the old arrangement available for an agreed overlap and recovery plan where practicable. Do not announce a universal "DNS propagation time" as a completion guarantee: caches and provider processes differ. Use observed delivery and the provider’s guidance to decide whether it is safe to retire old services.

• Trace a missing website enquiry email

Document what remains after the transfer

At completion, keep the registrar, DNS host and email provider listed separately with renewal and support contacts. Verify the business can recover those accounts without the former contractor. Check any automated sending service still has its required DNS records and that important delivery errors reach someone who can act on them.

My website migration planning treats working email as a business requirement, not an incidental technical detail. If you are changing providers, bring the existing account names and invoices. We can establish whether a minimal website connection change will do, or whether domain and email work needs its own agreed scope.

Sources and further reading

• auDA: transferring your .au domain name
• Google Workspace: missing contact-form messages
• Resend: verified sending domains