Transferring a domain does not have to interrupt a website or email service. This guide provides a practical workflow for preparing the domain, preserving DNS records, coordinating the registrar change, checking each service, and monitoring the setup after the transfer.
Overview
A domain transfer moves the registration from one registrar to another. It does not automatically move your website files, databases, mailboxes, SSL certificates, or hosting account. Those services may continue running at the same provider throughout the transfer, provided the domain’s DNS configuration remains correct.
The safest approach is to separate the registration change from any hosting migration. First, document the current DNS and hosting setup. Next, unlock the domain and request its authorization code, sometimes called an EPP or transfer code. Then submit the transfer at the new registrar while keeping the existing nameservers in place unless you have a specific reason to change them.
Nameservers are especially important. They identify the DNS service that answers requests for your domain. If the domain continues using the same nameservers during the registrar transfer, the website and email records can usually continue resolving as before. Changing registrars and nameservers at the same time creates two separate changes to troubleshoot, so avoid combining them unless your migration plan requires it.
Before starting, identify who controls each part of the system: the current registrar, DNS provider, web host, email provider, CDN, and certificate management. If you are also moving the website to new web hosting, use a separate pre-move checklist such as this hosting migration guide.
What to track
1. Domain eligibility and account access
Confirm that you can sign in to the current registrar and that the domain is not close to expiration. Check the domain status for a registrar lock or transfer lock, and review whether any account security setting could delay the request. Some domain types have additional transfer requirements, so check the relevant registrar instructions before submitting a transfer.
Verify that the administrative or registrant contact details are current. Transfer communications may depend on account notifications or approval steps. Avoid changing ownership details immediately before a transfer unless necessary, because a contact change can affect transfer eligibility under the registrar’s process.
2. The authorization code and transfer status
Request a fresh authorization code if the existing code is missing, expired, or rejected. Store it securely and enter it carefully at the new registrar. Record the date and time of the request, the transfer order number, and any status shown in either registrar’s control panel.
Useful status notes include whether the domain is unlocked, whether the transfer is pending, whether an approval is required, and whether the transfer has completed. Do not assume that an order submission means the transfer is finished; confirm completion in the new account.
3. Every DNS record
Export or copy the complete DNS zone before making changes. At minimum, record:
- A and AAAA records for the website or other servers
- CNAME records for subdomains and hosted services
- MX records for email delivery
- TXT records for SPF, DKIM, DMARC, verification, and other services
- CAA records if your certificate setup uses them
- SRV records for services that require them
- Existing redirects, subdomain records, and DNS-specific settings
Also note the current nameservers and the DNS provider responsible for editing the zone. A registrar transfer may leave these nameservers unchanged, but you should verify that explicitly rather than relying on an assumption.
4. Service checks
Make a short inventory of the services that depend on the domain. Test the main website, important subdomains, webmail, inbound email, outbound email, transactional messages, APIs, and any third-party login or verification process. Take a backup of website data and confirm that you can restore it if a separate hosting problem occurs. For a broader backup routine, see this website backup strategy.
Cadence and checkpoints
Before the transfer
- Choose a low-risk maintenance window, even if no interruption is expected.
- Record the domain’s current registrar, expiration date, nameservers, and DNS records.
- Confirm website, email, and hosting access with a second administrator where possible.
- Unlock the domain and obtain the authorization code.
- Check that the destination registrar account is ready and that the domain spelling is correct.
If DNS changes will be part of the move, review record time-to-live values in advance. Lowering a TTL may help resolvers check for changes sooner, but it does not instantly clear every cached answer. Make the change early enough to be useful, and restore an appropriate TTL after the migration has stabilized.
During the transfer
Submit the transfer request and save the confirmation details. Monitor messages from both registrars, but do not cancel the old registration or remove the existing DNS zone prematurely. If an approval step is available, follow the instructions shown in the relevant account. Keep the existing website and email service operating until the new registrar confirms completion.
Immediately after completion
Check the new registrar’s account for the domain, expiration information, nameservers, DNSSEC status if used, and transfer lock setting. Confirm that the nameservers match your intended configuration. Then test the website over both the root domain and the www hostname, check several important subdomains, and send test messages in both directions.
DNS management panels can display records differently, so compare the live result with the inventory you created before the transfer. If the new registrar also provides DNS hosting and you intend to use it, recreate and verify the zone before switching nameservers.
How to interpret changes
A working website at one location does not prove that the entire domain setup is healthy. Test from more than one network or use independent DNS lookup tools to compare the nameservers and key records. Differences between locations may reflect caching, propagation, or an inconsistent DNS zone rather than a failed domain transfer.
If the website fails but email works, inspect the A, AAAA, and CNAME records and confirm that the hosting account still accepts the domain. If email fails while the website works, review MX, SPF, DKIM, and DMARC records first. If only one subdomain fails, compare its individual record with the saved DNS inventory.
An SSL warning usually points to certificate coverage, hostname configuration, or a DNS destination that does not match the certificate. A registrar transfer does not automatically issue or renew a certificate. If you use cPanel, refer to this SSL setup walkthrough and verify the certificate for every hostname visitors use.
Do not repeatedly edit records while results are still being cached. Record each change, its time, and the expected result. This creates a useful timeline and reduces the risk of correcting one resolver’s old answer by changing a configuration that was already correct.
When to revisit
Revisit the transfer record the next day, again after several days, and at least once during the following month. Confirm that the domain remains in the correct account, renewal details are understood, nameservers are unchanged or intentionally updated, and website and email checks still pass. Add the new registrar and DNS provider to your internal asset inventory and password-management process.
Review the setup quarterly, or sooner when a recurring data point changes: the domain approaches renewal, a DNS provider changes, email services are replaced, a subdomain is added, DNSSEC is enabled or disabled, or hosting moves to a different platform. Keep an up-to-date DNS export and a current list of owners and recovery contacts.
Finally, treat a future registrar transfer as a controlled change rather than an emergency task. Confirm backups, document the DNS zone, test contact access, and schedule monitoring before you begin. This preparation helps preserve continuity whether you are moving to domain hosting with a new control panel, consolidating domains, or pairing registration with cloud hosting.
