How to Move Business Email to a New Host Without Losing Mail
Two weeks before you move email anywhere is not the time to start reading about MX records. And yet that is exactly when most people start, because email migrations tend to get scheduled as an afterthought to a website move, rather than planned as their own job with their own risks.
The website can go down for an hour with nobody much noticing. Email cannot. A gap of even a few minutes at the wrong moment can mean a quote, a booking or a supplier reply vanishes into a mailbox that no longer exists, and nobody finds out until the customer calls asking why nobody replied.
This is one of the practical guides in the business email section of the knowledge centre, and it’s worth reading in full before you touch a single DNS record.
Short answer: Moving email to a new host means setting up mailboxes on the new provider, copying existing mail across, then repointing your domain’s MX records once everything is confirmed working. Done properly, mail keeps flowing throughout by lowering DNS TTLs beforehand and running both providers briefly in parallel.
What actually has to happen when you move email to a new host?
Three separate things need to happen in order: mailboxes get created on the new host, existing mail gets copied across so history isn’t lost, and the domain’s MX records get updated to tell the internet where new mail should be delivered. Skipping the order, especially changing MX records before mail is actually migrated, is where most problems start.
None of the three steps is technically hard on its own. The difficulty is entirely in the sequencing and the timing.
How do you prepare before touching anything?
Lower the TTL, or time to live, on your domain’s MX records to around 300 seconds two days before you plan to move. This is the single most useful thing you can do, because it controls how long other mail servers cache your old MX records and keep trying to deliver to the old address after you’ve switched.
- Lower MX record TTL to 300 seconds two days beforehand
- List every mailbox that needs to exist on the new host, including shared or catch-all addresses
- Note any devices, forms or third-party tools that send mail through the old mailbox, since those need reconfiguring too
- Confirm you have full admin access to both the old and new mail systems before you start
If you’re not certain how many mailboxes actually need to move, it’s worth trimming the list before the migration rather than after. The guide to how many mailboxes a small business actually needs is a quick read and often shrinks the job.
Do you need to copy old emails across, or just set up new mailboxes?
Most businesses need the history moved, not just a fresh empty mailbox, since years of client correspondence and order confirmations often live nowhere else. IMAP migration tools, built into most mail platforms, can copy folder structures and messages directly from the old server to the new one without anyone downloading a single file.
Where a direct IMAP transfer isn’t available, exporting to a standard format and importing on the new side is the fallback, though it takes longer and is more fiddly with attachments and folder structure than a direct transfer.
When should you actually switch the MX records?
Only after mailboxes exist on the new host and, ideally, mail history has been copied across. Switching MX records is what tells the world’s mail servers to start delivering to the new location, so doing it before mailboxes are ready means incoming mail has nowhere to land.
| Stage | What happens | Timing |
|---|---|---|
| Lower TTL | Shortens how long old MX records stay cached | 1 to 2 days before the move |
| Create mailboxes | New addresses exist on the new host, empty | Before switching MX |
| Copy mail history | Old messages transferred via IMAP or export | Before or immediately after switching MX |
| Switch MX records | New mail starts arriving at the new host | Once mailboxes and access are confirmed |
| Monitor both inboxes | Watch for stray mail still arriving at the old address | For a few days after the switch |
What tends to go wrong during an email move?
Mail arriving at the old server after the switch is the most common issue, caused by other servers holding a cached MX record until its TTL expires. This is exactly why lowering TTL in advance matters, since it shrinks that window from potentially two days to a matter of hours. Checking the old mailbox for a week after the move catches anything that still slips through.
Password resets and app-specific logins are the other common trap. Every device and app that had the old mailbox configured, phones, Outlook, invoicing software, needs the new server details entered manually, and this is usually the step that gets forgotten until someone’s phone stops receiving mail.
Is it worth doing this yourself or having someone else run it?
A small setup with two or three mailboxes and no complex forwarding is manageable to move yourself if you follow the sequence carefully and don’t rush the MX switch. A larger setup, or one with mail-dependent automations like invoicing systems or CRM integrations, carries more risk if something is missed, and that’s where paying someone to run the whole migration earns its cost.
Once mail is flowing through the new host, check its SPF and DKIM records are set up correctly too, since a fresh set of sending servers needs its own authentication rather than inheriting the old ones. The guide to SPF, DKIM and DMARC explained covers exactly what to check.
Frequently asked questions
Will I lose emails during the migration if I follow the right order?
Following the sequence correctly, lowering TTL, setting up mailboxes, copying history, then switching MX records, keeps the risk very low. Most losses happen when steps are done out of order or when the old mailbox is deleted before everyone has confirmed the copy is complete.
How long does moving business email to a new host usually take?
The mailbox setup and mail copy can often be done in a day for a small number of accounts. The safer total window, including the TTL lowering beforehand and monitoring afterwards, spans closer to a week from start to finish.
What happens to emails sent to my old address after I switch?
With a properly lowered TTL, this window is short, typically hours rather than days, though a small number of servers may still hold an old cached record for longer. Checking the old mailbox for stray messages for about a week after the switch is the standard precaution.
Do I need to tell my contacts my email address is changing?
No, not if you’re keeping the same email address and only changing which server hosts it. Your address stays exactly the same; only the infrastructure behind it moves, so nobody needs to update anything on their end.
Can I migrate email and my website at the same time?
You can, but treating them as one job increases risk, since a website issue can distract attention from monitoring the mail switch, and vice versa. Doing the website first, confirming it’s stable, then handling email separately tends to go more smoothly.
If the mailbox count and sending tools involved make this feel like more than a weekend job, GoodHost’s migrations team can run the move for you, and you can read what’s involved at goodhost.com.au/migrations before deciding whether to do it yourself.