Transfer a domain without losing email: preserve DNS and service

You can transfer a domain to another registrar while keeping the same email provider. The transfer changes who manages the registration; it does not copy mailboxes. To keep email working, preserve the DNS records that route and authenticate mail, and keep the email subscription active.

The main trap is assuming that unchanged nameservers guarantee an unchanged service. The old registrar may stop hosting the DNS zone after the domain leaves. A domain can still point at those nameservers while the records it needs are no longer being served.

Identify four separate services

Namecheap’s transfer guidance explains the distinction between nameservers that continue operating and a registrar’s bundled DNS that may end when registration moves. Ask the current provider directly whether its DNS service remains available for your particular account.

Save the complete DNS zone

Export the zone if possible, and keep readable copies of important records. Include MX, SPF, DKIM selectors, DMARC, mail hostnames, verification records, and any service-specific discovery records. Also preserve website, subdomain, and certificate-related records. A screenshot of the two MX lines is not a complete recovery plan.

List sending services separately: employee mail, invoices, marketing software, and website notifications may use different systems. The incoming inbox working does not prove those outgoing paths remain authenticated.

If the existing DNS will continue, a registrar-only transfer may need no mail-record changes. If it will not, establish an independent DNS destination before beginning the transfer. Build the equivalent zone there, verify the records with that provider, and plan the nameserver change while the old service remains available.

Put DNS continuity before the transfer request

1. 01 Preserve services Confirm DNS and mail subscriptions will remain available.
2. 02 Transfer registration Follow the registrars’ eligibility and authorization process.
3. 03 Verify ownership Check renewal, DNS, email delivery, and account recovery.

Check the registrars’ restrictions before relying on a DNS change during a pending transfer. Give yourself time to fix a missing record before a renewal or hosting cancellation deadline. If DNSSEC is enabled and DNS providers are changing, follow their supported migration procedure for the signing keys and parent DS record; this is more than copying ordinary host records.

ICANN’s transfer FAQ describes circumstances in which a transfer may be locked, including recent registration, a recent transfer, or registrant changes. Check eligibility before changing contact details just for housekeeping. Country-code domains can have different registry procedures.

Verify mail from outside your organization

Use an unrelated external mailbox to send a message to each critical address, then reply. Check aliases, shared mailboxes, website forms, and automated invoices. A message between two colleagues can stay inside one mail system and miss a public DNS problem.

For a technical check, compare the domain’s public MX and authentication records with the saved zone. On a system with dig, these are read-only queries; replace the example domain with yours:

dig example.com NS +short
dig example.com MX +short
dig example.com TXT +short
dig _dmarc.example.com TXT +short

DKIM uses provider-specific selector names, so query the selector your service supplies rather than guessing. If results differ between resolvers, record which resolver returned which value and the remaining TTL.

Cancel only what has actually been replaced

Once registration moves, confirm the new expiry date, renewal setting, payment method, and recovery contacts. Keep email and any still-required DNS service paid. A completed domain transfer is not permission to delete the old provider account if that account still holds mailboxes or other services.

If you also want to change email providers, schedule that as a separate migration with a mailbox inventory and data checks. For Microsoft 365 from GoDaddy, use the product-specific transfer path. Keeping the projects distinct makes it much easier to locate a failure and recover without guessing.