Transferring a domain is usually straightforward, but a rushed move can interrupt email, expose account weaknesses, or leave ownership and renewal details unclear. This reusable checklist explains how to transfer a domain to a new registrar while keeping control of DNS, websites, email, security settings, and renewal records.
Overview
A registrar transfer moves the management of a domain from one registrar to another. It does not automatically move your website files, hosting account, mailbox contents, or DNS records. Those services may remain where they are unless you separately migrate them.
The safest approach is to separate the transfer into three parts: prepare the domain, authorize the move, and verify every connected service afterward. Before starting, identify who owns the domain, who can access the current registrar account, where DNS is hosted, and which systems depend on the domain.
Use this comparison to clarify what changes during a transfer:
| Item | Usually affected by registrar transfer? | Action to take |
|---|---|---|
| Registrar account and billing | Yes | Create or confirm the destination account and payment details. |
| Domain ownership and contact records | May require review | Confirm registrant information and account access before approval. |
| DNS records | Depends on the DNS provider | Export or document records and confirm the authoritative nameservers. |
| Website hosting | No, unless separately migrated | Keep hosting active until the website is verified after the move. |
| Email hosting | No, unless separately migrated | Preserve MX, SPF, DKIM, and related records. |
| SSL certificates | Usually no | Check certificate management if DNS or hosting settings will change. |
If you are also changing hosting, treat that as a separate project. The website migration checklist can help you plan files, databases, testing, and cutover independently from the registrar move.
Checklist by scenario
Before you move any domain
- List the domain, current registrar, destination registrar, renewal date, and current owner.
- Confirm that you can sign in to the current registrar and access its security verification method.
- Verify the domain is not close to an important launch, campaign, renewal, or contract deadline.
- Record current nameservers and DNS records, including A, AAAA, CNAME, MX, TXT, and any verification records.
- Confirm that the website, email, payment systems, APIs, and third-party tools are still working.
- Check the current registrar’s transfer instructions, domain lock setting, privacy behavior, and any transfer-related charges.
- Make sure the domain is eligible for transfer under the applicable registrar and top-level-domain rules. Requirements can vary, so use the registrar’s current guidance rather than relying on an old checklist.
When you need the domain authorization code
Most transfers require an authorization code, also called an EPP code or transfer code. Request it from the current registrar through its domain-management area or support process. Treat the code as sensitive account information: use the official registrar dashboard, avoid sharing it in public tickets or chat channels, and request a fresh code if you suspect it has been exposed.
- Unlock the domain if the current registrar shows a registrar lock or transfer lock.
- Request or retrieve the authorization code.
- Start the transfer at the destination registrar using the exact domain name and code.
- Review the destination registrar’s contact, billing, and renewal settings before submitting.
- Approve any confirmation messages sent to authorized contacts or accounts.
- Monitor both registrar accounts until the transfer shows as complete.
When DNS is managed separately
A domain can be registered at one company while its DNS is hosted elsewhere. In that case, the registrar transfer should not require changing nameservers. Record the current nameservers and confirm they remain assigned after the transfer. If you plan to move DNS too, copy the complete zone first and lower relevant DNS TTL values only when you understand the timing and rollback plan. For record-by-record guidance, see DNS records explained for websites and email.
When ownership or access is changing
Do not combine a registrar transfer with an ownership change unless you have documented approval and understand the consequences. First establish who controls the domain account, registrant contact, recovery email, and multifactor authentication. Keep a written handover record containing the domain, responsible owner, renewal date, DNS provider, hosting provider, and recovery contacts. Remove former administrators only after the new owner has confirmed access.
What to double-check
- Renewal date: Record the date before and after transfer. Confirm whether the destination account has automatic renewal enabled and whether its billing contact is current.
- Nameservers: Compare the nameservers before starting and after completion. A change can affect both the website and email.
- Email records: Verify MX records and the TXT records used for SPF, DKIM, DMARC, domain verification, and other services.
- Website access: Test the main domain, www version, redirects, forms, login pages, and any important subdomains.
- Security controls: Recheck multifactor authentication, recovery addresses, domain lock, DNS account access, and registrar notifications.
- Privacy settings: Review domain privacy or WHOIS privacy settings at the destination registrar. Availability and display behavior can differ by domain type and registrar.
- Certificates and integrations: Confirm that HTTPS works and that payment providers, analytics, APIs, deployment tools, and verification services still recognize the domain.
Use a simple post-transfer verification note: “Domain transfer complete: registrar confirmed; nameservers unchanged; website tested; inbound and outbound email tested; HTTPS tested; renewal and auto-renewal reviewed; MFA and recovery contacts confirmed.” Store it with your infrastructure records.
Common mistakes and domain transfer problems
The domain remains locked. Return to the current registrar and check the transfer-lock status. Some dashboards display several locks, so confirm which setting controls registrar transfers.
The authorization code fails. Copy it carefully, check for hidden spaces, and request a new code if it may have expired or been regenerated. If the error continues, ask the current registrar whether the code is valid for the exact domain.
The transfer is delayed. Review both registrar accounts for pending approval messages, verification requests, or support notices. Do not cancel the old account until the destination registrar confirms completion.
Email stops working. Compare MX and authentication records with your pre-transfer notes. If nameservers changed, restore the intended DNS configuration and allow time for DNS changes to be observed across networks.
The website disappears. Check nameservers, A and AAAA records, CDN settings, and hosting configuration before changing website files. A registrar transfer alone does not move hosting content.
Access is lost after the move. Confirm the destination account owner, recovery email, MFA device, and administrator roles. Keep evidence of ownership and registrar correspondence available for support.
When to revisit this checklist
Review this process before every domain transfer, ownership change, registrar consolidation, renewal cycle, or website migration. It is especially useful during seasonal planning when teams are cleaning up portfolios or changing vendors. Recheck it whenever a registrar changes its dashboard, authorization workflow, privacy controls, billing process, or transfer instructions.
For a practical final pass, schedule the transfer during a period when someone can monitor the website and email. Export or document DNS first, confirm account recovery access, start the transfer with the authorization code, and test every dependent service after completion. Keep the registrar, DNS, hosting, renewal, and ownership details in one maintained inventory. That small record reduces the chance that a future transfer becomes an emergency.
If the move is part of a broader infrastructure change, pair this checklist with the website security and uptime checklist and the guide to backing up website files and databases. A registrar transfer is safest when ownership, DNS, hosting, security, and recovery are treated as connected parts of the same domain-management plan.
