How to Transfer a Domain to a New Registrar: A Step-by-Step Walkthrough

Transferring a domain isn't complicated, but it is unforgiving of sloppy sequencing. Miss a step and you can stall a transfer for a week, break email during a live campaign, or trigger a rejection that sends you back to square one. For operators managing acquisitions—or investors consolidating a portfolio onto one registrar—the process is a repeatable checklist, not a mystery.

This walkthrough covers exactly how to transfer a domain to a new registrar: what to prepare, the order of operations, realistic timelines, and the failure points worth guarding against. If you run domains as strategic assets, treat the transfer as an operational discipline you can execute the same way every time.

Before you start: what a transfer actually is

A registrar transfer moves the management of a domain from one ICANN-accredited registrar to another. Ownership doesn't change—you still control the asset—but billing, DNS management, renewal, and administrative control shift to the new provider. This is different from changing ownership (a registrant transfer or push) and different from simply pointing your nameservers elsewhere.

Most operators transfer for a reason: consolidating a portfolio for cleaner management, escaping a registrar with poor support or opaque pricing, or bringing a freshly acquired domain onto their preferred stack. Whatever the driver, the mechanics are standardized across gTLDs like .com, .net, and .org under ICANN policy.

The two conditions that block most transfers

Before you touch anything, confirm the domain is eligible. Two rules trip people up more than any other:

• The 60-day lock. Domains recently registered or transferred are locked for 60 days. If you just acquired the name, this is often the constraint that governs your timeline. We break down the mechanics in why domains are locked for 60 days after purchase—read it before you plan a transfer window.
• Registrar lock (transfer lock). A separate protective setting that you can usually toggle off yourself in the current registrar's dashboard. This one you control directly.

Step 1: Prepare the domain at the losing registrar

Your current registrar—the "losing" registrar in ICANN's terminology—is where all the prep happens. Log in and work through the following:

1. Verify contact details. The administrative email on file must be one you can access, because approval messages often route there. Update it before you begin if it's stale.
2. Unlock the domain. Find the registrar lock setting and disable it. Some registrars label this "transfer lock" or "domain lock."
3. Disable WHOIS privacy (if required). Certain registrars block transfers when privacy protection is active, or the redacted contact email prevents approval emails from reaching you. Turn it off temporarily; you can re-enable it after the move.
4. Confirm the domain isn't in a redemption or expired state. Transfers require an active, in-good-standing domain.

Get your authorization code

Next, request the authorization code—also called the EPP code, auth code, or transfer key. This is the single string that proves you have the right to move the domain. Without it, the gaining registrar can't initiate anything. Some registrars display it instantly; others email it or impose a short delay. We cover the retrieval process and common snags in Authorization Codes Explained.

Treat the auth code like a password. It grants transfer authority, so don't leave it sitting in an unsecured shared inbox.

Step 2: Protect continuity before the switch

This is the step most guides skip—and the one that separates a clean transfer from a costly one. A registrar transfer can reset or interrupt DNS and email if you don't plan for it.

Document your current DNS records before you initiate: A records, CNAMEs, MX records for email, TXT records for SPF/DKIM/verification. If your DNS is managed at the registrar you're leaving, those records may not carry over. Recreate them at the new registrar (or wherever your DNS will live) before the transfer completes, so resolution never gaps.

For any domain running production traffic or live email, follow the sequencing in how to transfer a domain without downtime or losing email. The core principle: your DNS and mail should already resolve correctly at the destination before control changes hands.

Step 3: Initiate the transfer at the new registrar

Now move to the gaining registrar—the new home for the domain. The flow is consistent across providers:

1. Start a new transfer order and enter the domain name.
2. Paste in the authorization code you retrieved.
3. Pay the transfer fee. For most gTLDs this includes a one-year renewal, so you're not just paying to move—you're extending the registration by a year. Understand the full cost picture in domain transfer costs and renewal fees.
4. Confirm the admin contact details and submit.

Once submitted, the gaining registrar sends a confirmation request, and the process moves into approval.

Step 4: Approve and wait

Two approvals can be in play. The gaining registrar usually emails the administrative contact asking you to confirm the transfer—click that link promptly, because an unconfirmed request can expire. The losing registrar may also send its own approval email; explicitly approving there can accelerate the process considerably.

If no one acts, ICANN policy auto-completes most transfers after roughly five days. But you rarely need to wait that long. If both registrars support instant or explicit approval, a transfer can finish within hours. Plan for up to five days to be safe, and schedule around it—don't initiate the Friday before a launch.

What to do if it stalls

Transfers get rejected or stuck for predictable reasons: an expired auth code, a domain still inside the 60-day window, mismatched contact emails, or an unremoved lock. If yours hangs or bounces back, work through the transfer troubleshooting checklist rather than re-initiating blindly—repeated attempts rarely fix the underlying cause.

Step 5: Verify and re-secure after transfer

Once the transfer confirms, don't consider it done. Close the loop:

• Confirm the domain now appears in your new registrar's dashboard.
• Verify DNS is resolving and email is flowing—check your MX records actively, don't assume.
• Re-enable WHOIS privacy if you disabled it.
• Re-lock the domain to prevent unauthorized future transfers.
• Set auto-renew and confirm the new expiration date reflects the added year.

A note on timing: after any transfer, that fresh 60-day lock applies again. If you're staging further moves—say, consolidating several acquisitions—sequence them so no single domain gets stranded.

Where the transfer fits in your broader strategy

Consolidating domains onto one registrar isn't just administrative hygiene. It tightens portfolio oversight, simplifies renewals, and reduces the risk of a lapsed name slipping through the cracks—the kind of unforced error that can cost you an asset you paid a premium to acquire. If you're still weighing which names are worth that premium in the first place, our take on premium domains vs cheap domains frames the underlying calculus, and our guide to choosing a domain name covers what to prioritize before you buy.

Executed with a checklist, a registrar transfer is a 20-minute task plus a waiting period—not a source of anxiety. Prepare the losing registrar, protect DNS and email, initiate with a valid auth code, approve promptly, and re-secure on arrival. Run it the same way every time and it becomes routine.

Building or consolidating a portfolio and want names that are worth transferring in the first place? Browse the PixelWorks Domains inventory to see what's available, or reach out about a specific acquisition—we'll talk through the asset and the logistics of getting it onto your stack cleanly.