A domain transfer moves the registration — who you pay, where the paperwork lives — from one registrar to another. Done right, your site and email never blink, because the transfer itself doesn’t have to touch DNS at all. Done in a hurry, the old registrar’s DNS gets shut off mid-move and everything goes dark. This lesson is for anyone leaving a registrar they’ve outgrown, or reclaiming a domain from a developer who’s holding it. You’ll need logins at both registrars and a working grasp of your DNS records.

Export your DNS records before anything moves

If your domain uses the old registrar’s nameservers, those records can vanish when the transfer completes — so copy everything first. Use the panel’s export button, and confirm from the outside too:

dig yourdomain.com A +short
dig www.yourdomain.com +short
dig yourdomain.com MX +short
dig yourdomain.com TXT +short
dig NS yourdomain.com +short

Save that output in a dated file. If the nameservers point somewhere independent — Cloudflare, your host — good news: DNS lives outside the fight entirely, and the transfer won’t touch it.

Unlock the domain and get the transfer code

In the old registrar’s panel, turn off the transfer lock, then request the auth code (also called an EPP code) — the password that proves you’re allowed to move the domain. Two timing rules to know: ICANN locks a domain against transfer for 60 days after registration, a previous transfer, or a change to the registrant contact. If any of those just happened, you’re waiting out the clock — plan around it, don’t fight it. Also confirm the contact email on the domain is one you can actually read; approval messages go there.

Check the expiry-date fine print

A transfer includes one year of registration, added on top of whatever time you have left — you don’t lose paid time by moving. But don’t start a transfer in the last couple of weeks before expiry: if it stalls and the domain lapses mid-move, you’re into redemption fees and real downtime. Inside 30 days of expiry? Renew at the old registrar first, then transfer at your leisure. Boring, and correct.

Start the transfer at the new registrar

At the destination, choose “transfer a domain,” pay (that payment is the year of renewal), and paste the auth code. Then watch your inbox — both registrars may email asking you to approve. Approve promptly at both ends and the move often finishes in minutes; ignore the emails and it takes the maximum five to seven days instead. The waiting period is the old registrar’s chance to object, not a sign anything’s wrong.

Re-create DNS at the destination

If DNS lived at the old registrar, now rebuild it: enter every record from your step-one export into the new registrar’s DNS panel before you point the nameservers there, then switch nameservers once the zone matches. Records first, nameservers second — that order is the whole zero-downtime trick. If your DNS is hosted elsewhere, skip this step; just confirm the new registrar shows the same nameservers as before.

Verify the site and email still resolve

Check the answers from a public resolver, not your own cache:

dig yourdomain.com A +short @8.8.8.8
dig yourdomain.com MX +short @8.8.8.8

Compare against your step-one file — every value should match. Load the site, send yourself an email from an outside account and watch it arrive, then turn the transfer lock back on at the new registrar. Matching records, working mail, locked domain: that’s a finished transfer, and nobody visiting your site ever knew it happened.