Moving a domain to a new registrar does not require moving your website or email at the same time. This domain transfer checklist shows how to estimate the cost, protect DNS services, avoid an interruption, test the change, and keep a rollback plan ready.
Overview
A registrar manages the domain registration record. DNS may be managed there, at your web host, through a dedicated DNS provider, or across several services. Your website may run on shared hosting, WordPress hosting, a VPS, or cloud hosting somewhere else. Email can be separate again. Keeping those roles distinct is the key to transferring a domain without downtime.
A registrar transfer changes the company responsible for the registration. It does not automatically change the domain’s nameservers, website files, mailboxes, SSL certificate, or hosting account. Problems usually occur when someone changes nameservers unnecessarily, lets a domain expire during the transfer, fails to copy DNS records, or overlooks the account used for domain ownership verification.
Use this workflow before a renewal-price review, registrar consolidation, acquisition, rebrand, or hosting migration. Record the current configuration first, estimate the total cost, then transfer the registration while leaving working DNS in place.
Quick domain transfer checklist
- Confirm the domain owner, registrant contact, and administrative email address.
- Record nameservers, DNS records, TTL values, website IP addresses, mail records, and third-party verification records.
- Check the domain expiration date and any transfer restrictions shown by the current registrar or registry.
- Disable the registrar lock only when you are ready to start the transfer.
- Request the domain authorization code, sometimes called an EPP or transfer code.
- Confirm the new registrar’s transfer price, renewal price, privacy options, and supported payment method.
- Submit the transfer and approve any confirmation message sent to the authorized contact.
- Verify nameservers, DNS, website, email, SSL, redirects, and renewal settings after completion.
How to estimate
Estimate a domain migration in three parts: direct registration cost, operational overlap, and risk-adjusted effort. A simple planning formula is:
Estimated total = transfer charge + required renewal or added registration term + optional services + temporary overlap costs.
Do not treat the advertised transfer amount as the complete cost until you confirm what it includes. Depending on the domain extension and registrar, a transfer may be priced separately from renewal, may include an additional registration period, or may have a different process and fee. Premium domains, recently changed registration details, expired domains, and special extensions can follow different rules. Check the receiving registrar and applicable registry before paying.
Temporary overlap is often the safest operating choice. You might keep the old hosting account active until the new DNS and website have been tested, retain an existing email service while verifying MX records, or pay for a separate DNS service that is not tied to either registrar. Include those costs if they apply.
For an internal decision, calculate two totals:
- Minimum transfer cost: the registrar transfer or renewal charge plus any mandatory taxes or service fees shown at checkout.
- Safe migration cost: the minimum cost plus DNS, email, hosting, backup, monitoring, or overlap expenses needed to reduce operational risk.
This distinction prevents a low registrar price from hiding the cost of replacing bundled email, privacy, DNS management, or backup features.
Inputs and assumptions
Build a small inventory before beginning the domain registrar migration. Save it in a location that remains accessible if the old registrar account is closed.
Registration inputs
- Domain name and extension.
- Current expiration date, renewal status, and auto-renewal setting.
- Current registrar, account owner, registrant contact, and administrative email.
- Registrar lock status and the location of the authorization code.
- Transfer price, renewal price, privacy cost, taxes, and any premium or manual-processing charges.
- Whether the domain is subject to a registry-specific transfer rule or a recent ownership-change restriction.
DNS and service inputs
- Nameservers and the provider responsible for DNS hosting.
- A complete DNS export or manually documented records, including A, AAAA, CNAME, MX, TXT, and any CAA records in use.
- Current TTL values, website hosting IP addresses, CDN settings, redirects, and verification records.
- Email provider, MX priority, SPF, DKIM, DMARC, and mailbox access details. See the email hosting DNS and deliverability checklist for a deeper review.
- SSL certificate ownership, renewal method, and any dependency on the hosting control panel.
Assume the website and email will continue using their existing DNS during the registrar transfer. Changing nameservers is a separate migration and should be scheduled only when required. Lowering DNS TTL in advance can help with a planned DNS change, but it does not make a registrar transfer itself necessary or automatically faster. Confirm how long the current DNS provider honors TTL changes.
Before submitting the transfer, create a current backup and document a working restore path. A registrar transfer is not a substitute for a website backup or disaster recovery plan; use the backup and disaster recovery template to record recovery objectives and test evidence.
Worked examples
Example 1: Registrar-only transfer
A business domain uses a separate DNS provider, a managed email service, and an existing WordPress host. The team confirms that the nameservers will remain unchanged. Its estimate includes the receiving registrar’s transfer charge, any registration term added at checkout, and no hosting or email overlap because those services are unaffected.
The operational plan is to export DNS, verify the authorization code, unlock the domain, submit the transfer, approve the request, and compare nameservers before and after completion. The website and email are tested from multiple networks. In this case, the registrar changes while the service providers remain the same.
Example 2: Registrar and DNS consolidation
A developer wants to move a domain and place DNS under the new registrar. The cost estimate includes the domain transfer, possible privacy or DNS feature differences, and a short overlap period with the old DNS provider. The technical plan is more involved because records must be copied and validated before nameservers change.
First, the developer lowers TTL according to the existing provider’s documented behavior, copies every required record, and validates the new zone. After changing nameservers, the old DNS service remains available during the propagation window. If the website or email fails, the rollback is to restore the previously working nameservers, not to alter random records at the new registrar. Once the new zone is confirmed from several resolvers, the old DNS service can be retired.
Example 3: Transfer near expiration
A domain is close to expiration and the organization has not confirmed whether the transfer will complete in time. The safe estimate includes a possible renewal at the current registrar, the transfer cost, and the risk of paying for overlapping registration periods. The team should verify timing with both registrars and the relevant registry rather than assuming a transfer will complete before expiration.
If the expiration date is too close, renew first where appropriate, then transfer after confirming the domain’s status. Avoid disabling auto-renewal until you know which account will control renewal and have tested access to it.
Post-transfer test and rollback
- Confirm the domain appears in the new registrar account and the expiration information is recorded.
- Verify registrar lock and auto-renewal settings.
- Compare nameservers with the pre-transfer inventory.
- Open the website, test redirects, submit a form, and check the SSL certificate.
- Send and receive test email, then inspect SPF, DKIM, and DMARC behavior where applicable.
- Check monitoring, CDN, API callbacks, payment notifications, and other DNS-dependent integrations.
If a nameserver change was incorrect, restore the last known-good nameservers and keep the old DNS zone intact until service returns. Then identify the missing or incorrect record, correct the new zone, and schedule the nameserver change again. Do not delete the old DNS configuration until the new configuration has passed a complete test.
When to recalculate
Recalculate the transfer cost and review the checklist whenever an input changes. At minimum, revisit it before each domain move, renewal cycle, registrar consolidation, hosting migration, acquisition, or brand change.
Update the estimate when the registrar changes transfer or renewal pricing, privacy behavior, included services, authorization-code procedure, or account requirements. Also review it when the domain extension changes, when ownership or contact details are updated, or when the website, DNS, or email provider is being replaced at the same time. Registry and registrar rules can vary, so confirm current requirements instead of relying on an old checklist.
For a practical final review, complete these actions:
- Record the current expiration date and calculate the overlap budget.
- Export or document DNS and confirm who hosts the zone.
- Verify account access, ownership contacts, registrar lock, and authorization code.
- Price the transfer, renewal, privacy, email, DNS, and temporary hosting requirements.
- Schedule the change away from critical launches and preserve a rollback path.
- Run website, email, SSL, DNS, and monitoring tests after completion.
Keep the completed inventory with your website operations records. A repeatable domain transfer process reduces avoidable downtime and makes future registrar reviews, website migrations, and DNS changes easier to estimate and control.