Change Hosting, Keep Your Domain and Email Where They Are

Yes, you can change WordPress hosting without moving your domain or your email. The registrar, the DNS, the website and the mailbox are four separate services, and a host move touches only the website. In most cases you change one or two DNS records (the root A record and the www record) and leave every mail record alone.

I've had some version of the same phone call dozens of times. An office manager at an eight-person accounting firm knows the website host is bad. Pages load slowly, support takes three days to answer, the renewal invoice just jumped. Everyone agrees the site should move. Then someone asks, "Will we lose our email?" and the project stalls for another year.

That fear is reasonable. Everybody has heard about the company that changed something with its website and spent two days with no inbound mail. But when you look at what happened in those stories, it is almost always the same mistake, and it is avoidable. This post walks through which pieces of your setup move, which stay put, and the order that keeps the site up and the inboxes full.

Can you change hosting and keep your domain and email?

You can. Changing hosts means copying your WordPress files and database to a new server and pointing your domain's website records at it. Your domain registration, your Microsoft 365 or Google Workspace mailboxes, and the DNS records that route mail do not need to move. Most clean migrations change two records and nothing else.

The confusion comes from the fact that many people bought everything in one place years ago. GoDaddy sold you the domain, the hosting and maybe an email plan in the same checkout, so it all feels like one thing. It's four:

• The registrar holds your ownership of the domain name. You pay it once a year. It doesn't serve your website or your mail.
• The DNS host answers the question "where does this domain's website and mail live?" It's set by the nameservers on your domain. Often it's the registrar, sometimes Cloudflare, sometimes your old web host.
• The web host runs WordPress. This is the only piece you're replacing.
• The mail provider stores and delivers your email. If that's Microsoft 365 or Google Workspace, it doesn't care which company hosts your website.

According to Verisign's Domain Name Industry Brief, roughly 360 million domain names were registered across all top-level domains at the end of 2024. Registrars, DNS providers and web hosts are built to be mixed and matched, and the whole system assumes you might use a different company for each.

If you're leaving a hosted builder like Wix or GoDaddy Websites + Marketing rather than a WordPress host, the order of operations is a bit different, and we cover it in leaving a website builder without losing your domain or email.

Which DNS records change when you switch WordPress hosts?

Only the records that point at your web server change. That's the A record for the root domain (yourfirm.com), the www record (usually a CNAME or a second A record), and an AAAA record if your old host set one for IPv6. Mail routing, mail authentication and service verification records stay exactly as they are.

Here's what a typical zone looks like for a firm with a WordPress site and Microsoft 365 or Google Workspace mail:

Two rows deserve a closer look.

The AAAA record catches people. If your old host published an IPv6 address and your new host doesn't, a leftover AAAA record sends some visitors to the old server for as long as that server stays on. The site looks fine from your office and broken for a customer on a phone network that prefers IPv6. Update it or delete it at cutover.

The SPF record matters if your WordPress site sends email. Contact forms, WooCommerce order confirmations and password resets often go out through the web server itself. If your SPF record has an entry like ip4:198.51.100.22 for the old server, those messages will start failing authentication once the site moves. The fix is to send site mail through Microsoft 365, Google, or a transactional service via SMTP, then make sure SPF covers that route. Our guide to fixing WordPress email deliverability covers the SMTP setup, and there's a good argument for keeping transactional email off your marketing subdomain while you're in there.

What breaks email during a hosting migration?

Email almost never breaks because the website moved. It breaks because the DNS zone lived at the old web host, and someone either cancelled that host or changed nameservers before copying every record across. When the zone disappears, the MX records go with it, and inbound mail starts bouncing or queueing within hours.

Here's how that plays out. Years ago, the registrar's nameservers were changed to something like ns1.oldhost.com so the host could "manage everything." The MX records for Microsoft 365 got added inside the host's control panel. Nobody remembers that. Then the new host says "point your nameservers to us," the owner does it, and the new zone has an A record and nothing else. Mail stops.

Before you touch anything, look up your nameservers. Any WHOIS lookup or a command like dig NS yourfirm.com will show them. If they point at your registrar or at Cloudflare, you're in the easy case: you'll edit two records and leave the nameservers alone. If they point at your current web host, you have one extra job, and it should happen on a different day from the site move.

The other email trap is mail that's hosted by the web host itself. If your addresses live in cPanel mailboxes on the old server, cancelling the host deletes the mail. That's a separate migration, and frankly a good moment to rethink it. We've written about why your host's free mailboxes are not a business email plan. If you're already on Microsoft 365 or Google Workspace, you can skip this paragraph.

A third, smaller one: Cloudflare. If your DNS is on Cloudflare with the orange-cloud proxy on, changing the A record works the same way, but SSL settings on the new host and Cloudflare have to agree or the site will loop or throw errors. We broke that down in why the orange cloud breaks WordPress.

How to switch hosts with zero downtime

A zero-downtime move runs the new site and the old site side by side, tests the new one privately, and then flips the A record during a quiet hour with a short TTL. Visitors land on one working copy or the other, never on nothing. Mail records are never touched, so inboxes don't notice the move at all.

Here's the order we use, written so you can follow it with any host:

1. Save a copy of your current DNS zone. A zone file export, or screenshots of every record. This is your rollback plan for DNS.
2. Find out where DNS is hosted by checking the nameservers.
3. If DNS lives at the old web host, move the zone first. Recreate every record (MX, SPF, DKIM, DMARC, autodiscover, verification TXT, and the current A record) at your registrar's DNS or at Cloudflare. Send and receive test mail. Then switch the nameservers. Give this a few days before the site move.
4. Lower the TTL on the A, AAAA and www records to 300 seconds. Do it 24-48 hours ahead, because resolvers keep the old TTL until it expires. If your old TTL was 86400 seconds, that's a full day.
5. Copy the site to the new host and test it before DNS changes, using the new host's preview URL or a line in your computer's hosts file.
6. Pick a quiet hour. For a brochure site, any evening works. For a WooCommerce store, pause checkout for 15-30 minutes or run a final database sync right before the switch so no orders land on the old server.
7. Change the A record, the www record, and update or delete the AAAA record. Nothing else.
8. Check that SSL is issued on the new host, then test forms, checkout, logins and a few deep links.
9. Leave the old hosting account running for 7-14 days. Some resolvers ignore low TTLs, and you want stragglers to see a working site.
10. Cancel the old host, note the date so you don't get billed for a renewal you didn't want, and raise the TTL back to 3600 seconds.

People talk about "DNS propagation" as if the change spreads slowly across the internet. What happens is that caches expire. If the TTL is 300 seconds, most visitors see the new server within five minutes. That short TTL also gives you a fast rollback: put the old IP back and you're on the old host again in minutes.

After cutover, watch for 404s. Migrations that also change permalink structure or drop old pages leave broken links behind, and TopSyde customers can see and fix those from the portal, which we describe in broken links and 404s, fixed from your TopSyde portal. The full technical checklist for the site copy itself is in our WordPress migration guide.

What does staying on a bad host cost compared to moving?

A careful move costs a few hours of planning and one short evening window. A bad move that takes email down for a business day can cost a small firm a couple of thousand dollars in lost time. Staying put also has a price: renewal increases, slow support and outages you absorb every month you delay.

Run the numbers for our eight-person firm. If email goes down for four hours and each person's time costs the business $60 an hour, that's $1,920 before you count a missed client message or a bounced invoice. That figure is why the fear is rational. It's also why the plan above never touches mail records.

Now look at the other side. Renewal pricing on budget hosts often doubles or triples after the intro term, which we unpacked in why your hosting bill doubled at renewal. Slow support turns a 20-minute fix into a three-day wait. And when a WordPress vulnerability drops, a budget host may leave patching entirely to you, while a managed host can block the attack at the server level; we compared that in does your managed host protect you from zero-days.

According to W3Techs, WordPress runs about 43% of all websites (2025). That popularity makes it the most targeted CMS, and it's the main reason the host you pick affects your security as much as your speed. If you're weighing what kind of host to move to, managed vs unmanaged WordPress hosting lays out what you take on yourself with each.

The pattern I see most often: a business stays on a host it dislikes for 12-24 months because of the email question, pays two renewal cycles at the inflated price, and then moves in an afternoon once someone explains which records change. The delay costs more than the move.

How does a TopSyde migration handle DNS and email?

We copy your WordPress site to our servers, test it with you before anything public changes, and then tell you which records to update at your registrar, or update them alongside you on a call. Your mail records stay where they are. Microsoft 365 and Google Workspace keep delivering the whole time.

Concretely, here's what you get when you move to us:

• Your domain stays at your current registrar. We don't ask you to transfer it.
• Your DNS can stay where it is. If it lives at your old web host, we'll help you move the zone to your registrar or Cloudflare first, with every mail record copied and checked.
• A staging copy of your site on our infrastructure that you can click through before cutover.
• A cutover window you choose, with the old host left running until you're satisfied.
• A check of site-sent email (contact forms, order notifications) so it authenticates correctly from the new server.

Once you're live, monitoring runs 24/7, and a site-down ticket is answered within 15 minutes, 24/7, as written on our service level agreement. Other support tickets are answered in under 2 hours during business hours. The full list of what's included is on the spec sheet.

Plans start at $89/mo per site, and there's a 30-day free trial so you can run the new site on our hosting before you cancel the old one. Pricing for single sites and for multiple sites is on the pricing page. If you're a business owner with one or two sites, start at TopSyde for individuals. If you're an agency moving a stack of client sites that each have their own registrar and mail setup, TopSyde for agencies covers how we handle batch moves.

Tell us where your domain is registered and who runs your email. We'll tell you which two records will change, and you can decide from there.

Frequently Asked Questions

Do I need to transfer my domain to change web hosts?

No. The domain registration and the web hosting are separate services. You keep the domain at your current registrar and point its website records at the new host, which takes a few minutes in the registrar's DNS settings.

Will my Microsoft 365 or Google Workspace email go down when I switch hosts?

Not if the MX, SPF, DKIM, DMARC and autodiscover records stay in place, and a normal host move doesn't require touching any of them. The risk appears only when the DNS zone lives at the old host and gets deleted or replaced before those records are copied, so check your nameservers first.

How long does DNS take to update after changing hosts?

It depends on the TTL set on your A and www records. If you lower the TTL to 300 seconds a day or two before the move, most visitors reach the new server within about five minutes of the change. Keep the old host running for a week or two to catch resolvers that hold the old address longer.

What if my email is hosted by my current web host?

Then cancelling the host deletes the mailboxes, so the mail has to move before the hosting account closes. Most small businesses use the host change as the moment to move to Microsoft 365 or Google Workspace. Do the mail move first, confirm it works for a few days, then move the website.

Marcus Webb

DevOps & Security Lead

12+ years DevOps, Linux & cloud infrastructure certified

Marcus leads infrastructure and security at TopSyde, managing the server fleet and AI monitoring systems that keep client sites fast and protected. Former sysadmin turned WordPress hosting specialist.

LinkedIn