Moving email without losing any mail

Moving email without losing any mail

The way to move email without losing anything is to copy every message across before you touch any DNS record, not after. Create the new mailbox first, copy the contents into it using an email client or a sync tool, check every folder has arrived, and only then switch the MX record so new mail starts landing in the new place. Do it in that order and nothing goes missing. Do it the other way round, changing the address first and copying mail second, and you risk mail arriving somewhere nobody is watching.

Before you start

This assumes you already have a mailbox set up and ready to receive mail in cPanel at Hostworld. If you haven't created that yet, do that first: you need somewhere for mail to land before you start copying anything into it.

You'll also need:

• The mail server hostname, username and password for the old mailbox (wherever it currently lives).
• The mail server hostname, username and password for the new cPanel mailbox at Hostworld. Your cPanel dashboard shows the correct incoming (IMAP) and outgoing (SMTP) settings for the account.
• An email client such as Thunderbird, or, if you're comfortable on the command line and have a large amount of mail to move, a tool such as imapsync.
• Time. A mailbox with several gigabytes of mail can take hours to copy, not minutes, and rushing this step is where mail goes missing.

The biggest mistake people make with an email migration isn't a wrong setting, it's the wrong order: changing where mail is delivered before the new mailbox is actually ready, or shutting down the old mailbox the moment the new one is live instead of leaving it as a safety net. Both of those are covered below, and both are avoidable.

Step 1: Create the new mailbox before you do anything else

The new mailbox has to exist and be reachable before you change where mail is delivered to. If you flip the MX record first and the mailbox isn't ready, incoming mail either bounces or gets accepted somewhere you're not checking, and once mail bounces it's gone for good, the sender's server doesn't keep retrying forever.

Set up the mailbox in cPanel under the Email section, and confirm you can log into webmail for it before moving on. Don't skip that check: a mailbox that exists but that you can't actually get into is no better than one that doesn't exist yet.

If you're moving several mailboxes at once, for example a whole domain's worth of staff addresses, cPanel has an Address Importer under Email that creates a batch of mailboxes (or forwarders) from a spreadsheet in one go. It's worth knowing this exists so you're not creating twenty accounts by hand one at a time, but be clear about what it does and doesn't do: it creates empty mailboxes and forwarders from a list. It does not copy any existing messages into them. The content copy is still a separate step, covered next.

Step 2: Connect an email client to both mailboxes

Add both the old account and the new cPanel account to the same email client, as two separate IMAP accounts. Thunderbird handles this well and is free. Once both are added you'll see two separate folder trees in the same window, one for the old mailbox and one for the new one.

IMAP is what makes this reliable. Because both accounts are connected live, you're copying messages, folder structure, and message flags (read, unread, flagged, replied) directly from one mail server to the other. That's a meaningful difference from an older method some people still use, downloading the raw /mail/ directory from the old server via File Manager or FTP and uploading it to the new one. That raw-file method can work, but it depends on folder names and account paths matching exactly between the two servers, and if they don't, mail goes missing or turns up corrupted with no clear error telling you why. IMAP copying doesn't have that fragility, because both servers are talking the same protocol and agreeing on what a folder and a message actually are.

If you have a genuinely large mailbox, tens of thousands of messages or several gigabytes, a command-line tool such as imapsync is worth considering instead of a desktop client, since it's built specifically for server-to-server IMAP copying and handles interruptions more gracefully than a client left copying in the background. Either approach is copying over IMAP, the choice is really about scale and how comfortable you are on a command line.

Step 3: Copy, don't move

This is the single setting most likely to catch someone out. When you drag messages between the two folder trees in your email client, most clients ask, or default to, either Copy or Move. Choose Copy.

Move deletes the message from the old mailbox as soon as it's transferred. That sounds tidy, but it means if the transfer stalls partway through, which does happen with large mailboxes over IMAP (timeouts are a known issue when a sync runs for a long time), you're left with messages missing from both ends: gone from the old mailbox because Move deleted them, and never arrived in the new one because the transfer didn't finish. Copy leaves the original in place until you've confirmed the new one is complete, which is what you want while you're still checking your work.

Step 4: Verify every folder before you rely on it

Once the copy has finished, don't change anything else until you've checked it properly:

1. Log into webmail for the new cPanel mailbox and open every folder, not just the inbox, checking Sent, Drafts and any custom folders too.
2. Spot-check that attachments open correctly, not just that the message is present.
3. Send a test email to the new address from an account you don't control, and reply to it, to confirm both sending and receiving genuinely work end to end.

Only once that's confirmed should you move on to changing where mail is delivered.

Step 5: Change the MX record, or point the domain, only now

The MX record is what tells the rest of the internet's mail servers where to deliver mail for your domain. Change it too early and you risk mail going nowhere; change it once the new mailbox is copied and verified and you're simply telling incoming mail to start arriving at its new home.

If your domain's DNS isn't managed by Hostworld yet, this is also the point at which you point the domain at us properly, by setting the nameservers at your registrar to:

• ns1.serverworld.uk
• ns2.serverworld.uk
• ns3.serverworld.uk
• ns4.serverworld.uk

Once those nameservers are active, mail routing and the rest of your DNS for that domain is managed from your Hostworld cPanel. If your domain is staying with its current registrar's DNS and only the mailbox is moving, you just need the MX record itself updated to point at the new mail server, which your cPanel account details will show.

Either way, expect a transition window rather than an instant switch. DNS changes take time to spread across the internet, and during that window it's entirely normal, not a fault, for some incoming mail to still land on the old server while other messages start arriving at the new one. Keep checking both mailboxes until that window has clearly passed.

Step 6: Leave the old mailbox running for a few weeks

Resist the urge to cancel, wipe or close the old mailbox the moment the new one is working. Two things can keep sending mail there for longer than you'd expect:

• DNS caching genuinely takes time to clear everywhere, so some senders' mail servers keep using the old MX answer for a while after the change.
• Some mail systems deliver "locally" between accounts they consider to be on the same platform, effectively ignoring DNS, for as long as the old mailbox is still active on that system.

Keeping the old mailbox live and checked for a few weeks after the switch catches anything delivered by either of those routes. Once you've gone a couple of weeks without seeing anything new arrive there, it's safe to close it down.

If what you're actually moving is a whole cPanel account rather than a single mailbox, that's a different job: a full server-to-server account transfer can update the domain's DNS and mail routing as part of the move, all handled on the provider side rather than by copying mail manually. If that's your situation, open a support ticket and describe what you're moving so we can tell you what's involved.

What next

Once your mail is copied over and verified, the next thing worth reading is our step-by-step for the copy itself: copying email with IMAP sync in cPanel, which walks through the client settings click by click. If you're setting up hosting for the first time rather than moving an existing mailbox, our broader email hosting guides cover creating mailboxes, spam filtering and everything else in cPanel. And if anything about your particular setup doesn't match what's described here, for example an unusual number of mailboxes or a large archive, open a support ticket and we'll look at it properly rather than have you guess.