Email Migration
Migrating Email to a New Host Without Losing a Single Message
A safe, step-by-step sequence for moving mailboxes: IMAP sync, MX TTL changes, and post-cutover verification.
2
Weeks recommended overlap for old mailboxes
24/7
Human support during migration
Free
Managed migration assistance
30-day
Money-back guarantee to test the new host
In short
To migrate email to a new host safely, first create matching mailboxes on the new server, lower your MX record's TTL a few days ahead of time, then use an IMAP sync tool to copy every folder and message across before switching MX records. Keep the old mailboxes active for a week or two after cutover so any mail still in transit isn't lost.
The riskiest part of any email migration isn't the copying itself — it's the window around the MX cutover, when old and new servers can both be receiving mail simultaneously if DNS hasn't fully propagated.
Moving a website is usually simple compared to moving email, because email involves not just data but live, constantly-arriving traffic that has to keep flowing during the switch. Get the sequence wrong and you can lose invoices, customer replies, or weeks of archived correspondence permanently, since there's no 'undo' for mail that bounced during a bad transition.
Done in the right order, though, an email migration to a new host is a low-risk, well-understood process. This guide walks through preparing the new mailboxes, syncing existing mail with IMAP, timing the MX cutover, and confirming nothing was left behind.
Prepare the New Host Before Touching DNS
Before any DNS record changes, create every mailbox on the new host with the exact same addresses as the old one, matching usernames, aliases, and forwarders. This gives you a fully functional destination to sync mail into and lets you test sending and receiving from the new server in isolation, using its direct hostname or IP, without affecting live mail flow for your domain yet.
It's also the point to double-check password policies, mailbox storage limits, and any spam filtering rules you rely on, since these settings rarely transfer automatically between hosts. Confirming the new environment works correctly first means any problems you find are isolated to setup, not tangled up with an in-progress cutover.
Sync Existing Mail with IMAP Before Cutover
With both the old and new mailboxes active, use an IMAP migration tool (available in most cPanel-style panels, or third-party tools like imapsync) to copy every folder — inbox, sent, drafts, and any custom folders — from the old server to the new one. Because IMAP syncs are read-only against the source, this step carries no risk of deleting anything from the old host, so it can be run more than once if needed to catch mail that arrived mid-sync.
Run an initial full sync a few days before the planned cutover, since large mailboxes with years of archives can take hours to copy completely. Plan a final, quick top-up sync immediately before you change MX records, capturing anything that arrived between the first sync and the cutover moment.
Lower MX TTL and Time the Cutover
MX records tell the internet which server handles mail for your domain, and like any DNS record they're cached by other mail servers for a period defined by their TTL (time to live). A few days before cutover, lower your MX record's TTL to a short value such as 300 seconds (5 minutes), so that when you do make the actual switch, the change propagates to most of the internet within minutes instead of the default 24-48 hours some records use.
Perform the actual MX cutover during a low-traffic window for your business, and immediately after switching, run the final top-up IMAP sync to catch any messages the old server received in the last few minutes before mail traffic fully redirected to the new host.
Verify Delivery and Keep the Old Mailboxes Active
After cutover, send test emails from external accounts (Gmail, Outlook, a phone carrier email) to each migrated address and confirm they arrive in the new mailboxes promptly. Check that outbound mail from the new server isn't landing in recipients' spam folders, since a brand-new sending IP may need extra deliverability steps, including SPF, DKIM, and DMARC records matching the new host.
Keep the old host's mailboxes accessible, unchanged, for at least one to two weeks after cutover. DNS propagation isn't instantaneous everywhere, so some senders may still route mail to the old server briefly; having it still active means that mail isn't lost, just delayed until you do one final sync before decommissioning the old account.
Free Managed Migration, Handled by a Human
Hosting Cheap's free managed migration service covers full email migration, not just website files — our team can set up matching mailboxes, run the IMAP sync, and coordinate the MX cutover with you so nothing arrives out of order.
If anything looks off after cutover, 24/7 human support is available to check mail flow, DNS propagation, and deliverability together rather than leaving you to piece it apart alone.
- Free managed migration for full mailboxes, not just websites
- IMAP sync copies every folder without touching the source mailbox
- 24/7 human support throughout the cutover window
- 30-day money-back guarantee to confirm mail flow before committing
Why Hosting Cheap
What you get
Free managed migration
Our team helps set up mailboxes and coordinate the cutover at no extra cost.
IMAP-based syncing
Copy every folder safely without deleting or altering anything on the old server.
Low-TTL DNS control
Adjust MX record TTL directly in the panel to speed up propagation before cutover.
24/7 support
Get real-time help during the cutover window if anything needs checking.
Daily backups
Newly migrated mailboxes are backed up daily from the moment they're created.
30-day guarantee
Confirm mail flow works perfectly with a full 30-day money-back guarantee.
How It Works
Get set up in a few steps
Build and test the new mailboxes
Recreate every address on the new host and confirm sending and receiving work in isolation.
Sync mail and lower MX TTL
Run an IMAP sync of all folders and shorten your MX TTL a few days ahead of cutover.
Cut over and verify
Switch MX records, run a final top-up sync, and test delivery from outside accounts.
Included
Everything you need, on every plan
- Matching mailboxes created on the new host with identical addresses
- Password policies and storage limits checked on the new server
- Initial full IMAP sync completed a few days before cutover
- MX record TTL lowered to a short value ahead of the switch
- MX records updated during a low-traffic window
- Final top-up IMAP sync run immediately after cutover
- Test emails sent from external accounts to confirm delivery
- Old mailboxes kept active for one to two weeks post-cutover
FAQ
Frequently asked questions
Will I lose email during a host migration?
Not if you follow the IMAP-sync-then-cutover sequence: sync existing mail before switching MX records, do a final top-up sync right after, and keep the old mailboxes active for a week or two in case any mail is still routed there during propagation.
How long does an email migration take?
Setting up new mailboxes and running an initial IMAP sync typically takes a few hours to a day depending on mailbox size, though very large archives can take longer. The MX cutover itself, once TTL is lowered, propagates within minutes to most of the internet.
What is MX TTL and why does it matter for migration?
TTL (time to live) controls how long other mail servers cache your MX record before rechecking it. Lowering it before cutover means the switch to your new host reaches the rest of the internet in minutes instead of up to two days.
Do I need to change my email password after migrating?
Not necessarily, but it's worth setting a fresh password on the new host's mailboxes as a security best practice, especially if you're consolidating from an older or less secure hosting environment.
Can Hosting Cheap migrate my email for me?
Yes, free managed migration covers full mailboxes as well as websites — our team can set up matching accounts, run the IMAP sync, and help coordinate the MX cutover so nothing is lost.
Why keep the old mailboxes active after cutover?
DNS propagation isn't instant everywhere, so some senders may briefly still route to the old server after you switch MX records. Keeping old mailboxes live for a week or two lets you catch and sync any late-arriving mail before decommissioning.
Move Your Email With Zero Lost Messages
Free managed migration and 24/7 human support handle the mailbox move for you.
Get Started