Transferring a domain to a new registrar does not have to interrupt a website or business email. This checklist explains how to prepare the domain, preserve DNS, monitor the transfer, verify every service afterward, and maintain a recurring record so future registrar changes are easier to manage.
Overview
A domain transfer moves the registration record from one registrar to another. It is separate from moving website files, changing web hosting, or switching email providers. In a well-planned migration, the domain continues using its existing DNS configuration while the registrar transfer is processed.
The main risk is not usually the transfer itself; it is losing track of a dependency. A domain may support the public website, mailboxes, subdomains, verification records, APIs, staging environments, monitoring tools, and third-party services. Before starting, create an inventory and identify who can approve changes at both the current and new registrars.
Registrar interfaces and transfer requirements vary. A domain may need to be unlocked, protected contact details may need review, and an authorization code may be required. Some domains can be subject to registry or registrar restrictions after certain account or registration changes. Treat the receiving registrar's instructions as the final procedural reference, and resolve any eligibility warning before beginning.
If the transfer is part of a broader website move, separate the tasks. First stabilize hosting and DNS, then transfer the registration where practical. For a wider migration plan, see The Complete Website Migration Checklist.
What to track
Record the following items before you request the domain transfer. A simple spreadsheet, ticket, or password-manager note can provide a useful audit trail without storing sensitive credentials in plain text.
- Domain and registrar details: Record the domain name, current registrar, intended registrar, renewal date, registrar account owners, and the date the transfer was initiated.
- Transfer eligibility: Check whether the domain is unlocked, whether a transfer restriction is displayed, and whether the current registrar requires an account or contact verification step.
- Authorization code: Request the domain authorization code, also called an EPP code or transfer code in some systems. Copy it carefully, note when it was issued, and avoid sharing it in unsecured channels.
- Registrant contact information: Confirm that the administrative email address is monitored and that the registrant details are accurate. Review privacy or redaction settings separately; changing contact details may trigger additional verification at some registrars.
- Nameservers: Capture the current nameservers and confirm which provider hosts the DNS zone. The registrar and DNS host may be different companies.
- DNS records: Export or document A, AAAA, CNAME, MX, TXT, and relevant SRV records. Include records for subdomains, email authentication, domain verification, VPNs, APIs, and development environments.
- Service checks: List the website URL, www version, critical subdomains, inbound and outbound email addresses, SSL certificate coverage, payment or login flows, and any services that depend on the domain.
- Evidence before the change: Save screenshots or test results showing the website loads, email can be sent and received, and important DNS records resolve as expected.
Do not assume that moving a registration also moves DNS hosting. If the nameservers remain unchanged, the existing DNS provider may continue serving the zone. If you plan to change nameservers as well, treat that as a separate migration with its own testing window. Email-specific checks are covered in How to Set Up Business Email on Your Domain.
Cadence and checkpoints
Before starting
- Confirm that you control both registrar accounts and have access to the domain's administrative email address.
- Review the domain's expiration date and leave enough time to resolve an eligibility or verification issue before renewal becomes urgent.
- Document nameservers and DNS records. If the receiving registrar offers DNS import, compare the imported zone with your original record list rather than accepting it without review.
- Ensure automatic renewal settings, payment details, and account recovery methods are configured at the intended registrar.
- Unlock the domain only when you are ready to submit the transfer. Keep the transfer lock enabled at other times as a basic account-control practice.
During the transfer
- Start the transfer at the new registrar and enter the authorization code exactly as provided.
- Record the order or transfer reference and note any approval email, confirmation deadline, or status message.
- Check the domain status at the current and receiving registrars. Do not repeatedly change settings unless the registrar instructs you to do so.
- Continue monitoring the website, DNS resolution, and email while the transfer is pending. Use a DNS propagation checker only as a supporting view; compare results from more than one resolver when diagnosing inconsistent answers.
After completion
- Confirm that the domain appears in the new registrar account and that the registration and renewal information are correct.
- Verify nameservers and key DNS records against the pre-transfer inventory.
- Test the root domain, www host, important subdomains, redirects, login paths, forms, and transactional pages.
- Send test messages in both directions for each important mailbox or mail route. Check that MX and email authentication records remain present.
- Review SSL certificates and browser warnings, especially if the transfer was combined with a DNS or hosting change.
- Enable the new registrar's security controls, including strong authentication, account alerts, and transfer protection where available.
Keep the checklist open until the domain, website, and email have passed their tests. A completed registrar order is not the same as a completed operational migration.
How to interpret changes
A website outage after a registrar transfer does not automatically mean the registration transfer caused it. Start by comparing the current nameservers with the recorded values. If they changed, inspect the DNS zone at the provider listed by those nameservers. Missing A, AAAA, or CNAME records can affect the website, while missing MX or TXT records can affect email delivery and authentication.
Different DNS resolvers may show different answers for a period after a record change. Check the record's time-to-live value, compare authoritative DNS results with recursive resolver results, and avoid making repeated edits that make the investigation harder. If only some users report an issue, record their location, network, resolver, hostname, and timestamp.
For email problems, distinguish between a DNS issue and a mailbox-provider issue. Confirm MX records first, then review SPF, DKIM, and DMARC-related configuration where applicable. A domain transfer should not be treated as an opportunity to redesign email records unless that change is planned and tested separately.
If the transfer remains pending, read the exact status shown by both registrars. An incorrect authorization code, a locked domain, an unconfirmed approval message, or a registrar-specific review can require different actions. Contact support with the domain, transfer reference, timestamps, and screenshots, but do not disclose account passwords or unnecessary private data.
When to revisit
Revisit this record monthly or quarterly for business-critical domains, and at least before each renewal cycle for less active projects. The goal is not to repeat the transfer; it is to confirm that the ownership, renewal, DNS, and recovery information still match the way the domain is being used.
- Monthly: Confirm that automatic renewal is enabled, payment details are current, security alerts are working, and the domain still resolves to the intended services.
- Quarterly: Review registrar account owners, recovery methods, nameservers, DNS hosts, mail routing, and critical subdomains. Remove obsolete verification records and document intentional changes.
- Before renewal: Check the renewal date, renewal term, expected renewal cost shown in the account, privacy settings, and whether the domain is still held in the correct account.
- Before another migration: Export the current DNS zone, test backups, lower risk by separating registrar, DNS, hosting, and email changes, and schedule monitoring for the entire change window.
- After an incident: Update the checklist with the symptom, root cause, resolver or service involved, corrective action, and verification result.
Use this practical closeout sequence whenever you transfer a domain: document the baseline, verify eligibility, preserve DNS, submit the transfer, monitor status, test website and email, secure the new account, and schedule the next review. For broader infrastructure planning, pair it with website backup guidance and a review of whether your DNS and hosting arrangement still fits the site.
