Business email · Practical guide
How to migrate company email without losing messages
Email migration includes historical messages, inbound routing, outbound identity and user devices. Treat those as four separate acceptance checks.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Define what must survive the move
Create a mailbox inventory: addresses, aliases, forwards, shared boxes, retention requirements and account owners. Record folder counts and expected special folders (Sent, Drafts, Archive, Spam). A mailbox copy is incomplete if it imports Inbox but loses history or stores the imported Sent folder under an unexpected label.
Confirm what can be imported. IMAP typically handles message folders; contacts, calendar data and application-specific labels may need separate exports. If the source supports OAuth, prefer provider-approved authorization over sharing credentials or creating long-lived passwords for automation.
Verification checklist
- Count source messages by folder and owner
- Export contacts and calendars separately where needed
- Keep a reversible backup and record the cutover window
Provision destination before changing MX
Create the destination mailboxes, aliases and access policies first. Test login, sending, saving a sent copy, attachment download and password recovery. Install DKIM, SPF and DMARC records as instructed by the new provider without erasing currently necessary sending configurations.
Run an initial historical import while the old system is still active. Verify sample messages from different years, senders and folders. Some migrations require a second incremental sync near cutover to capture messages that arrived after the first copy.
Switch routing once both sides are ready
Update MX only after the destination has demonstrated successful inbound delivery. During DNS caching, some senders may still deliver to the previous MX. Keep the old mailbox accessible long enough to reconcile both systems and run a final import where supported.
Test new messages from multiple external domains, not only from a mailbox hosted on the same platform. Verify inbound routing, outbound DKIM and replies from smartphones and desktops. A transfer that looks successful in one browser can still leave a mail client pointed at an old SMTP server.
Verification checklist
- Verify messages arriving on both sides during propagation
- Reconcile folder counts and representative attachments
- Update clients, signatures, recovery channels and automated integrations
Close the migration deliberately
Do not cancel the previous provider on the day MX changes. Agree on a verification window based on your risk and retention requirements. Export any last messages, preserve records needed for audit, and remove obsolete DNS only after sending tests confirm no legitimate sender relies on them.
In the handover report, state the import method, any folders not migrated, the source and destination counts and the timestamp of the final sync. That makes it possible to distinguish a data-copy issue from an email-delivery issue later.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
Review OlaCheap business email service →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.