Domain Transfer Checklist: Move Registrars Without Disruption
Moving a domain name to another registrar can make billing, support, and portfolio management simpler. The transfer changes which company manages the registration; it does not, by itself, move your website files or email service. A little preparation helps prevent avoidable delays and protects the services that depend on the domain.
Confirm That the Domain Can Be Transferred
Check the domain’s extension and current status before paying for a transfer. Rules vary by top-level domain. For many generic top-level domains, restrictions can apply during the first 60 days after registration or a previous registrar transfer. A change of registrant may also trigger a 60-day lock under the applicable policy. Your current registrar can explain any lock shown in the account.
Do not leave the move until the registration is about to expire. Although expiry does not always prevent a transfer, it adds unnecessary uncertainty. Review the renewal date and any recovery status first. Our article on domain expiration explains why the timing matters.
Secure the Account and Authorization Code
Sign in directly to the current registrar, enable multi-factor authentication if available, and confirm that the account and registrant contact details are accurate. Make sure you can receive transfer-related messages. If a contact change would impose a transfer lock, ask the registrar about the consequences before editing the details.
Most generic-domain transfers require an authorization code, often called an AuthInfo or EPP code. Request it through the current registrar’s secure interface. Treat it like a credential: give it only to the intended gaining registrar and never post it in a public support ticket. Remove the transfer-prohibited lock only when you are ready to submit the request.
Keep DNS and Email Working
Record the existing nameservers and, if possible, export the DNS zone before starting. An inter-registrar transfer normally leaves the domain’s delegation in place, but the new registrar’s onboarding flow may offer to replace nameservers or use its default DNS service. Review that choice carefully.
If you also intend to change DNS hosting, treat that as a separate operation. Copy A, AAAA, MX, TXT, CNAME, and other required records before changing nameservers. Check email authentication records and DNSSEC settings as well. Our guide to DNS resolution shows how nameservers connect the domain to web and mail services.
Submit and Track the Request
Enter the domain and authorization code at the new registrar, review the price and registration-term details, and complete any requested confirmation. Watch for messages from both registrars. A pending transfer can require action, and a failed request usually includes a reason such as a lock, incorrect code, or ineligible domain status.
Avoid making unrelated ownership or DNS changes while the request is pending. Keep a record of the submission time and any confirmation emails. If the process stalls, ask the gaining registrar to identify the specific status rather than repeatedly restarting the transfer.
Verify the Result
Once complete, confirm that the new registrar appears in the domain record, the expiry date is what you expected, and automatic renewal and payment settings are correct. Recheck nameservers, DNSSEC, website access, and incoming email from outside your network. Save the authorization and billing records for future account management.
For the formal rules governing transfers between ICANN-accredited registrars, see the ICANN Transfer Policy. Country-code domains may follow different registry rules, so check their requirements separately.
