Keep registration, DNS, hosting and email changes separate where supported; establish continuity and recovery before authorizing a registrar transfer.
A registrar transfer moves the domain registration. It does not automatically move website files, mailbox history or every DNS dependency. To protect the working services, identify where each lives, confirm transfer eligibility, and preserve the current DNS arrangement where both providers support it.
This guide primarily concerns generic domains such as .com. Country-code domains can have different rules. It is a planning checklist based on official documentation, not a transfer we performed or a promise of uninterrupted service.
Know which change you mean
| Change | What moves | What still needs a separate plan |
|---|---|---|
| Registrar transfer | The company managing registration and renewal | DNS continuity, website and mailbox services |
| Nameserver change | The authoritative DNS provider | The complete replacement zone and DNSSEC coordination |
| Website migration | Website application, files and database | Email history, domain registration and external jobs |
| Change of registrant | The registration contact or holder details | Authorization and any resulting transfer restriction |
The distinction matters when a provider offers to “move everything.” Ask which rows are included. A discounted registration transfer is a different product from a managed website or email migration.
1. Confirm control and eligibility
Use an owner-controlled registrar account and confirm its recovery route works. Identify the current registrar through the account or official registration lookup. Read who should control the domain account if an agency or former colleague is the only person with access.
ICANN’s registrant FAQ describes restrictions that can follow a recent registration, previous transfer or change of registrant. Some are subject to specific policy and registrar conditions. Do not assume every lock can be removed with the same switch or that updating contact details immediately before transfer is harmless.
Check the current effective Transfer Policy and the actual domain’s status with both registrars when eligibility is unclear. Ask for the specific reason and next allowed action rather than trying repeated orders.
2. Build a continuity inventory
Record the current nameservers, complete active DNS zone, website host, mailbox service, renewal date and account owner. Include MX destinations and their address dependencies, authentication and verification records, subdomains and DNSSEC status. Store this information privately; an authorization code belongs in a secure transfer workflow, not a shared planning document.
Ask the old provider whether its DNS and bundled email remain available after registration leaves. Keeping the same nameservers helps only if that service remains active and your new registrar permits the arrangement. Do not cancel a hosting bundle because the registrar transfer has completed.
Namecheap’s DNS instructions explain that existing records are not automatically carried into every replacement DNS arrangement. An automatic scan is a starting point to compare with your inventory, not proof that every subdomain and mail dependency was found.
3. Check the destination’s DNS conditions
Some registrars allow your existing DNS provider; others require their own. Cloudflare’s transfer process, for example, requires the domain to be active on Cloudflare before the registration transfer. That means DNS preparation is part of its route, rather than an optional assumption.
If nameservers must change, create and review the replacement zone first. Coordinate DNSSEC using the exact current providers’ instructions. Stale DS data can cause validation failures when DNS authority changes. Do not treat disabling DNSSEC as a universal requirement for every registrar-only transfer or leave the final security state undocumented.
Use the website and email DNS checklist to verify that delegation work does not silently remove a functioning mailbox configuration.
4. Authorize through the genuine registrar workflow
When ready, use the current registrar’s documented unlock and authorization-code process and initiate the transfer with the intended new registrar. Check the destination and account carefully. Respond to legitimate confirmation requests through the verified provider interface; do not hand codes to someone who contacts you unexpectedly.
Record the quoted transfer charge, currency, eligibility and the effect on the registration term. Domain extensions, premium names and renewal timing can differ. A low transfer price does not establish the next renewal bill, and a generic registration comparison is not a quote for this transaction.
5. Monitor the services and finish the handover
- Confirm transfer status in the genuine accounts, not only a promotional confirmation page.
- Recheck the authoritative nameservers and intended DNS configuration.
- Open the website at the final domain and verify HTTPS.
- Test incoming and outgoing email, important aliases and website-form delivery separately.
- Confirm the destination account’s recovery, renewal responsibility and final DNSSEC state.
Keep the previous services until their replacement and continuity are verified. Cached DNS can make different checks disagree during a change; one successful browser view is insufficient evidence that every dependency works.
If the domain is expired or the transfer is refused
Check the EPP status and ask the registrar for the exact restriction. Redemption and pending deletion are different from an ordinary transfer lock. A transfer is not a reliable emergency shortcut for restoring an expired domain; use the expiration recovery guide before cancelling or buying substitutes.
For a planned future move, compare registration, renewal, DNS choice and account control. Choose the service that fits those requirements rather than creating avoidable operational work for a small introductory saving.
Sources and verification
Editorial review 2026-10-08. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- ICANN: domain transfer FAQs for registrantsChecked Registrar transfers require authorization and may be blocked by applicable registration, transfer or registrant-change locks; expired-domain conditions differ.
Limits: Generic top-level-domain scope; country-code domains and provider procedures can differ. - ICANN: Transfer PolicyChecked Policy distinguishes inter-registrar transfers and changes of registrant and sets permitted denial conditions.
Limits: Check the effective current version and actual domain status; not legal advice or an individual eligibility determination. - ICANN: EPP domain status codesChecked Status codes distinguish transfer restrictions and lifecycle states including redemption.
Limits: Status interpretation does not guarantee a successful transfer or recovery. - Namecheap: changing DNSChecked Delegation changes can require records to be recreated manually in the replacement zone.
Limits: Namecheap-specific DNS arrangements; not proof all registrars retain DNS after a transfer. - Cloudflare: transfer a domain to CloudflareChecked Cloudflare requires an active Cloudflare DNS zone before registration transfer and gives provider-specific DNSSEC preparation.
Limits: Cloudflare-specific prerequisite; must not be generalized to every registrar or every DNSSEC migration.