Understanding the Domain Transfer Process: Step by Step

Transferring a domain between registrars is a routine operation that every domain investor performs regularly, yet the process has specific technical requirements and timing constraints that catch people off guard. A transfer done wrong can leave your domain in limbo for days or fail entirely. Here is exactly how the process works for .com and most other gTLDs.

Prerequisites for Transfer

Before initiating a transfer, verify these conditions at the current (losing) registrar:

Domain is unlocked. Most registrars lock domains by default to prevent unauthorized transfers. Log into the current registrar, find the domain management page, and disable the transfer lock. The status code should change from clientTransferProhibited to OK or active.

60-day lock has passed. ICANN requires a 60-day lock on newly registered domains and on domains that have recently undergone a registrant contact change. If you registered the domain or changed the WHOIS contact within the last 60 days, you cannot transfer it yet.

Domain is not expired. Expired domains cannot be transferred until they are renewed at the current registrar. Some registrars allow renewal during the grace period; others require redemption fees.

You have the authorization code (EPP code / auth code). The losing registrar provides this code, which the gaining registrar requires to initiate the transfer. Generate the auth code through your registrar dashboard — it is typically a random string of letters, numbers, and symbols.

The Transfer Process

Obtain the auth code from the current registrar.
Initiate the transfer at the new (gaining) registrar. Enter the domain name and the auth code. Pay the transfer fee, which is typically equal to one year of registration (this extends your registration by one year — so a transfer is not an added cost but a prepaid renewal).
Confirm the transfer request. The gaining registrar sends a verification email to the domain registrant email address. Click the confirmation link. Some registrars also require the losing registrar to send a confirmation to the registrant.
Wait for the transfer to process. ICANN mandates a 5-day window during which the losing registrar can cancel the transfer if the registrant objects. Most registrars allow the registrant to approve the transfer early, shortening this to 1-2 days.
Verify completion. Check WHOIS to confirm the domain now shows the new registrar. Verify that DNS records transferred correctly (some transfers reset DNS to defaults).

Transfer Timing

The standard timeline is 5-7 days from initiation to completion. This breaks down as:

Day 0: Transfer initiated at gaining registrar
Day 0-1: Verification emails sent and confirmed
Day 1-5: Mandatory waiting period (can be shortened if losing registrar approves early)
Day 5-7: Transfer completes, domain appears at new registrar

During the transfer, the domain continues to resolve normally using its existing DNS records. There should be zero downtime for any website or email hosted on the domain.

Bulk Transfers

Transferring 10+ domains simultaneously requires planning:

CSV upload. Most registrars support bulk transfer via a CSV file containing domain names and authorization codes. Namecheap, GoDaddy, Dynadot, and Porkbun all offer this feature.

Auth code collection. The bottleneck in bulk transfers is collecting auth codes from the losing registrar. Some registrars generate all codes at once through the bulk management interface. Others require clicking through each domain individually. For 500+ domains, this can take hours if the losing registrar does not support bulk auth code export.

Staggered initiation. Some gaining registrars have daily limits on transfer initiations. Plan for 50-100 transfers per day if your target registrar imposes rate limits.

Cost. Each transfer costs one year of registration at the gaining registrar. Transferring 100 .com domains to Namecheap at $8.88 each costs $888 — but this extends each domain registration by one year, so it is effectively a prepaid renewal at the new registrar rate.

Transfer Issues and Troubleshooting

Transfer fails — domain is locked. The most common failure reason. Return to the losing registrar, verify the domain is unlocked, and re-initiate.

Auth code rejected. Auth codes are case-sensitive and expire after a set period (varies by registrar). Generate a fresh code and try again.

Transfer stuck in pending. If the transfer sits in “pending” status for more than 7 days, contact the gaining registrar support. The losing registrar may not have processed the release.

DNS records reset. Some gaining registrars reset DNS records to their defaults during transfer. If you have custom DNS (A records, CNAME records, MX records for email), back them up before the transfer and re-apply them at the new registrar immediately after the transfer completes.

Email interruption. If MX records reset during transfer, email delivery will fail until you reconfigure them. For critical email domains, update MX records at the new registrar immediately upon transfer completion.

Registrar-Specific Notes

GoDaddy outbound transfers: GoDaddy provides auth codes through the domain management page. They send a transfer confirmation email with an “approve” or “deny” option. Approving expedites the transfer.

Namecheap inbound transfers: Namecheap charges $8.88 per .com transfer (includes one year of renewal). The interface supports bulk transfers via CSV.

Cloudflare inbound transfers: Cloudflare charges at-cost (~$9.15 for .com). Requires DNS to be managed through Cloudflare before transfer. The transfer process is integrated with their DNS management flow.

Porkbun: Charges $9.73 per .com transfer. Clean interface for both individual and bulk transfers. Free WHOIS privacy included post-transfer.

For security considerations during transfers, see domain registrar security guide and domain locking strategies. For the technical details of DNS during transfers, read domain cname and a records explained.