How to Transfer Domains in Bulk (2026)

Published October 19, 2026

Moving one domain takes 15 minutes plus a 5-day ICANN wait. Moving forty takes planning. Here’s the order of operations that avoids downtime, lost email, failed transfers, and the 3 AM realization that something didn’t carry over.

Phase 1: Inventory (before you touch anything)

Build a spreadsheet. Every domain gets a row with these columns:

• Domain name and TLD
• Expiry date — sort by this; domains expiring soonest move first
• Registrar lock status — you’ll unlock them in batches later
• Nameservers — what they’re currently set to
• What’s on it — live site, email, parked, redirect, nothing
• 60-day status — registered or transferred in the last 60 days? (ICANN rule: those can’t move yet)
• Special notes — premium renewals, registry locks, anything unusual

This spreadsheet becomes your migration control panel. Update it as each domain moves.

While inventorying, flag every domain with email on it. Email domains are the fragile ones — they move last, after you’ve practiced on simpler domains.

Phase 2: Prepare

Screenshot or export every DNS zone. For each domain with a live site or email: export the full DNS zone file from the old registrar. If anything fails to carry over during transfer, this is your restore point. It takes ten minutes and it’s the single most valuable insurance in this guide.

Verify access everywhere. Old registrar login, new registrar login, and the email account tied to both as the registrant contact. Transfer approval emails go to the registrant contact — if that inbox is dead, an old employee’s, or behind 2FA on a lost phone, fix it now, not mid-migration.

Check TLD-specific quirks. Most gTLDs (.com, .net, .org) follow the standard auth-code process, but some don’t:

• .uk domains don’t use auth codes — they use an IPS tag change, initiated at the gaining registrar. Different flow, same result.
• Some ccTLDs (.io, .ai, .co and others) have their own transfer rules, fees, or waiting periods. Check the gaining registrar’s help docs for each ccTLD you hold.
• Premium domains may have transfer restrictions — check before you start the batch.

Lower DNS TTLs. A day or two before you start, drop the TTL on important records to 300 seconds. If you need to fix DNS mid-migration, changes propagate in minutes instead of hours.

Phase 3: Move in batches

Work in batches of 5–10. Not one at a time (too slow), not all at once (one mistake multiplies across everything). After each batch lands, verify before starting the next.

Suggested batch order:

1. Batch 1: 2–3 parked or low-stakes domains. This is your shakedown run — learn the new registrar’s transfer flow where mistakes don’t matter.
2. Middle batches: standard domains with simple sites. Build rhythm.
3. Final batches: email domains and business-critical domains. By now the process is muscle memory.

Keep the old registrar account open until every domain shows in the new registrar. Don’t close anything mid-migration.

Phase 4: The per-domain checklist

For each domain, in order:

1. Unlock the domain at the old registrar (disable transfer lock / theft protection).
2. Disable WHOIS privacy temporarily if the transfer fails with it on — re-enable at the new registrar (free at Porkbun, Cloudflare, and Dynadot).
3. Copy the auth code (EPP code) from the old registrar’s panel.
4. Start the transfer at the new registrar with the domain name + auth code. The fee includes a one-year renewal — you’re prepaying next year’s registration, not paying a penalty to leave.
5. Approve the confirmation email from the old registrar. This skips most of the 5-day ICANN wait. No approval = auto-completes in 5 days.
6. Verify DNS carried over. Check the site loads; send and receive a test email. Compare against your exported zone files.
7. Re-enable the transfer lock at the new registrar.
8. Re-enable WHOIS privacy at the new registrar.
9. Update your spreadsheet. Mark it moved, note the new expiry date (old expiry + 1 year).

Avoiding downtime

The transfer itself doesn’t change your DNS — nameservers stay as they are unless you change them. Downtime happens when:

• DNS doesn’t carry over. Rare with major registrars, but verify anyway. Your exported zone files are the fallback — re-import them if anything’s missing.
• Email breaks. MX records are the usual casualty. Test send and receive on every email domain after transfer, not just one direction.
• You change nameservers mid-transfer. Don’t. Complete the transfer first, then migrate DNS as a separate, deliberate step if needed.
• A domain expires mid-transfer. This is why you sorted by expiry date. If anything’s expiring within two weeks, renew it at the old registrar first — a failed transfer on an expired domain is a mess.

A domain expires mid-transfer. This is why you sorted by expiry date in Phase 1. If anything’s expiring within two weeks, renew it at the old registrar first — a failed transfer on an expired domain can send it into redemption, which is expensive and slow to reverse.

Registrant contact changes trigger locks. Updating the registrant name, organization, or email can trigger a fresh 60-day transfer lock at some registrars. If you’re cleaning up contact details, do it after the migration, not during.

Troubleshooting failed transfers

“Invalid auth code.” The most common failure. Auth codes are case-sensitive and sometimes expire. Generate a fresh one at the old registrar and retry — don’t reuse one from yesterday.

“Domain is locked.” The transfer lock is still on at the old registrar, or there’s a 60-day lock from a recent registration, transfer, or contact change. Check both.

“Transfer rejected by losing registrar.” Some registrars email you asking to approve or deny — if you miss the email, some default to deny rather than approve. Watch your inbox during migration week.

WHOIS privacy interference. If a transfer fails for no clear reason, disable privacy at the old registrar and retry. Re-enable at the new one.

ccTLD weirdness. If a .uk, .io, or other ccTLD fails, stop and read that TLD’s specific process — forcing the standard flow wastes days.

Phase 5: Post-migration audit

When the last batch lands:

1. Verify every row in your spreadsheet — new registrar, new expiry, lock on, privacy on.
2. Run a DNS check on every domain with services attached. Every site loads, every mailbox works.
3. Confirm auto-renew settings at the new registrar match your intentions.
4. Disable auto-renew at the old registrar for everything — then, after a 30-day safety window with zero issues, close the old account.
5. Update your records — the spreadsheet, your password manager, any documentation that names the old registrar.

Timing

Each batch takes about 30 minutes of active work, then up to 5 days of waiting (less if you approve every confirmation email promptly — most of the wait disappears). A 40-domain portfolio in batches of 10 = four work sessions spread over roughly a week. Not a weekend project, but not a saga either. The inventory spreadsheet is the part people skip and regret skipping — every hour spent on it saves two in troubleshooting later, and it doubles as your audit trail when the migration is done.

Where to move

Leaving Namecheap: Namecheap → Porkbun or Namecheap → Cloudflare. Leaving GoDaddy: GoDaddy → Porkbun. Choosing: compare the options and best registrars for portfolios. Mechanics refresher: how domain transfers work.