Moving your website to a new host is usually straightforward, but a lot of site owners panic the moment they remember their email runs through the same domain. The good news: your inbox and your website are controlled by two separate DNS settings, which means switching hosts doesn’t have to touch your email at all — unless you let it.
Table of Contents
This guide walks through exactly what happens to email during a host migration, how to tell whether your email is actually moving too, and the steps to take so you never lose a message or suffer downtime.
Quick Answer
Your website and your email are controlled by different DNS records — A records point to your web server, while MX records point to your mail server. Changing web hosts only changes your A record, so your email keeps working through whatever provider (Google Workspace, Microsoft 365, or your old host’s mail servers) you were already using, as long as you don’t touch your MX records at the same time.
Why Your Email Usually Isn’t Affected
DNS splits a domain’s responsibilities across different record types. The A record (or CNAME) tells browsers which server hosts your website. The MX record tells the internet which server handles mail for @yourdomain.com. These are independent settings that live in the same DNS zone but don’t interact with each other.
So if your email runs through Google Workspace, Microsoft 365, or a dedicated email provider, moving your website to a new host changes only the A record. Your MX records — and therefore your email — stay exactly where they are. Many people change web hosts for years without ever touching email, because they’re not using hosting-provided mailboxes.
The situation is different if your email is hosted BY your web host — meaning your inbox lives on the same server as your website (common with shared hosting plans using cPanel webmail, like name@yourdomain.com set up through the hosting control panel). In that case, moving hosts does mean moving your mailboxes, and your MX records need to change along with your A record.
How to Migrate Email Safely When It Does Need to Move
If your email is tied to your old host, treat it as a separate migration from your website, and do it in this order so nothing gets lost. First, set up all your email accounts on the new server (or new provider) using the exact same usernames and passwords, without changing any DNS yet. Second, test the new mailboxes directly using the new server’s hostname in an email client, confirming you can send and receive before any DNS change happens.
Next, lower the TTL (time to live) on your MX records to something short, like 300 seconds, at least a day before your planned cutover — this makes the eventual switch propagate in minutes instead of hours. Once the shorter TTL has had time to take effect, update the MX records to point to the new mail server. With a low TTL, most of the internet picks up the change within minutes to a couple of hours, though DNS changes can occasionally take up to a day or two to reach every resolver.
Keep the old mail server active and don’t delete those mailboxes for at least a week or two after the switch. During the propagation window, some senders’ systems may still briefly deliver to the old server, so checking both inboxes avoids missed messages. Once you’ve confirmed everything is flowing to the new server and nothing is landing on the old one anymore, it’s safe to decommission the old mailboxes.
Tips / Common Mistakes
Don’t change your MX records and your A record on the same day as a reflex — check first whether your email even depends on your web host. If you use Google Workspace or Microsoft 365, it almost certainly doesn’t.
Don’t cancel your old hosting account the moment the new site goes live. Keep it active for at least a week so any lingering mail or DNS caches tied to the old mail server (if email was moving too) have time to clear.
Don’t skip lowering the TTL before a real email migration. Jumping straight from a 24-hour TTL to a new MX record means some mail servers could take up to a day to notice the change, during which messages might route to a server you’re about to decommission.
Double-check SPF, DKIM, and DMARC records if you’re also switching email providers. These records authenticate your outgoing mail, and leaving old entries in place (or forgetting to add new ones) can cause your email to land in spam or get rejected entirely.
Explore more: more web development guides.
Email during a web host migration FAQs
Will I lose email access while my website moves to a new host?
No, not if your email runs through a provider like Google Workspace or Microsoft 365. Since website hosting and email use separate DNS records (A records vs. MX records), moving your site doesn’t interrupt your inbox unless you’re also moving your email at the same time.
How do I know if my email is hosted by my web host or a separate provider?
Check your current MX records (most domain registrars have a DNS lookup tool, or you can use a free online MX record checker). If they point to Google, Microsoft, or a dedicated email service, your email is separate from your hosting. If they point to your hosting company’s own servers, your email lives on your hosting account.
How long does it take for email to fully switch over after an MX record change?
With a properly lowered TTL beforehand, most mail servers pick up the new MX record within minutes to a couple of hours. In rare cases, some resolvers can take up to 24–48 hours, which is why it’s smart to keep the old mail server running for a short overlap period.
Should I migrate my website and email at the same time?
It’s generally safer to separate the two. Migrate and verify your website first, then handle email as its own step with its own TTL reduction and testing period, so a problem in one migration doesn’t compound the other.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Photo by Mariia Berezovsky on Unsplash.