Transferring a domain does not have to interrupt your website or email. This practical domain transfer checklist explains what to verify before, during, and after a registrar migration so your DNS, hosting, SSL, renewal settings, and security controls continue working.
Overview
A domain transfer moves the registration record from one registrar to another. It does not normally move your website files, database, hosting account, email mailbox, or DNS zone automatically. Keeping those services separate is the key to transferring a domain without downtime.
Before you begin, identify three providers or systems involved in your setup:
- Registrar: The company where the domain is registered and renewed.
- DNS provider: The service answering queries for records such as A, AAAA, CNAME, MX, TXT, and verification records. This may be the registrar, your web host, or a separate DNS host.
- Hosting and email providers: The systems serving your website and handling mail. A registrar transfer does not replace either service.
In a low-risk migration, the domain keeps using its existing nameservers throughout the transfer. The new registrar takes over registration and renewal management, while DNS continues to point to the same website and email services. For background on the wider setup, see this DNS, SSL, and propagation checklist.
Transfer eligibility varies by domain extension, registrar, account status, and recent changes. Treat the registrar's current transfer instructions as authoritative, and allow extra time when the domain supports a business-critical website or business email.
Checklist by scenario
Before transferring any domain
- Confirm the domain is not expired or in a recovery state. Renew it first if the registration is close to expiration. A transfer is a poor time to resolve an expired-domain problem.
- Check the transfer lock. Registrars commonly provide a lock or transfer-protection setting. Disable it only when you are ready to request the transfer, then re-enable protection after completion.
- Request the authorization code. This may be called an EPP code, transfer code, or auth code. Store it securely and use the latest code supplied by the current registrar.
- Verify the domain contact and account email. Make sure you can receive transfer notices and approve requests where required. Do not assume that changing the account login also changes the domain's operational contact details.
- Record the current configuration. Export or copy the nameservers, DNS records, renewal date, auto-renewal setting, privacy setting, DNSSEC status, forwarding rules, and domain contacts.
- Confirm your hosting and email are healthy. Test the website, HTTPS version, key forms, transactional mail, inbound mail, and any important subdomains before making changes.
Take a screenshot or save a text record of the current DNS zone. Pay particular attention to MX records for email, TXT records used for SPF or domain verification, CNAME records for services, and any records for staging, APIs, or developer tools.
If DNS is managed by the current registrar
Decide whether to move DNS to the new registrar or keep it with a separate DNS provider. If you move DNS during the registrar transfer, recreate every required record before changing nameservers. A safer sequence is often to move DNS first, confirm it works, and then transfer the registration.
When moving a DNS zone, compare the old and new records line by line. Check record names, values, priorities, ports, trailing dots where relevant, and proxy or routing settings. Do not rely only on a website loading; email and third-party integrations may fail even when the homepage works.
If the website or email must remain online
Keep the existing nameservers unchanged during the registrar migration unless there is a specific reason to change them. The transfer should then affect the registrar account rather than the destination of web and mail traffic.
Schedule the work when you can monitor it. Notify relevant users if the domain supports business email, customer logins, payment flows, webhooks, or other time-sensitive services. Keep access to the old registrar until the transfer is confirmed and the new account has been secured.
If you are also moving to a new host
Separate the two projects. First copy the website, database, configuration, mailboxes, and backups to the new host. Test the site using a staging address or temporary hostname, then prepare the new DNS records. Once the new host is ready, change DNS according to a planned cutover and verify propagation. Transfer the registrar separately when practical.
This approach makes troubleshooting clearer: a registrar transfer problem, a DNS change, and a hosting migration are different failure points. For environment planning, compare the role of staging and production hosting before changing a live site.
What to double-check
DNS and nameservers
After the transfer, confirm the nameservers still match your intended DNS provider. Use a DNS lookup tool from more than one network or resolver when possible. Check the apex domain, the www hostname, important subdomains, MX records, and TXT records. DNS results may differ temporarily because resolvers cache records, so verify over time rather than treating one lookup as conclusive.
SSL and website behavior
Open both HTTP and HTTPS versions of the site, including important pages and forms. Confirm that the certificate covers the hostnames visitors use and that redirects behave as expected. A registrar transfer should not normally replace a certificate, but a nameserver or hosting change can affect certificate validation and renewal.
Email and authentication
Send a test message to and from the domain. Check aliases, forwarding, autoresponders, mailing lists, and applications that send mail. Confirm that SPF, DKIM, and DMARC-related records remain present if your email provider uses them. Also review login alerts and recovery addresses for the registrar account.
Renewal and billing
Confirm the domain appears in the new registrar account with the correct expiration date, renewal term, auto-renewal preference, and payment method. Review whether a transfer changes the expiration date under the applicable extension and registrar terms rather than assuming the outcome. Set a calendar reminder even when auto-renewal is enabled.
Security controls
Enable multi-factor authentication on the new registrar account, use a unique password, and check every user or delegate with access. Re-enable the domain transfer lock when the migration is complete. Review privacy protection, DNSSEC, API keys, access tokens, and domain forwarding. Remove old registrar users and revoke credentials that are no longer needed.
Common mistakes
- Changing nameservers unnecessarily: A registration transfer and a DNS migration are separate operations. Changing both at once makes it harder to identify the cause of an outage.
- Assuming hosting moves with the domain: Website files, databases, mailboxes, and backups remain where they were unless you migrate them separately.
- Forgetting non-website records: MX, TXT, DKIM, verification, API, and subdomain records can be more operationally important than the homepage A record.
- Starting immediately after a domain change: Recent changes to registrant details or other settings may affect transfer eligibility. Check the current registrar guidance before editing contacts close to the migration.
- Using an old authorization code: Codes can expire or be replaced. Request a fresh code when needed and protect it like an account credential.
- Closing the old account too soon: Keep access until DNS, email, SSL, renewal data, and security settings have all been verified.
- Testing only from one device: Local DNS caches can hide problems. Test from different networks and use independent DNS lookups.
If the goal is to move the website as well as the domain, create a separate migration plan with a full backup and rollback point. The guidance on website backups can help you define what must be recoverable before the cutover.
When to revisit
Use this checklist before every registrar migration, even if you have transferred domains before. Revisit it before seasonal planning cycles, major campaigns, company changes, hosting moves, and any update to your DNS or email architecture. Registrar interfaces, transfer workflows, domain-extension requirements, and security options can change, so confirm the current instructions at the time you act.
For a practical final review, complete these steps in order:
- List the registrar, DNS provider, host, and email provider.
- Save the current DNS zone and domain settings.
- Verify the site, email, SSL, backups, renewal date, and account access.
- Unlock the domain and obtain a current authorization code.
- Submit the transfer without changing nameservers unless planned.
- Monitor transfer status and keep the old registrar available.
- After completion, secure the new account, re-lock the domain, and test every critical service.
Record the completed checks in your maintenance documentation. The next transfer will be safer and faster when the domain's dependencies, DNS records, renewal settings, and recovery contacts are already documented.
