HomeServicesManaged IT ServicesClaude DeploymentInsightsAboutContact
Exchange Server to Exchange Online

Exchange Online Migration Services

Move mailboxes from on-premises Exchange Server to Exchange Online without breaking the printers, line-of-business apps, shared mailboxes, and delegates that depend on it.

MethodCutover or hybrid chosen from your size, timeline, and identity setup.
Mail flowSMTP relay, connectors, and app senders inventoried before cutover.
MailboxesUser, shared, resource, archive, and delegate moves sequenced together.
ExitA plan for the last Exchange server, not just the mailboxes.

Migration workstreams

The mailbox move is the easy part

Exchange Server usually carries years of hidden dependencies. We find them first, so cutover is a planned event rather than a scramble.

Discovery

Exchange assessment

Versions, mailbox sizes, archives, public folders, transport rules, connectors, certificates, journaling, and anything that relays through Exchange.

Design

Cutover vs hybrid

A cutover migration for smaller, simpler environments or a hybrid deployment when you need coexistence, directory sync, or a longer move window.

Mail flow

Relay & connectors

Scanners, ERP systems, monitoring tools, and web apps that send mail are re-pointed to supported Exchange Online sending options.

Mailboxes

Batches & permissions

Users, delegates, and shared mailboxes they rely on are moved together so calendar delegation and Send As do not break mid-project.

Cutover

DNS & clients

MX, Autodiscover, SPF, DKIM, and DMARC changes, Outlook profile behavior, and mobile device reconnection planned and tested.

Closeout

Decommissioning

A supported plan for the last Exchange server, recipient management in hybrid, and safe removal of on-premises dependencies.

EXO

Built for environments that cannot go dark

Email is the system everyone notices when it breaks. We plan migration batches, communication, and rollback so the business sees a quiet cutover.

Plan the Exchange Move
  • ✓Exchange Server version and support-status review, including Exchange SE planning
  • ✓Cutover or hybrid recommendation with the trade-offs written down
  • ✓SMTP relay and application sender inventory with replacement options
  • ✓Delegate, shared mailbox, and resource mailbox batch planning
  • ✓Public folder migration or replacement with shared mailboxes or Microsoft 365 Groups
  • ✓Post-migration validation, EWS and legacy-auth app checks, and decommission runbook

Where projects go wrong

What usually breaks in an Exchange migration

These are the failure points we look for in every Exchange Server assessment.

Relay

Devices that send mail

Multifunction printers, ERP systems, and scripts that relay through on-premises Exchange stop sending if nobody inventories them before the server is removed.

Delegates

Split permissions

Moving an executive without their assistant, or a user without the shared mailbox they work from, causes calendar and Send As problems during coexistence.

Apps

Legacy protocols

Applications that use Exchange Web Services or basic authentication need to be checked against Exchange Online, which no longer supports some older access methods.

Public folders

Forgotten data

Public folders often hold years of shared mail and calendars. They need a decision: migrate, replace with shared mailboxes or Groups, or archive.

DNS

Autodiscover & certificates

Stale Autodiscover records, expired certificates, and split-brain DNS cause Outlook prompts and connection failures after cutover.

Last server

Premature removal

Turning off the last Exchange server in a hybrid environment without a supported recipient-management plan can leave attributes unmanageable.

Proof & guides

See how we approach it

An anonymized client story plus the planning guides we wrote from hands-on project work.

Case study

Exchange Online migration

An anonymized move off Exchange Server where the app-relay inventory prevented a Monday-morning outage.

Read more →
Guide

Exchange Server to Exchange Online

Cutover, staged, and hybrid paths compared, with planning steps and common pitfalls.

Read more →
Guide

Exchange Online EWS retirement

What the Exchange Web Services retirement means for apps and integrations.

Read more →

FAQ

Exchange migration questions

Cutover works well for smaller environments that can move everyone at once. Hybrid fits larger organizations, phased moves, directory-synced identities, or cases where some mailboxes must stay on-premises for a while. We recommend one after reviewing your environment.
Often, yes, but it must be planned. In hybrid environments that use directory sync, recipient attributes still need a supported management method. We document that decision before anything is shut down.
We inventory every device and application that relays mail, then move each one to a supported Exchange Online sending option such as authenticated SMTP, direct send, or a connector.
With correct Autodiscover and a planned cutover, most Outlook clients reconnect automatically. Some mobile devices and older clients need a new profile, which we schedule and support.
Exchange Server 2016 and 2019 have reached end of support. The realistic paths are moving to Exchange Online or upgrading to Exchange Server Subscription Edition. We help you choose based on compliance, cost, and dependencies.

Still running Exchange Server?

Get a clear path off on-premises Exchange

We will assess your Exchange environment, choose the right migration method, and hand you a cutover plan you can trust.

Book an Exchange Migration CallAll Migration Services