Migrating Business Email Without Losing Messages

Move business email with a plan for messages, recipients, DNS and the final synchronization. Protect the old service until you have checked real inbound and outbound delivery.

Start here: protect the only copy

No migration method guarantees that every item will move without planning and verification. First identify where mail actually lives: server folders, local PST archives, POP-only computers, shared mailboxes and other devices.

Inventory users, aliases, groups, shared addresses, calendars, contacts, rules, archives and retention requirements. Confirm who is authorized to access and transfer each mailbox. Do not collect users’ passwords in a spreadsheet.

1. Choose a supported method

Microsoft 365 supports different migration paths depending on the source and organization. A supported IMAP migration transfers mail folders, but does not transfer contacts, calendars or tasks. Those require a separate supported plan.

Review source/destination limits, item failures and licensing before selecting a tool. Exchange-to-Exchange scenarios can need a different method from a small IMAP move. Test a representative pilot mailbox rather than assuming one successful folder proves the whole organization is ready.

2. Prepare recipients before changing MX

Create the intended destination mailboxes and all required aliases and shared addresses. Verify access and available storage. Add the domain and complete ownership verification without prematurely switching mail delivery.

Preserve the old provider and an independent recovery copy where supported. Keep transfer credentials or migration endpoints restricted and follow your organization’s security and retention requirements. Do not disable MFA or compliance controls as a shortcut.

3. Synchronize and inspect

Run the supported initial migration while the source remains available. Review migration reports for skipped, oversized or failed items. Compare representative folder counts, date ranges, attachments and important historical messages.

Counts can differ because of folder mapping or filtering; investigate differences rather than claiming success from a green summary. Confirm calendars and contacts through their separate migration process.

4. Switch routing and finish the overlap

At the approved window, change MX and related service records to the destination. Preserve website DNS unless it is part of the same reviewed plan. Configure SPF, DKIM and DMARC for the legitimate sending systems without duplicating SPF records.

Cached MX answers can still direct some senders to the old provider. Keep it available and perform the migration method’s final synchronization before completing or removing the migration relationship. Reconfigure clients using the supported sign-in method.

5. Test business use, not just login

• Send externally to each important address and reply from the new system.
• Check aliases, shared-mailbox permissions and mobile/desktop clients.
• Test website forms, scanners and business applications through their approved sending method.
• Verify historical mail, attachments, contacts and calendars against the inventory.
• Review delivery errors, authentication results and outstanding migration failures.

A missing message may be in the old mailbox, a local archive, a skipped-item report or Junk. Preserve evidence before moving or deleting anything.

Rollback and retirement

If routing must revert, account for messages already delivered to the destination. Do not overwrite new mail with an older backup or leave users sending from two disconnected copies.

Retire the former service only after the owner accepts verification, retention and recovery arrangements. Remove temporary migration access through the supported administrative process, then retain the final reports privately.

Official references

• Microsoft: Mailbox Migration Options
• Microsoft: IMAP Mailbox Migration
• Microsoft: Add a Domain

Documentation checked 2026-10-18. Examples use reserved names and addresses; replace placeholders only for systems you are authorized to manage. Interfaces and included features depend on your provider and account.