How to Migrate Email Accounts
Migrate email in this order: create every mailbox on the new server first, copy old mail over IMAP while both servers run, lower the MX TTL to 300 seconds a day early, then switch MX, SPF and DKIM together and test from an outside account. Keep the old host online for 72 hours.
For site owners moving mail to a new host without losing messages or sent history.
knowledge
- Read time
- 6 min
- Sections
- 8
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 15 November 2026.
What is the safe order for an email migration?
Mailboxes first, mail copy second, DNS last — reversing any two of these is how mail gets lost. If MX records flip before the new mailboxes exist, inbound mail bounces; if the old host is cancelled on day one, messages that still arrive there during propagation disappear with it.
- Create the mailboxes on the new server with identical addresses, matching quotas, aliases and forwarders.
- Sync stored mail over IMAP while both servers are live, then run the sync a second time to catch mail that arrived during the first pass.
- Verify the copy by comparing folder and message counts, especially the Sent folder, before touching DNS.
- Lower the MX TTL to 300 seconds at least a day before the cutover, so a mistake can be undone in five minutes instead of a day.
- Switch MX, SPF and DKIM together on cutover day — a half-updated authentication set sends legitimate mail to spam.
- Test from an outside account and read the headers for
spf=passanddkim=pass, both inbound and outbound. - Keep the old server online for 72 hours, run one final delta sync, back up the new mailboxes, then cancel.
How do you create the mailboxes on the new server?
Every address, alias and forwarder must exist on the new server before MX records point at it. In cPanel that is Email → Email Accounts → Create; use the same local part as the old mailbox so addresses never change for your correspondents.
- Quota: at least as large as the old mailbox. A 2 GB archive copied into a 1 GB quota stops halfway and looks like a sync bug.
- Aliases and forwarders: recreate them now — a missing alias silently bounces customer mail after cutover.
- Catch-all: recreate only if you ran one before, and only after checking what it was collecting.
- Passwords: set them during creation so phones and Outlook need just one reconfiguration later.
If the website is moving too, finish the mailbox work first. The site and its mail are separate DNS records, and mixing both changes into one window makes any failure harder to diagnose — the zero-downtime site migration guide keeps the two tracks separate.
How do you copy old mail without losing folders or sent messages?
Copy mail over IMAP while both servers run, using imapsync from a terminal or drag-and-drop in Thunderbird for one or two mailboxes. Nothing in this step changes DNS, so a mistake costs time, not deliverability.
For a single mailbox, imapsync maps folders automatically:
imapsync --host1 mail.oldhost.com --user1 you@example.com --password1 OLDPASS \
--host2 mail.webji.in --user2 you@example.com --password2 NEWPASS --automapRun it a second time after it finishes; the delta pass picks up anything that arrived meanwhile. For cPanel-to-cPanel moves, the host's account transfer tool copies the whole mail directory and preserves folder prefixes exactly. The copy has worked when the folder lists match, message counts are within a few of each other, and a search for an old invoice finds it on the new server.
Folder mismatches almost always come from a prefix the tool did not map — INBOX.Sent versus Sent — which is why the Sent folder gets its own check before DNS changes. The POP3 vs IMAP comparison explains why only IMAP can do this bidirectional copy.
When do you switch the MX, SPF and DKIM records?
Switch DNS only after the copy verifies, and only after the MX TTL has spent a day at 300 seconds. A record still cached with a 24-hour TTL keeps delivering to the old server for a day after you edit it, which stretches a clean migration into a week of split mail.
- Set the TTL on the MX records to 300 seconds and save, a full day before the cutover.
- Copy the new host's exact MX hostnames and priorities — a wrong priority routes mail down the backup path first.
- Replace the SPF include with the one the new host publishes, and add the DKIM TXT record it generated. Keep exactly one SPF record.
- Confirm from two networks with
dig +short MX example.comanddig +short TXT example.com.
Leave DMARC unchanged unless the reporting address moves. If you have never published one, add a monitor-only policy in the weeks after the migration — never on cutover day, when you need a clean before-and-after picture. The business email setup guide covers each record's syntax.
How do you test the new mail flow, and when can you cancel the old host?
Test in both directions from an outside account, then keep the old host accepting mail for 72 hours before cancelling it. In Gmail, open the test message, choose "Show original" and read the authentication results: both spf=pass and dkim=pass should appear.
- Inbound: a message from outside lands in the inbox, not spam, with both checks passing in the headers.
- Outbound: the reply from the new mailbox arrives with the right display name and signature.
- Clients: phone, desktop and webmail all send through the new SMTP hostname.
- Wind-down: after 72 hours, run the final delta sync, export a backup of the new mailboxes, and only then cancel the old account — the last copy must exist before anything is deleted.
How does moving cPanel mail to Google Workspace or Microsoft 365 differ?
Both platforms import cPanel mail over IMAP, both copy mail only, and both still need you to make the MX switch yourself. Contacts, calendars and tasks require a separate export, so plan them before the cutover rather than after it.
Google Workspace uses the Admin console data import tool: connect the source account over IMAP, map each address to a Workspace user, and start the import. Larger organisations upload a CSV instead — one import covers up to 1,000 users, and a delta import picks up mail that arrived afterwards. Microsoft 365 runs an IMAP migration from the Exchange admin centre and requires each destination mailbox to exist before the batch starts; mail that reaches the old address after the migration window is not copied.
The sequence on this page still applies to both: mailboxes first, copy second, DNS last. The console changes; the order does not. WebJi® publishes Google Workspace and Microsoft 365 mailbox plans if the destination is either suite.
What usually goes wrong after a mail cutover?
Four failures generate most post-migration support tickets: bounces, missing old mail, spam-foldered mail and duplicates. Each has one cause and one fix.
| Symptom | Cause | Fix |
|---|---|---|
| New mail bounces | MX points at a server where the mailbox does not exist | Create the mailbox, or roll MX back to the old host |
| Old mail missing | Sync skipped a folder prefix or stopped early | Re-run the sync with folder mapping and compare counts |
| Mail lands in spam | SPF or DKIM still describes the old server | Publish the new SPF include and DKIM record |
| Messages arrive twice | A forwarder on the old host still copies to the new one | Remove the forwarder after the final sync |
One case only looks like a failure: mail delivered to the old server during propagation. That is expected, which is exactly why the old host stays online for 72 hours and receives a last sync. If deliverability problems persist after the records settle, the blacklist check guide is the next diagnostic step.
Can WebJi® run the email migration for you?
Yes — WebJi® moves mailboxes, aliases and stored mail between cPanel accounts as part of its migration service, free subject to terms and approval. Send the domain, the mailbox list and the current host to support@webji.services and the team schedules the copy; support replies in Hindi and English 24/7 with an average first reply under 60 minutes. If the domain itself is moving, start with a domain transfer so the whole DNS zone is managed in one place.
Destination mailboxes on WebJi® business email hosting start at ₹2,520 a year for five 5 GB mailboxes (₹504 per mailbox) before 18% GST, with the 10 GB tier at ₹4,200 a year for five mailboxes; checkout confirms current charges.
Frequently asked questions
Will I lose old emails when switching email hosts?
No, provided the IMAP sync completes and the old server stays online until the new one holds everything. Compare folder counts, run a second sync before the MX change, and keep the old host accepting mail for 72 hours afterwards so late arrivals are copied rather than lost.
How long does an email migration take?
A handful of mailboxes sync in a few hours, and the MX switch propagates within the TTL you set — commonly five minutes after a day at 300 seconds. Very large archives take proportionally longer to copy over IMAP, so run the first sync days before the planned cutover, not the night before.
Can I migrate email with zero downtime?
Effectively yes: with mailboxes created first, a current sync and a short TTL, no mail bounces at any point. During propagation some senders still reach the old server, which is why it must keep running and accepting mail until the final delta sync closes the gap.
Do I need to change SPF and DKIM when only moving hosts?
Yes. SPF and DKIM name the servers allowed to send for your domain, so they must describe the new host from cutover onward. Publish the new SPF include and the new DKIM TXT record in the same change window as the MX records, and keep a single SPF record — two conflicting ones fail the check outright.
What is the difference between IMAP sync and a cPanel transfer for mail?
IMAP sync copies message by message and works between any two standards-compliant servers, preserving folders, flags and read states. A cPanel account transfer copies the underlying mail directories wholesale, which is faster and keeps folder prefixes exact, but both accounts must be on cPanel for it to apply.
Last editorial update: 15 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.