Moving a domain between registrars can be risky; one wrong change to the DNS records can cause a website or inbox to go quiet. The risk gets even bigger when the domain is registered in an old account and the email for it is somewhere else entirely.
During the September 24, 2026, Office Hours livestream, a viewer asked for advice on exactly this kind of situation. Nathan Ingram, the agency trainer here at hosting.com, walked through how he handles it.
In this post we'll go over what Nathan explained, the process he uses, and his reasoning behind the order of operations, plus a few things to keep in mind when email is on the line.
What did the viewer ask?
The question brought up during the livestream is one that many agencies have to deal with: the client's domain is tied to a hosting account, but the email is managed on a separate service.
Here is how our viewer posed the question:
A client managed email on Fastmail. His domain is tied to a hosting account. We are trying to move the domain to another provider so it's not tied to the hosting account.
We need to manage the DNS so that there is an A record to point to the hosting on my hosting server. And MX records to manage the email on Fastmail.
Looking for recommendations where to move the domain and how to do it safely without messing up the email. Cloudflare?
Are you still encouraging clients to purchase and have their own account for domains?
As you can see, there are three parts to this question:
Where should the domain move to?
How can it be done without disrupting email?
Should the client own the domain in their own account?
Two terms are worth defining here: the A record, which points the domain to the server where the website is, and the MX records, which tell the internet where to deliver the domain's email. Both must survive the move.
Let's start from back to front, as domain ownership is what shapes everything else.
Should clients own their own domains?
Nathan answered this part of our viewer's question first with a clear yes. In his view, it's always best practice to let the client manage their own domain. This matters in our viewer's case because her client's domain is tied to a hosting account.
Since she’s trying to separate the domain from the hosting account, having the domain in the client’s own account makes untangling it easier. Nathan’s own reasoning on domain ownership is a matter of principle:
Philosophically, I believe that customers should own their own domain name. It's their business property. They should own it.
That view rests on a distinction Nathan was quick to clarify: registering a domain and managing its DNS are two different things. Keeping them separate is what makes client ownership of domains workable for an agency. The client holds the registration in their account, and the agency is given access to manage the DNS.
This way, the client owns something that belongs to their business, and the agency can still do the technical work it was hired for. Nathan said he's handled this in different ways over the years, and the one he finds easiest is to do it with the client:
Get on a Zoom call, help them set up a Cloudflare account. You can, once they set up the Cloudflare account, add a payment method and then delegate access to you.
Doing it this way keeps the client in the loop while the account is created, and it means the agency does not have to wait on a back-and-forth of emails to get started. Everyone being immediately informed of such developments is a much better situation to be in, than having to wait.
Ultimately, the setup comes down to three things:
The client creates and owns the Cloudflare account.
The client adds a payment method, so the domain can be paid for and transferred in.
The client delegates access to the agency, so the agency can do the migration work.
There is one detail worth raising with the client, though. Nathan pointed out that delegated access in Cloudflare can be broad, including "all the rights to do everything, including spend money on their card." That's a good reason to agree, in advance, on what access the agency will have and what it will and won’t do with it, so nobody is surprised later.
Why consider Cloudflare for a domain move like this?
When our viewer asked if they should use Cloudflare, Nathan's answer was yes. This post uses Cloudflare as the example because it's the route he walked through, and because Cloudflare's process has a requirement that the domain has to be running through Cloudflare for DNS before the registration can move in. More on that below.
Our viewer also mentioned that Fastmail offers some domain registrations but that she was not sure they would cover DNS for an A record. That's worth confirming with any provider before relying on it. Whatever provider you choose, the website's A record and the email's MX records need a home that you can manage.
How do you move the domain without breaking email?
The core idea is to settle DNS first and move the registration last. That way, the website and email records are never left without a home. Nathan walked our viewers through the sequence in one go, and the order he gave is deliberate:
Set the domain up in Cloudflare. Import your DNS ... and then flip the name servers so that Cloudflare is now the DNS. Then you can do the transfer domain over to Cloudflare.
Each step of the process sets up the next one, which matters a great deal for a client whose email runs through the same domain. For a setup like our viewer's, this is what the process looks like:
Ensure access to the current DNS and the domain. Nathan asked if our viewer had that login because they'd need access to both.
Export all of the DNS records from the current provider. Nathan stressed keeping that exact download so it can be uploaded into Cloudflare during the migration. For our viewer's client, that export should include the A record for the website and the MX records that route email to Fastmail.
Add the domain to Cloudflare and import the records. The domain doesn’t have to be at Cloudflare yet, and Nathan was clear this step comes before the transfer.
Change the name servers. Once the records are in, you point the domain's name servers at Cloudflare so it becomes the DNS provider.
Transfer the registration. This comes last. Take the transfer code from the previous registrar and enter it in Cloudflare.
Because the domain transfer is the last thing to occur, the A record and MX records are already in place and working by the time the transfer happens. The next section explains why doing it like this is important.
Why does the order matter?
The order is not just a matter of preference. Nathan explained that Cloudflare enforces it:
In order to transfer a domain, the domain has to already be set up in Cloudflare for DNS.
If you try to do the transfer first, you'd hit a wall. But there's also a timing benefit, too. Another viewer pointed out in the chat that the transfer takes time, so the DNS should move first anyway.
Settling DNS first means the site and email are sorted while the transfer catches up. Nathan’s verdict on the approach is that it's going to make life a lot easier for everyone.
What if the current registrar makes the transfer slow?
Not every domain transfer goes smoothly, and it helps to set expectations with the client. In Nathan's experience, when he had to move a bunch of domains from one registrar to another a couple of years ago, it was almost instantaneous.
However, he was also quick to add that not all registrars work that way. If the current registrar is slowing things down, the DNS-first order is what keeps you covered, and it's worth leaving extra time before the client expects everything to be finished.
Can you still manage client sites if the client owns the domain?
A third viewer asked in the chat whether Nathan keeps customer sites in his own Cloudflare account. He does have access to them, but the domain itself stays with the customer:
Oh, totally... We have access to them. But if the customer is buying it, like the customer should own their domain.
And that's the model in a nutshell. Ownership of the domain sits with the client while the agency's access covers the day-to-day management. The client keeps control of their business property, and the agency can still do the work it was hired for.
Where can you learn more about Cloudflare?
As the process we described relies heavily on Cloudflare, you might be wondering where you can learn more about it.
We recommend the Cloudflare basics: setup and configuration and Cloudflare advanced: optimization and security livestreams Nathan did for a guided tour of the interface and what the platform can do for you.
If you have questions you'd like to ask Nathan directly, or want to learn more about WordPress, AI, agency work, and web hosting in general, you are also welcome every Thursday at 2 p.m. ET for Office Hours. Bring your questions or simply listen in to learn new things.
FAQ
What do you need from the current registrar before transferring a domain to Cloudflare?
You need to unlock the domain and request an authorization code, sometimes called a transfer or EPP code.
These codes often expire, so request one when you’re ready to use it. The domain also can’t have been registered or transferred in the last 60 days. A recent change to the registrant’s name, organization, or email can trigger the same 60-day lock.
How long does the move take?
After the name servers are changed, the domain usually shows as active in Cloudflare within minutes, though it can take up to 24 hours.
You can’t enter the transfer code until it does. The transfer itself depends on the current registrar. Cloudflare says it can take up to 10 days, and most registrars finish within 5 business days of your approval. Because DNS is already running at Cloudflare by then, the website and email aren’t waiting on the transfer.
Do you need to turn off DNSSEC before moving a domain?
If DNSSEC is enabled at the current registrar, yes.
Cloudflare recommends disabling it there first and waiting at least 24 hours before changing name servers. Then re-enable it in Cloudflare once the transfer completes. DNSSEC adds a digital signature to DNS answers, and leaving the old one in place when you switch DNS providers can make lookups fail.