Migrate from Exchange or IMAP to Microsoft 365 Without Losing Mail
A migration playbook covering inventory, cutover versus staged moves, PST side paths, coexistence, and verification so folders and history survive the switch.
- Inventory mailbox sizes, aliases, and forwarding before you choose cutover or staged.
- IMAP moves mail; it does not magically recreate calendars, rights, or public folders.
- Keep a source snapshot (backup or PST) until item counts match in Exchange Online.
- DNS cutover is a communication event — users should know when Outlook profiles change.
Choose the migration story that matches the source
Exchange Server (especially supported hybrid/native moves) preserves more mailbox structure than a generic IMAP pull. IMAP is common for hosted mail, cPanel, and miscellaneous providers. Do not use an IMAP playbook for a healthy Exchange org just because a blog said it was “simpler.”
Discovery checklist
See Office 365 Email Backup
Reliable mailbox backup and recovery for Microsoft 365 environments.
Learn more- Mailbox count, largest mailboxes, and shared mailboxes
- Aliases, delegates, and resource calendars
- Public folders or shared IMAP folders
- Third-party devices that send mail (MFPs, applications)
- Bandwidth between source and Microsoft 365
Cutover vs staged vs hybrid
- Cutover: small orgs, short coexistence, all MX at once
- Staged: batches of users, longer calendar, more communication
- Hybrid: Exchange coexistence when you need a bridge
IMAP projects are usually staged: migrate mail, switch clients, then MX. Calendar and contacts may need a second tool or a PST side path.
The no-data-loss pattern
- Snapshot or export critical mailboxes (backup or PST)
- Pilot two typical users and one “messy” power user
- Compare folder trees and item counts
- Fix mapping issues (Sent, Trash, custom folders) before the rest of the company
- Move MX only when pilots are signed off
- Keep source online read-only for a defined rollback window
PST as a safety valve
When IMAP cannot carry a folder or a user has a local archive, import the PST into the Microsoft 365 mailbox after the primary mail sync. That is a controlled exception, not the whole program. See how to import PST files.
After MX moves
Update printers and applications. Watch NDRs for 48 hours. Then enable an independent Office 365 mailbox backup so the new tenant is not a single point of failure. Broader planning lives in Office 365 migration best practices.
Recommended next step
Import PST to Office 365
Migrate PST archives into Microsoft 365 with audit-ready controls.
