A domain transfer does not have to interrupt your website or email. This practical checklist explains how to prepare DNS, confirm transfer eligibility, obtain the domain authorization code, protect email continuity, monitor the handoff, and verify everything after the move.
Overview
A domain transfer moves the registration from one registrar to another. It is separate from moving your website files, changing your hosting provider, or redesigning your site. In many cases, the website can remain online throughout the transfer because the domain's existing nameservers and DNS records continue to direct visitors to the same infrastructure. However, this depends on how the current and new registrars handle DNS management, so preparation matters.
The safest approach is to treat a transfer as a controlled administrative change rather than a last-minute technical task. First document the current domain and DNS configuration. Then confirm that the domain is eligible, unlock it, request its domain authorization code, and start the transfer with the new registrar. Keep the existing hosting and email services active until you have verified the transfer and all critical records.
Before making changes, record the domain's expiration date, current registrar, account owner, nameservers, and administrative contact email. Also identify who controls the DNS zone. DNS may be managed by the registrar, a separate DNS provider, a hosting platform, or a security service. If you are unsure, use a DNS lookup tool or the provider's control panel to confirm the authoritative nameservers. For background, see this guide to nameservers and DNS records.
Checklist by scenario
Scenario 1: Transferring the domain while keeping the current website and email
- Document the current setup. Save a copy of the DNS records, including A, AAAA, CNAME, MX, TXT, and any verification or security records. Note the current nameservers and confirm where the zone is hosted.
- Check the domain status. Look for registrar locks, pending updates, expiration concerns, or other restrictions. Some domain extensions and recent account changes may have transfer eligibility requirements. Check the current registrar's instructions for the specific extension.
- Confirm access to the registrant account and contact email. You may need account access to unlock the domain or request the authorization code. A transfer-related message may also be sent to an address associated with the registration.
- Disable the transfer lock. Registrars often provide a transfer-lock control in the domain management panel. Disable it only when you are ready to begin, and re-enable it if the transfer is postponed.
- Request the domain authorization code. This code may also be called an EPP code or transfer code. Copy it carefully and use the current code supplied by the registrar rather than an old saved version.
- Start the transfer at the new registrar. Enter the exact domain name and authorization code. Review the transfer summary, renewal settings, DNS options, and contact details before submitting.
- Monitor the approval process. Watch the account dashboard and the relevant administrative email address. Follow the new registrar's confirmation steps promptly, but do not approve a cancellation or transfer request you did not initiate.
- Verify service after completion. Confirm that the domain appears in the new account, the nameservers are correct, the website loads over HTTPS, and email can send and receive. Keep the old registrar account available until these checks are complete.
Scenario 2: Transferring the domain and moving hosting at the same time
Combining a domain transfer with a website migration creates more variables. A lower-risk sequence is to prepare the new hosting environment first, test the site using a temporary address or local configuration, and copy the DNS records before changing nameservers. Once the new website is ready, decide whether to transfer the domain before or after the DNS change based on your providers' requirements.
Do not assume that a domain transfer also moves website files, databases, SSL certificates, backups, or email mailboxes. Those are separate migration tasks. Create a backup of the site and database, identify the required runtime settings, and document scheduled jobs, API integrations, and environment variables. The cloud hosting backup strategy guide provides a useful framework for planning this part of the move.
For a business website, lower the DNS TTL ahead of a planned DNS change if your provider allows it, while remembering that cached values may not change immediately everywhere. Test the new site before switching traffic, and keep the old hosting active until the new environment is stable.
Scenario 3: Protecting a custom email domain
Email deserves separate attention because a website can appear healthy while mail delivery is failing. Before the transfer, record every MX record and any related TXT records used for SPF, DKIM, DMARC, domain verification, or email security. Also record any CNAME records used by an email provider.
If the nameservers will remain unchanged, the transfer itself may not require an email DNS change. Still, verify the records before and after completion. If you will move DNS providers, recreate the full zone first and confirm that the new MX and TXT records match the active configuration. Avoid deleting the old DNS zone until mail flow has been tested from more than one address.
Scenario 4: A domain that cannot be transferred immediately
If the domain is locked, recently updated, close to expiration, involved in a dispute, or subject to an extension-specific restriction, pause rather than repeatedly submitting transfer requests. Ask the current registrar why the transfer is unavailable and check the registry or registrar documentation for the applicable requirement. You can often prepare the DNS inventory, backups, account access, and new registrar account while waiting for eligibility to change.
What to double-check
- Domain spelling: Confirm the exact domain, including its extension. A transfer request for a similar-looking domain is a different transaction.
- Ownership and contact details: Make sure the account and registrant information are controlled by the appropriate person or organization. Keep contact email access available during the transfer.
- Nameservers: Compare the nameservers before starting and after the transfer. A registrar change should not automatically mean a DNS provider change, but provider workflows differ.
- DNS records: Check A and AAAA records for the website, MX records for mail, CNAME records for services, and TXT records for verification and email security. The DNS records guide explains the role of each record type.
- SSL and redirects: Confirm that HTTPS still works and that www, non-www, HTTP, and HTTPS versions resolve as intended. Review the redirect configuration guide if traffic behavior changes.
- Renewal and billing settings: Review the new registrar's renewal date, auto-renewal status, payment method, and transfer-related terms. Do not rely on memory for renewal ownership after the move.
- Monitoring: Watch website uptime, DNS responses, and email delivery during and after the transfer. An uptime monitoring plan can help identify a real service interruption instead of relying on occasional manual checks.
Common mistakes
Changing nameservers unnecessarily. If the current DNS provider is working, leaving the nameservers unchanged can reduce risk. Change them only when you intentionally want to move DNS management.
Transferring without a DNS copy. A transfer is not a substitute for documentation. Save the zone before beginning, especially when the registrar also hosts DNS.
Letting the domain expire during the process. Begin with enough time to resolve an eligibility issue or approval delay. If expiration is approaching, contact both registrars and confirm the safest order of operations.
Moving hosting, DNS, and email at once without testing. Separate the changes where possible. If several changes must happen together, create a rollback plan and keep the old services available.
Ignoring provider-specific instructions. Transfer workflows vary by domain extension and registrar. Check the current instructions instead of assuming that a process used for one domain will work for another.
Deleting the old account too soon. Keep access to the former registrar, DNS provider, hosting account, and email service until the domain, website, and mail have all been verified.
When to revisit
Use this checklist whenever a domain transfer is planned, but revisit the details before each transfer rather than treating an old procedure as permanent. Registrar interfaces, approval workflows, DNS providers, hosting architectures, and extension-specific requirements can change. Review the plan before seasonal business periods, major launches, ownership changes, or a planned hosting migration.
A practical final review is simple: confirm the domain is eligible, export the DNS records, verify account and email access, unlock the domain, obtain a current authorization code, and decide whether nameservers will change. After submitting the transfer, monitor approval messages and test the website, HTTPS, DNS, and email. Once everything is stable, update your internal documentation with the new registrar, renewal date, DNS provider, and responsible owner.
If a transfer fails, record the exact error message and check the domain status, lock state, authorization code, contact email, and eligibility conditions before trying again. Avoid making unrelated DNS or hosting changes while troubleshooting. A clear change log makes it easier to identify the cause and return to a known working configuration.
