A safe domain transfer starts with ownership and DNS documentation. Unlock the domain only when ready, protect the authorization code and keep registrant email accessible.
What should you evaluate?
Start by defining confirmed requirements, then compare resources, management and growth path. Do not choose by product label alone; focus on workload fit, operational responsibility, migration and recovery.
Eligibility
Some TLDs have transfer locks after registration or ownership changes.
Authorization
EPP or authorization codes should be treated like credentials.
DNS continuity
A registrar transfer is separate from changing nameservers or hosting.
Registrant email
Approval requests often rely on the registered contact address.
A practical decision process
- Define the current workload and expected growth.
- Review resource limits and published capabilities.
- Define management and security responsibilities.
- Plan backup and migration before change.
- Confirm final price and terms in checkout.
Test important changes before production and keep a clear rollback path whenever the service is business-critical.
Specifications, prices and terms can change. The cart, customer portal and applicable service terms are the final reference.
Frequently asked questions
Will my site go offline during transfer?
It should not if DNS remains correct, but poor planning can cause disruption.
Does transfer move email?
No. Email and DNS need separate planning.
Can transfer fail?
Yes, for example because of lock status, wrong authorization or missing approval.