Transferring a domain does not have to interrupt a live website. This guide explains how to prepare DNS, check transfer eligibility, estimate the time and cost involved, move the domain between registrars, and verify that websites, email, and security records continue working afterward.
Overview
A domain transfer moves the registration record from one registrar to another. It is separate from moving website files, databases, email mailboxes, or hosting accounts. In many cases, the website can remain on its existing hosting while the registrar changes.
The main risk is not the transfer itself but changing or overlooking DNS settings. DNS tells browsers and mail systems where to find your website and email. If the new registrar replaces the existing DNS zone with an empty or incomplete zone, visitors may see an error and email delivery can fail. The safest approach is to preserve the current DNS configuration before starting and avoid changing nameservers during the transfer unless there is a specific reason to do so.
A typical domain migration has five stages:
- Record the current registration and DNS configuration.
- Confirm that the domain is eligible to transfer.
- Unlock the domain and obtain its authorization code.
- Submit the transfer at the new registrar and approve any confirmation messages.
- Verify DNS, website, email, renewal settings, and account security.
The best domain registrar for your situation is not necessarily the one with the lowest introductory price. Compare the renewal price, transfer fee, domain privacy options, DNS management, support, account security, and the registrar's handling of the extensions you use.
How to estimate the time, cost, and risk
Use a simple transfer worksheet before you begin. It creates a repeatable estimate without relying on a promotion or an assumed completion time.
Estimated project time = preparation time + registrar processing time + verification time.
Preparation may include exporting DNS records, checking the domain status, locating the authorization code, and reviewing email access. Registrar processing time varies by extension, registrar, approval method, and whether the transfer is manually approved or allowed to complete through the normal process. Verification usually takes a short, planned review of the website and email rather than a passive wait.
For cost, use this formula:
First-year transfer budget = transfer charge or included registration term + optional privacy or protection fees + any separate hosting or email costs.
Do not use the transfer price alone as your comparison. Record these figures for both registrars:
- Transfer price or renewal price attached to the transfer, if applicable.
- Standard renewal price for the next term.
- Price of privacy protection, premium DNS, email, or other optional services.
- Taxes, currency conversion, and payment processing differences where relevant.
- Cost of keeping related services at the old provider during a transition period.
To estimate downtime risk, first ask whether nameservers will change. If the existing nameservers remain active and the DNS zone is preserved, the transfer itself normally does not require a website outage. If nameservers, DNS records, hosting, or email are changing at the same time, treat that as a separate migration project and allow time for testing.
Inputs and assumptions
Gather the following information before requesting a transfer.
Domain eligibility
Check the domain's expiration date, transfer status, ownership details, and any registrar or registry restrictions. Some domains cannot be transferred shortly after registration, a previous transfer, or certain account or contact changes. Rules also differ by domain extension. The current registrar's help documentation is the safest place to confirm eligibility.
Make sure you can access the registrant or administrative email address associated with the domain. If that address is obsolete, update it before starting, but check whether the change creates a temporary transfer restriction.
Authorization and privacy
Most transfers require an authorization code, sometimes called an EPP code or transfer code. Request it from the current registrar and copy it exactly. A domain privacy service may hide public contact details without preventing a transfer, but its behavior varies. Confirm that the authorization code and transfer approval messages will reach you while privacy protection is enabled.
Unlock the domain only when you are ready to submit the transfer. Afterward, re-enable the registrar lock or equivalent protection at the new registrar if it is not restored automatically. Keep two-factor authentication enabled on both registrar accounts during the process.
DNS and service dependencies
Copy the complete DNS zone, including A, AAAA, CNAME, MX, TXT, and any verification or security records. Pay particular attention to:
- MX records used for business email hosting.
- SPF, DKIM, and DMARC records used for email authentication.
- Subdomains for applications, APIs, staging sites, and developer tools.
- Certificate validation, payment, analytics, and search-console records.
Confirm which service currently hosts DNS. The registrar may not be the DNS provider. If nameservers point to your web host, a CDN, or a separate DNS platform, document that relationship and do not replace those nameservers casually.
Worked examples
Example 1: Registrar-only transfer
A small business keeps its website and email at the same hosting provider but wants to move the domain to a different registrar. The nameservers will not change. The owner records the DNS zone, confirms the domain is eligible, unlocks it, obtains the code, and starts the transfer.
In this case, the estimated outage risk is low because the authoritative DNS service remains unchanged. The budget should include the new registrar's transfer or registration charge, the next renewal price, and any privacy fee. The owner should still verify the homepage, contact forms, login pages, and email sending and receiving after completion.
Example 2: Registrar and hosting transfer together
A developer is moving both the domain and website to a new provider. This is not one change but two: a registrar transfer and a hosting migration. The developer first copies the site, tests it on the new host, lowers DNS record time-to-live values where appropriate, and confirms the new server works. The registrar transfer can then proceed independently while the old hosting remains available as a fallback.
The estimate should include separate preparation and testing time for the hosting move. The transfer budget should not be presented as the full migration cost because hosting, backups, email, and possible development work are separate inputs. See the WordPress website launch checklist for a broader review of domain, hosting, DNS, and SSL dependencies.
Example 3: Transfer near renewal
A domain is approaching renewal while the owner is comparing registrars. The owner records the exact expiration date, checks how a transfer affects the registration term for that extension, and confirms the new registrar's price before proceeding. If the transfer could take longer than expected or eligibility is uncertain, renewing at the current registrar may be the safer way to prevent expiration. The owner can then transfer after confirming the domain is eligible.
When to recalculate
Revisit your estimate whenever one of the underlying inputs changes. Check again before starting if:
- The domain is within a short period of expiration.
- The registrant, administrative contact, or account details have changed.
- The domain was recently registered or transferred.
- You are changing nameservers, hosting, email, or CDN services at the same time.
- The registrar changes its transfer, renewal, privacy, or redemption pricing.
- The domain extension has special eligibility or authorization requirements.
After the transfer completes, confirm that the registrar account lists the correct expiration date, auto-renewal setting, contact information, privacy status, and nameservers. Test the root domain and important subdomains from more than one network. Send and receive test emails, check certificate warnings, and review monitoring alerts. A DNS propagation checker can help compare answers from different resolvers, but it should supplement—not replace—real browser and email tests.
Keep a final migration record containing the transfer date, registrar, renewal date, nameservers, DNS provider, and recovery contacts. This domain migration checklist makes the next renewal or transfer easier and reduces dependence on one person's memory. For related infrastructure decisions, compare your hosting options in the small-business hosting guide and review your control-panel requirements before moving hosting as well.
