Transferring a domain to a new registrar does not have to interrupt your website or email. This domain transfer checklist helps you inventory dependencies, estimate cost and timing, prepare the EPP or Auth-Code, verify DNS ownership, and create a rollback plan before you move a domain.
Overview
A registrar transfer changes the company that manages your domain registration. It does not automatically move your website files, cloud server, email inboxes, DNS zone, SSL certificates, or application databases. That distinction is the key to avoiding downtime.
Before you move a domain, identify where each service is hosted and which system controls its DNS. A domain may be registered with one provider, use nameservers operated by a second provider, point to a cloud VPS, and send email through a third-party service. The transfer can be straightforward when those dependencies remain unchanged. Problems usually arise when the transfer is combined with a nameserver change, a website migration, or an email provider change without a complete record inventory.
Use this workflow when consolidating domains, reviewing renewal costs, changing ownership or billing, moving to a domain-and-hosting provider, or replacing a registrar. For a broader inventory of domains and dependencies, see the domain portfolio management checklist.
The safest default is to transfer the registration first while keeping the current DNS hosting and web infrastructure unchanged. Once the transfer is complete and verified, plan any DNS or hosting changes as a separate project.
How to estimate
Estimate the transfer using four separate measures: direct cost, preparation time, registrar processing time, and operational risk. Keeping these measures separate produces a more useful plan than treating every domain transfer as the same task.
1. Estimate the direct cost
Record the receiving registrar’s transfer charge, any included registration extension or renewal term, applicable taxes, and optional services such as privacy, DNS hosting, monitoring, or security features. Also record the losing registrar’s renewal price, because a lower transfer price may not represent the long-term cost.
Use this simple comparison:
First-cycle transfer cost = transfer charge + taxes + optional services
Expected annual cost = renewal price + recurring optional services
Do not assume that every domain extension follows the same pricing or transfer process. Check the receiving registrar’s current terms for the exact extension, currency, renewal treatment, and any restrictions before you authorize the move.
2. Estimate preparation time
Preparation time depends less on the domain itself than on the number of services attached to it. A simple domain with documented DNS may take only a short review. A business domain supporting several websites, transactional email, verification records, APIs, and subdomains needs a more careful inventory.
Count the following before scheduling the transfer:
- Websites, applications, redirects, and staging environments
- Mailboxes, forwarding addresses, and email security records
- DNS providers, nameservers, and DNS administrators
- Subdomains used by apps, APIs, dashboards, status pages, or vendors
- SSL certificate issuance, renewal, and validation dependencies
- Third-party services that verify ownership through DNS
3. Estimate processing and propagation time
A registrar transfer and DNS propagation are different events. The transfer may be accepted and completed while the website and email continue using the same DNS records. DNS changes become relevant if you change nameservers or edit records during the move.
Allow time for account verification, obtaining the EPP or Auth-Code, removing a registrar lock where required, completing approval steps, and checking the transfer status. Exact requirements and timelines vary by registrar, domain extension, account security settings, and the reason for the transfer. Treat the receiving registrar’s current instructions as authoritative rather than relying on an old checklist.
Inputs and assumptions
Complete this pre-transfer inventory before requesting the move. Store it in a secure location and avoid placing passwords or private keys in a general-purpose spreadsheet.
| Input | What to record | Why it matters |
|---|---|---|
| Domain and extension | Exact domain, extension, renewal date, and current registrar | Transfer rules and costs can differ by extension. |
| Registrant account | Account owner, administrative contact, and access status | You may need account access or approval before moving. |
| Registrar lock | Whether the domain is locked and how to unlock it | A locked domain may not be eligible to transfer until the lock is removed. |
| Auth code | Where to request the EPP, Auth-Code, or transfer code | The receiving registrar generally needs a valid code to start the request. |
| WHOIS or registration privacy | Whether privacy is enabled and whether contact details are current | Contact visibility and approval workflows can vary. |
| Nameservers | Current authoritative nameservers and DNS provider | This identifies where the live DNS zone is managed. |
| DNS records | A, AAAA, CNAME, MX, TXT, and other active records | You need a recoverable record set if DNS changes are required. |
| Services | Website, email, SSL, APIs, verification tools, and redirects | These dependencies determine the transfer’s operational risk. |
Export or copy the current DNS zone from the DNS provider, not merely from the registrar account. If the registrar is not hosting DNS, transferring the registration should not move the zone automatically. Confirm this distinction with both providers before proceeding. The DNS records cheat sheet and zone-file template can help you document the records.
Pay particular attention to email. Record MX, SPF, DKIM, and DMARC entries, along with any vendor-specific TXT records. Do not delete or recreate these records during a registrar transfer unless you have a separate reason to change DNS. Use the email DNS setup guide when validating mail dependencies.
Before starting, verify that the domain is not close to expiration, subject to an unresolved ownership issue, or involved in an active change that could complicate account access. Policies differ by registrar and extension, so check the current transfer eligibility requirements. If a transfer is declined, read the stated reason and correct that condition rather than repeatedly submitting the same request.
Worked examples
Example 1: Marketing website with external DNS
A company uses Registrar A for registration, a separate managed DNS provider for nameservers, and cloud hosting for its website. Email is handled by a third-party provider. The transfer plan is low risk if the company keeps the same nameservers and does not edit the DNS zone.
The cost estimate includes the receiving registrar’s transfer charge, taxes, and any recurring privacy or DNS options. The preparation checklist includes the renewal date, account access, registrar lock, Auth-Code, nameservers, and a DNS export. After the transfer, the team checks the website, HTTPS, redirects, and email delivery. Because DNS hosting did not change, a nameserver migration is not part of this estimate.
Example 2: Domain and DNS are managed together
A developer uses one provider for registration and DNS, with an application hosted on a VPS. The intended receiving registrar offers DNS management, but the team has not decided whether to use it. The safest approach is to export the existing zone, compare the receiving provider’s records, and choose one controlled cutover plan.
If the nameservers remain with the original DNS provider, the registration transfer can be evaluated separately from DNS migration. If nameservers will change, add DNS-zone recreation, record validation, TTL planning, and propagation monitoring to the schedule. The domain transfer without downtime guide provides a focused operational sequence.
Example 3: Portfolio consolidation
An organization is moving several domains to one registrar. Estimate each domain independently, then group them by risk: inactive domains, domains with websites only, domains with email, and domains supporting production applications. Start with a low-risk domain to validate the new registrar’s workflow. Apply the same inventory and verification process to the remaining domains, while keeping a separate record of renewal dates and ownership contacts.
When to recalculate
Recalculate the transfer plan whenever an input changes. The most important triggers are a new renewal quote, a change in registrar or DNS pricing, a different transfer requirement for the extension, an approaching expiration date, a new website or email provider, a nameserver change, or a change in domain ownership.
Recheck the plan before each renewal cycle if cost is the reason for moving. Compare the full expected annual cost rather than only the introductory transfer charge. Recheck it before a launch or infrastructure migration if the domain is used by a production application, because a registrar move should not be allowed to obscure a separate deployment risk. For server-related changes, keep the domain transfer separate from the application cutover and follow a documented production checklist.
On transfer day, use this final action list:
- Confirm account access, billing details, and the correct domain.
- Verify the current DNS provider and save a fresh DNS record inventory.
- Check the domain’s lock status and request the current EPP or Auth-Code.
- Review privacy and registrant contact details according to the registrar’s instructions.
- Submit the transfer at the receiving registrar and complete required approval steps.
- Monitor transfer status without changing DNS unnecessarily.
- After completion, test the website, HTTPS, redirects, email sending and receiving, important subdomains, and ownership-verification services.
- Store the new renewal date, registrar account owner, DNS provider, and recovery contacts in your domain inventory.
If something fails, use the saved DNS zone and the original provider’s service records to restore the last known configuration. A registrar transfer is not the same as a website migration, so avoid changing multiple infrastructure layers at once. For future reviews, combine this checklist with the domain renewal and expiration guide and your organization’s website launch checklist.