Moving a domain to a new registrar does not have to interrupt your website, email, or other online services. This practical domain transfer checklist explains how to prepare, verify eligibility, preserve DNS settings, compare costs, and complete the move with a controlled handoff.
Overview
A domain transfer changes the company that manages your domain registration. It does not automatically move your website files, hosting account, email inboxes, databases, or DNS-hosted services. Keeping that distinction clear is the foundation of a safe migration.
In many cases, your existing DNS records continue to direct visitors to the same hosting provider during and after the registrar transfer. However, this depends on how your DNS is configured. If your current registrar also provides authoritative nameservers and you change or remove those nameservers during the move, the website or email service may stop resolving correctly.
The safest approach is to treat the transfer as a sequence of separate tasks:
- Confirm that the domain is eligible to move.
- Record the current registration, DNS, and contact details.
- Prepare the new registrar account and review its pricing.
- Request the domain authorization code or transfer code.
- Submit the transfer and complete any required confirmations.
- Verify DNS, website, email, renewal, and security settings afterward.
Before choosing a destination registrar, compare more than the promotional price. Review the standard renewal cost, transfer cost, privacy options, support channels, account security features, DNS controls, and the registrar’s process for recovering access. The domain registration pricing guide can help you separate first-year offers from the costs that matter over the life of the domain.
Checklist by scenario
Scenario 1: Moving a personal or low-traffic domain
For a domain with no critical business services, start with a basic preparation checklist:
- Confirm the domain name, current registrar, expiration date, and registrant account.
- Check whether the domain is locked against transfers.
- Locate the registrar’s transfer or authorization code request.
- Confirm that the administrative contact email or account contact details are accessible.
- Compare the destination registrar’s transfer and renewal pricing.
- Save a copy of the current DNS records and nameserver values.
- Start the transfer from the new registrar only after reviewing its instructions.
A domain transfer may extend the registration term in some situations, while other cases may be treated differently depending on the extension and registrar. Do not assume that a transfer is free, that it always adds a year, or that the same billing rules apply to every domain extension. Check the transaction summary before paying.
Scenario 2: Domain used for a live website
For a production website, DNS continuity is more important than the registrar interface itself. Before initiating the transfer:
- Identify the authoritative nameservers for the domain.
- Record A, AAAA, CNAME, MX, TXT, and any verification records currently in use.
- Confirm where DNS is hosted: the current registrar, the web host, a CDN, or a separate DNS provider.
- Check that the website works on both the root domain and the
wwwhostname if both are used. - Make sure you can access the hosting and DNS provider accounts independently of the registrar.
If the nameservers will remain unchanged, the registrar move may not require a DNS redesign. If you plan to move DNS at the same time, treat that as a separate migration and test it independently. The domain and hosting setup checklist provides a broader way to review the relationship between the domain, DNS, and hosting layers.
Scenario 3: Domain used for business email
Email deserves its own check because a website can appear healthy while mail delivery is broken. Record the MX records and any TXT records used for email authentication or service verification. These may include SPF, DKIM-related records, domain verification records, or other provider-specific entries.
Do not delete or replace email records merely because the registrar is changing. Confirm which provider operates email, identify the account that controls the relevant DNS zone, and test sending and receiving before and after the transfer. If the transfer includes a nameserver change, schedule extra validation for email rather than relying only on a browser test.
Scenario 4: Moving several domains
For a portfolio transfer, create a spreadsheet with one row per domain. Include the extension, current registrar, expiration date, transfer eligibility, lock status, authorization code status, DNS provider, email dependency, destination account, transfer submission date, and final verification date.
Move a low-risk domain first if practical. This gives you a chance to learn the destination registrar’s workflow before transferring a domain that supports a major website or important email addresses. You can also use the domain and hosting cost calculator to estimate the budget impact of moving multiple domains.
What to double-check
| Item | What to verify | Why it matters |
|---|---|---|
| Registrar lock | Whether the domain is marked as transferable | A transfer cannot usually proceed while a registrar-level lock or restriction remains active. |
| Authorization code | How and where the current registrar provides the code | The destination registrar may require this code to identify and authorize the transfer. |
| Contact access | That you can receive required notices or sign in to the relevant account | Confirmation steps can be delayed if contact details or account access are outdated. |
| Expiration timing | Whether there is enough time to complete the process comfortably | A transfer should not be started casually when the domain is close to expiration or involved in a dispute. |
| DNS records | Nameservers and the complete active record set | These records direct web traffic, email, verification services, and other applications. |
| Costs | Transfer charge, renewal price, taxes, add-ons, and future billing terms | A low introductory price may not represent the long-term cost. |
| Security | Two-factor authentication, recovery options, and account permissions | The registrar account controls an important part of your online identity. |
Eligibility rules can vary by domain extension, registrar, registration history, and account status. Some domains may have additional requirements or restrictions. Treat the destination registrar’s current transfer screen and the current registrar’s instructions as the final operational references, especially when moving a less common extension.
After submission, save the confirmation email, transaction ID, and any stated completion window. During the transition, avoid making unnecessary changes to nameservers, DNS records, registrant details, or hosting configuration. Fewer simultaneous changes make troubleshooting much easier.
Common mistakes
- Changing DNS during the registrar transfer without a plan. A transfer and a DNS migration are different projects. Combining them increases the number of variables during an outage.
- Comparing only the first-year price. Include renewal charges, transfer costs, privacy fees, paid support, taxes, and optional security products when comparing registrars.
- Forgetting email records. MX and TXT records are easy to overlook when copying only the website’s A or CNAME record.
- Waiting until the last moment. A transfer may require account access, code retrieval, confirmation, or support intervention. Build in time for unexpected steps.
- Assuming the website is the only service affected. Check email, APIs, SSL or certificate validation, analytics, payment integrations, staging environments, and third-party verification records.
- Discarding the old account too soon. Keep access to the former registrar and DNS provider until the transfer, billing, and service checks are complete.
- Failing to document the final state. Record the new registrar, renewal date, nameservers, DNS provider, and account owner so the next review does not begin from scratch.
If you are also changing hosting, review a structured domain and hosting comparison guide before deciding which parts of the setup should move together.
When to revisit
Revisit this checklist before every domain transfer, even if you have used the same registrar before. Registrar interfaces, transfer instructions, prices, privacy options, and confirmation workflows can change. Domain extensions may also have different requirements, so a process that worked for one domain is not automatically suitable for another.
It is also useful to review your registrar arrangement during an annual planning cycle. Check whether renewal pricing still fits the budget, whether the account has current recovery details, whether two-factor authentication is enabled, and whether the domain portfolio is documented. If you are evaluating a new extension, compare its registration and renewal terms with the alternatives in the guide to domain extensions by website type.
Use this final action list before you click the transfer button:
- Choose the destination registrar after comparing ongoing costs and controls.
- Export or record DNS, hosting, and email details.
- Confirm transfer eligibility, lock status, and account access.
- Request and securely handle the authorization code.
- Submit the transfer and complete required confirmations.
- Monitor the domain status without making unrelated configuration changes.
- Test the website, email, DNS records, and key integrations.
- Record the new renewal date, registrar, and responsible account owner.
A careful domain transfer is primarily a documentation and sequencing exercise. Keep registration, DNS, hosting, and email responsibilities separate in your notes, change one major layer at a time, and verify each service before closing the old arrangement.
