Get off the mail server without losing a message

The maintenance burden is the other half. Cumulative updates that must be applied in sequence, certificates that expire and take mail flow down with them, database growth and log truncation, backup that has to be application-aware, and a service where every problem is company-wide by definition. For a business with thirty mailboxes, that is a lot of specialist attention for something Microsoft will run for a few dollars per user.

Planning the migration

A good migration is mostly discovery. We inventory every mailbox including the ones nobody uses, measure sizes, catalog public folders and who actually opens them, find every shared and resource mailbox, and list every system that sends mail through the server, the copier, the accounting package, the alarm monitoring, the line-of-business application with SMTP settings entered in 2017 by someone who has left.

That last category causes most post-migration incidents. Mail simply stops arriving from a system nobody remembered, usually a week later when somebody notices the statements never went out. We find those before cutover by watching what actually connects to the server.

Hybrid, cutover and public folders

For small mailbox counts, a cutover migration is often simplest: move everything in one weekend, change DNS, reconfigure clients. For larger environments or where coexistence is needed, hybrid lets on-premises and cloud mailboxes work together with shared calendars and a single address list while you migrate in batches. Hybrid adds complexity but removes the big-bang risk, and we choose based on size and tolerance rather than habit.

Public folders are the classic complication. They are usually old, often huge, and frequently contain data nobody has opened in years alongside a handful of items that are business critical. We audit usage, migrate what matters to shared mailboxes or SharePoint where that fits better, and move genuine public folder content properly rather than dragging a decade of unused hierarchy into the cloud.

Mail flow rules, connectors, journaling and transport settings all need to move deliberately. So do the small things that generate support calls afterward: mobile device reconfiguration, Outlook profile rebuilds, autodiscover records, cached address book entries pointing at old addresses, and the delegate permissions that silently do not carry over. We work through a checklist rather than a memory, and we keep the old environment intact until the new one has been proven for a couple of weeks.

After the move we complete the security work that on-premises Exchange made awkward: MFA, conditional access, modern authentication and proper filtering. Those details live on our business email page, our Microsoft 365 page and at email.orcait.io. The wider migration method is on data migration.