A registrar transfer moves the administration of a domain registration between providers under the applicable rules. It is different from changing the registrant or moving a website’s hosting, although a sale can involve several of those tasks.
Start with control, eligibility and service continuity. Follow the receiving registrar’s current instructions rather than assuming every extension uses one universal workflow.
Identify the transfer and responsible accounts
Record exact domain, registrant, current registrar and receiving provider. Confirm that you have authority to request the move and access required approvals.
The current ICANN Transfer Policy describes relevant inter-registrar conditions and authority. Registry-specific processes can differ for other extensions.
An account push within the same registrar is not automatically the same operation as an inter-registrar transfer.
Check status and restrictions
Review relevant locks, proceedings and registration state through the current registrar. ICANN’s status-code guide explains applicable labels.
Ask which condition prevents a transfer when it cannot proceed. Do not assume that every lock should be disabled or that an old universal waiting-period statement remains applicable.
Contact-data changes can also affect the process. Review current conditions before changing details solely to prepare a move.
Preserve DNS and dependent services
Record nameservers and the configuration needed by the website and email services. Transferring registration does not automatically move hosting or mailboxes.
Our hosting guide separates those roles. Clarify whether a provider-specific arrangement needs additional work before changing it.
Plan a way to verify important services after completion, with account recovery available independently.
Prepare the receiving registrar’s request
Confirm extension support, fees, term effects and account requirements. Obtain any required authorisation code through the current provider’s genuine process and keep it private.
Remove an applicable transfer restriction only when the rules and authority permit it. Initiate the request through the receiving registrar’s supported route.
Our expired-domain transfer guide explains additional status and restoration questions when expiry is involved.
Complete required authorisation and notices
Follow the actual providers’ current approvals and verification steps. The current registrar may send notices concerning the request; that does not make it the service initiating your purchase of a receiving transfer.
Verify unexpected messages through the real account. A code request or payment screenshot from an unrelated sender is not adequate authority to change control.
Keep dates, confirmations and any denial explanation for support or the relevant complaint process.
Confirm completion and administration
Check the correct domain in the receiving account, current registrant details, resulting term and renewal settings. Verify DNS and dependent services against the saved records.
Secure access and retain the agreement and receipt. Our registration checklist covers those controls.
A successful transfer is a verified change under the relevant rules. Clear scope and records make it manageable without promising that every domain can move immediately or that a single generic sequence applies everywhere.