Academy › Publishing › Domain and email
The domain transfer happens in three steps, not one
You'll know how to split transfer day into three moves (account, DNS, and email) and carry them out in the right order so you're never left without a website or email.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
When you sell the business or switch agencies, cutting off access for whoever's leaving isn't enough: that day you need to move something bigger than a login. The day the sale is signed, or the day you fire the agency, someone tells you, 'I'll hand everything over this afternoon and we're done.' It sounds reassuring. And it's the line that ends up costing you the most.
When you sell the business or switch agencies, cutting off access for whoever's leaving isn't enough: that day you need to move something bigger than a login. The day the sale is signed, or the day you fire the agency, someone tells you, "I'll hand everything over this afternoon and we're done." It sounds reassuring. And it's the line that ends up costing you the most.
If you move all three at once and one of them gets stuck, your website can stop loading or your email can stop arriving, and there's no quick way to tell which of the three caused it.
First the account, then the DNS, then the email
- 1Change the owner at the registrar
If the domain stays with the same registrar, you just need to change the account's owner and email: the registrar asks for confirmation from both the previous owner and the new one. If you're also switching registrars, ask the current one for the transfer code (the EPP or AuthInfo code) and complete the transfer before changing the owner. According to ICANN's transfer policy, which governs generic domains like .com (the mandatory version since August 2025), changing the owner triggers a 60-day lock that blocks moving the domain to another registrar, unless your registrar lets you waive that lock before requesting the change. The ICANN group that reviewed this policy recommends in its final report dropping this lock and the double confirmation from both owners, the old one and the new one; until that change takes effect, the lock and double confirmation still apply, so ask your registrar which rules it follows. That same day, don't touch the DNS: an ownership change only affects the owner's name, organization, and email, so the servers the domain points to, the nameservers, stay exactly the same, and your website and email keep working exactly as before. If you're also switching registrars and your outgoing registrar is the one hosting your DNS, ask them beforehand whether they'll keep serving it once the domain is no longer with them. - 2Wait for confirmation
If you're switching registrars, the same policy requires your current registrar to give you the code within five calendar days at most, if it doesn't let you generate it yourself, and gives it another five days to respond to the transfer request: if it doesn't respond in that window, the transfer is approved automatically. If you're staying with the same registrar, it has to process the ownership change within one day of receiving both confirmations. During this wait, the account change is already underway, but nothing else moves yet. There's no rush: the domain keeps resolving normally. - 3Move the DNS, if the new owner wants a different provider
First, lower the TTL on every record (the setting that controls how long a change takes to kick in) to something short, like 300 seconds. According to Google Workspace's help on DNS, the new TTL only takes effect once the old one expires: if the current one is 86,400 seconds, lower it at least 24 hours before touching anything else. Copy each record one by one: A, CNAME, TXT, MX. Don't delete the old zone until you've confirmed the new one responds the same way. - 4Migrate email last
With the MX record still on a low TTL, set up the new accounts and copy over the email history before changing anything. Only once the new accounts already have the full history do you switch the MX record. Keep the old inbox open for a few days after the switch, so you can catch anything still coming in: according to Google's guide on MX records, a new MX record can take up to 72 hours to be recognized across the internet, and during that window some email may keep arriving at the old server.
Each of these three moves runs on its own clock, and you don't control that clock: the registrar does, or simply how the internet works. Forcing all three through in one afternoon doesn't speed anything up. It just means that if something goes wrong, you've got three suspects at once instead of one. And if your domain is a .es, the account's clock isn't set by that ICANN policy, which applies to generic domains: it's set by Dominios.es. There, the ownership change is started by the owner, their administrative contact, or their registrar agent, and confirmed by the new administrative contact through the Dominios.es panel. The registrar agent change is requested by the new agent and has to be approved by the domain's administrative contact.
All at once or in layers
- One single event, easy to announce
- If something breaks, you don't know whether it was the account, the DNS, or the email
- The possible failures in all three pieces pile up on the same afternoon
- Each piece gets checked before you touch the next one
- If something fails, you know exactly which piece it was
- It takes more calendar days, but none of them with your business down
- You have time to let people know about the old email address before shutting it down
Which one to choose: Go layer by layer whenever you can set the date in advance: an agreed-upon sale, a planned agency switch. You only compress the timeline, never skip the order, when the old provider disappears all at once: a missed payment, a shutdown, a partner who leaves angry. In that case, prep the new account, the new DNS, and the new email in parallel, ready to go live, and as soon as you get the registrar key, you run the ownership change first, then the DNS, then email last.
When you're in a hurry, the excuse for skipping the order is 'the agency stopped answering' or 'the partner who's leaving won't wait.' The urgency can be real. But compressing the timeline and skipping the order are two different things, and mixing them up is where people make the mistake that's hardest to fix.
Before anyone changes anything, ask in writing for the transfer code and an exact copy of the current DNS. That way, if anything gets lost along the way, you have a snapshot of how everything looked before you started.
With this, transfer day stops being a nerve-wracking afternoon and turns into three short appointments, each one checked before moving on to the next. The account changes hands, the DNS resolves the same or better, and email doesn't lose a single message along the way.
What remains to be seen is how, once everything has moved, you prove that you're the only one in control, and no one else.
- A domain transfer is three moves, not one: account, DNS, email
- You know the order that leaves no gap in your website or email: the registrant first, then the DNS, email last
- You know when to compress the timeline without skipping the order: when the old provider disappears overnight
- You have the exact wording to request the transfer code and DNS before anyone touches anything
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. You sell the business, and the buyer's contract requires the entire transfer (account, DNS, and email) to be wrapped up the same day you sign.
Don't promise that date for all three pieces. For a .com switching registrars, the current registrar has up to five calendar days to hand over the transfer code, and another five to respond to the transfer request. What you can get moving on signing day is the account: the ownership change, which the registrar processes within a day once you both confirm it if you're staying with the same one, or the transfer, if you're switching registrars. Then put it in writing that the DNS and email migrate over the following days, with a deadline.
2. The agency that managed the domain shuts down overnight and stops answering the phone.
That's where you compress the timeline: you set up the new account, the new DNS, and the new email in parallel while you get the transfer code. If it's a .com, look up who holds it in ICANN's public lookup, lookup.icann.org, and ask that registrar for the code, proving you're the owner: according to ICANN's transfer policy, they have to give it to you within five calendar days if they don't let you generate it yourself. Once you have the key, move the account first (the transfer and, if needed, the ownership change, in that order), then the DNS. Don't skip the order even if the urgency is real.
3. The new owner wants to migrate the email before the domain's ownership change is confirmed, because "email is the urgent part."
You can set up the new email and copy over the message history without touching the MX records yet, that doesn't depend on who owns the account. But the MX change, the one that makes new mail start arriving in the new inbox, has to wait until the registrar account is confirmed, because if the transfer falls through, the new email is left with no real domain behind it.
The new email is left with no real domain behind it if you skip the order. Three steps done isn't the same as a verified transfer: nine dated checks are still missing.
Sources
- Transfer Policy. ICANN, version updated in 2024 and mandatory since August 21, 2025 (accessed October 2026).
- Final Report of the Policy Development Process on the Transfer Policy Review. GNSO (ICANN), February 4, 2025.
- DNS basics. Google Workspace Help, accessed October 2026.
- Set up MX records for Google Workspace. Google Workspace Help, accessed October 2026.
- Change the domain owner. Dominios.es (Red.es), accessed October 2026.
- Change registrar agent. Dominios.es (Red.es), accessed October 2026.
In Yodai you connect the domain you already have to your site, and it stays registered where it is, in your name. See how your own domain for your website works.
NextThe nine-point checklist that wraps up the handoff