Migration runbook

How to transfer a domain name safely

Move a domain between registrars without changing its website or email service, and know which locks can delay the transfer.

Format
Migrate · Intermediate
Published
Published
Updated
Updated
Reading time
3 min read
Guide Domains Migrate Intermediate domains

Key takeaways

  • A registrar transfer does not need to change nameservers or interrupt service.
  • Check eligibility, renewal state, access to the registrant email, and DNS hosting before starting.

Before you begin

  • Administrative access to the current and receiving registrar accounts
  • A current record of nameservers and critical DNS records

Transferring a domain sounds riskier than it is. A registrar transfer only changes which company manages the registration — your website, email, and DNS hosting don’t have to move at all. Keeping those layers separate, in your head and in your plan, is what makes a transfer boring in the best possible way.

Confirm that the domain can transfer

Check the domain’s status and expiration date. A generic top-level domain may be ineligible within 60 days of initial registration, a recent transfer, or certain registrant-contact changes. A registrar or registry lock, dispute, court order, or unpaid prior registration period can also block a transfer.

Read the current registrar’s process and the receiving registrar’s requirements. Country-code domains may follow registry-specific rules.

Record the working configuration

Export or capture the complete DNS zone, current nameservers, registration contacts, renewal date, and domain status codes. Confirm who hosts DNS. If the current registrar also hosts DNS, ask whether that DNS service continues after transfer; if not, move DNS to a stable provider before transferring the registration.

Resist the urge to bundle a registrar transfer, nameserver change, web-host move, and email migration into one big weekend. When something breaks halfway through, you want to know which change broke it.

Prepare account access

Verify that the registrant or administrative contact email can receive messages. Secure both registrar accounts with multi-factor authentication. Confirm the receiving account is owned by the correct organization.

Unlock the domain only when ready to begin. Obtain the transfer authorization code—often called an auth code or EPP code—and keep it confidential.

Start and approve the transfer

Initiate the transfer at the receiving registrar, enter the authorization code, and review the renewal term and registrant details. Approve confirmation messages from the gaining and losing registrars when required.

Transfers can take several days. Leave nameservers unchanged and monitor the website, email, and DNS during that period. The ICANN transfer policy defines the standard framework for generic top-level domains.

Verify completion and re-secure the domain

After the transfer completes:

  1. Confirm the domain appears in the receiving account.
  2. Compare its nameservers with the pre-transfer record.
  3. Test the website, mail delivery, and critical DNS records.
  4. Verify the new expiration date and automatic-renewal settings.
  5. Re-enable transfer lock and review recovery contacts.

Keep the old registrar account until billing and any remaining services are resolved. Do not delete DNS zones or hosting services merely because the registration moved.

Rollback and escalation

If a transfer is unauthorized, contact both registrars immediately and preserve confirmation messages and account logs. If a registrar will not provide a reasonable way to unlock an eligible domain, use ICANN’s transfer complaint process.

Sources and further reading

Was this guide helpful?