A transfer is not a hosting move
Changing registrars does not require changing hosting or email. Downtime usually comes from changing nameservers or losing DNS records.
A process totransfer without losing services
| Step | Action | Tip |
|---|---|---|
| 1 | ActionBack up the DNS zone | TipSave A, AAAA, CNAME, MX, TXT, CAA, TTL and nameservers |
| 2 | ActionConfirm eligibility | TipCheck locks, registrant details and approval email |
| 3 | ActionObtain Auth/EPP | TipUnlock only during the planned transfer window |
| 4 | ActionTransfer without changing DNS | TipKeep nameservers and move hosting separately |
| 5 | ActionRelock and test | TipVerify web, mail, TLS, subdomains, 2FA and renewal |
Prepare and transfer
Export the DNS zone, verify ownership email, unlock the domain and use the authorization code with the new registrar.
Verify afterward
Restore transfer lock and test the website, email, SSL and subdomains before closing the previous account.
Verified sources
Go deeper
These two resources expand on the key points with criteria, data and guidance from the organizations responsible for them.
It brings together the official process, FAQs and requirements registrars must follow when moving a domain between providers.
It defines locks, AuthInfo codes, authorization and denial grounds, making it the policy reference for a safe transfer.



