How to Transfer a Domain Without Losing Your Website or Email

Overview

A domain transfer changes the company responsible for managing your domain registration. It is separate from moving your website files, changing web hosting, or migrating an email service. In many cases, the website and email can remain online throughout the transfer because the domain continues using its existing DNS configuration. That continuity depends on careful preparation.

Before starting, identify three separate systems:

• Registrar: The provider where the domain is registered and renewed.
• DNS provider: The service publishing records such as A, AAAA, CNAME, MX, TXT, and NS records. This may be the registrar, your hosting provider, or a separate DNS platform.
• Website and email providers: The services receiving traffic and mail based on your DNS records.

The safest transfer plan preserves the current nameservers and DNS records until the new registrar is confirmed and tested. If you also want to change hosting or DNS providers, treat that as a separate project. Combining several infrastructure changes makes it harder to identify the cause of an outage.

For a broader pre-launch review, see the website launch and migration checklist. If you need to change where the domain points, use the guide to domain DNS records, nameservers, and propagation.

Checklist by scenario

Scenario 1: Moving only the registrar

This is the lowest-risk transfer scenario. Your hosting, DNS, and email providers remain unchanged.

1. Record the current configuration. Export or copy the domain’s nameservers and DNS records. Include email-related MX, SPF, DKIM, and DMARC records, as well as verification records used by analytics, payment, search, or other services.
2. Confirm access to the registrant account. Make sure you can sign in, complete account security checks, and receive messages at the administrative or registrant email address associated with the domain.
3. Check the domain status. The domain may need to be unlocked before a transfer can begin. Look for a registrar lock, transfer lock, or similar setting. If the dashboard is unclear, ask the current registrar what must be changed.
4. Request the transfer authorization code. This may be called an EPP code, auth code, or transfer code. Treat it like a temporary credential and share it only with the new registrar’s transfer form or support process.
5. Start the transfer at the new registrar. Enter the exact domain name and authorization code. Review the transfer destination carefully before submitting.
6. Approve required messages. Check the domain’s contact email and both registrar accounts for transfer instructions. Approval steps vary, so follow the instructions shown by the registrars.
7. Keep the old account active. Do not cancel the old registrar or delete DNS settings until the transfer is complete and the new account has been checked.

Scenario 2: Transferring a domain and changing hosting

Plan the registrar transfer and website migration separately where possible. First copy the website to the new host, test it using a temporary address or staging setup, and confirm that the required SSL certificate is ready. Then decide when to update DNS.

If the nameservers remain unchanged during the registrar transfer, visitors should continue reaching the existing host. After the transfer completes, you can update the relevant DNS records during a controlled migration window. This approach gives you a clear rollback option: restore the previous DNS values if testing reveals a problem.

For WordPress sites, review the staging and launch process in this staging site guide before changing live DNS.

Scenario 3: Transferring a domain used for business email

Email continuity deserves its own check because a small DNS error can affect delivery even when the website still loads. Before transferring, document every MX record and confirm which service handles mail. Also record SPF, DKIM, and DMARC values if they are present.

Do not assume that moving the domain registrar moves mailboxes or messages. Those remain with the email provider unless you separately migrate them. After the transfer, send test messages to and from multiple external addresses, check replies, and confirm that existing mailboxes and aliases still work.

Scenario 4: A domain near expiration

Avoid starting a transfer at the last moment. Review the domain’s expiration date, renewal settings, and any pending notices before you begin. A transfer can take time, and registrar or registry rules may restrict transfers during certain account or registration states. If timing is tight, resolve renewal or status questions with the current registrar before proceeding.

What to double-check

• Nameservers: Confirm that the new registrar shows the intended nameservers. A transfer should not silently replace them, but verify rather than relying on assumptions.
• DNS records: Compare the new account with your saved copy. Check the root domain, www hostname, subdomains, verification records, and any custom records used by applications.
• Email records: Confirm MX, SPF, DKIM, and DMARC entries. Check both inbound and outbound mail.
• DNSSEC: If DNSSEC is enabled, verify that the DS record and signing configuration remain coordinated with the DNS provider. An inconsistent DNSSEC setup can make a domain appear unreachable to validating resolvers.
• Privacy settings: Review domain privacy or contact redaction settings after the transfer. The setting may not carry over exactly, and contact details should be checked for accuracy.
• Renewal and billing: Confirm the new expiration date, auto-renewal preference, payment method, and renewal notification address.
• Account security: Enable available multi-factor authentication, remove unnecessary users, and store recovery details securely.
• HTTPS and redirects: Open the website over HTTPS, test the www and non-www versions, and check important redirects. A registrar transfer should not replace your SSL certificate, but the site should still be tested.

Use a DNS propagation checker only as one input. Compare results from more than one network or resolver, and test the actual website and email rather than treating a single checker result as proof of completion.

Common mistakes

• Changing nameservers unnecessarily: A registrar transfer does not require a DNS provider change. Leave nameservers alone unless you have a separate reason to move DNS.
• Requesting the code from the wrong account: The authorization code must come from the current registrar, not the hosting or email provider.
• Ignoring the transfer contact email: Approval messages can be missed if the address is outdated, protected by an inaccessible mailbox, or filtered as spam.
• Deleting the old account too soon: Keep access until the transfer, DNS, email, and renewal details have all been verified.
• Forgetting non-website services: Chat tools, APIs, SaaS products, certificate validation, and transactional email may depend on DNS records that are easy to overlook.
• Combining too many changes: Moving the registrar, DNS, hosting, and email on the same day creates avoidable troubleshooting work.
• Assuming privacy is permanent: Recheck privacy settings and public registration information after the transfer.

When to revisit

Return to this checklist before every domain transfer, especially before a seasonal campaign, product launch, business rebrand, or planned hosting migration. Revisit it whenever your registrar, DNS provider, email platform, or account security workflow changes.

Keep a current domain inventory with the registrar, expiration date, DNS provider, hosting provider, email provider, renewal owner, and recovery contact. Update the inventory after each infrastructure change. A short record of the last verified DNS and email configuration can save more time than troubleshooting from memory.

When the transfer is complete, perform this final check:

1. Confirm the domain appears in the new registrar account.
2. Verify the nameservers and important DNS records.
3. Open the website over HTTPS and test key pages.
4. Send and receive test email from an external mailbox.
5. Review privacy, DNSSEC, renewal, billing, and account security settings.
6. Keep the old registrar account and transfer notes until the results are stable.

For future moves, save this checklist with your domain inventory. Separating registrar changes from hosting and DNS changes is the simplest way to transfer a domain without losing the website or email services that depend on it.