HomeServicesManaged IT ServicesAI DeploymentAccredOneInsightsAnswersAboutFree Consultation
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.

What an Exchange Online migration with Accred includes

Accred Consulting moves mailboxes from on-premises Exchange Server to Exchange Online and plans the exit from the last server. We inventory mailboxes, archives, public folders, connectors and every app or device that sends mail through Exchange, recommend cutover or hybrid in writing, move mailboxes in batches with delegates together, re-point mail flow and DNS, and document a supported decommission path. Our fixed-scope package typically runs 4 to 10 weeks, depending on mailbox count and relay dependencies.

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.

Who this is for

  • You still run Exchange Server 2016 or 2019, which reached end of support on October 14, 2025.
  • Patching, certificate renewals and cumulative updates take up IT weekends.
  • A partial move years ago left a hybrid setup nobody fully understands.
  • Scanners, ERP systems, monitoring tools or scripts relay mail through the Exchange server.
  • You want to retire on-premises Exchange, or keep only what is still justified.

What is in scope, and what is not

Usually in scope

  • Inventory of user, shared and resource mailboxes, archives, public folders, transport rules, connectors, journaling and certificates
  • A relay inventory: every app, scanner and device that sends mail through Exchange, with a replacement option for each
  • Cutover or hybrid recommendation with the trade-offs written down
  • Target readiness: licensing, directory sync, MFA and connectors
  • Mailbox moves in planned batches, with delegates and shared mailboxes kept together
  • MX, Autodiscover, SPF, DKIM and DMARC changes and Outlook and mobile reconnection
  • A decommission checklist for the last Exchange server

Handled separately or agreed during discovery

  • Rewriting custom applications that use Exchange Web Services. We find them during discovery; the code work is its own project. See EWS retirement remediation.
  • Upgrading servers you keep on-premises to Exchange Server Subscription Edition.
  • Replacing third-party archiving or journaling products.
  • Replacing printers or devices that cannot send mail by any supported method.

Cutover or hybrid: how we choose

QuestionCutover migrationHybrid deployment
SizeSmall environments; Microsoft caps cutover at 2,000 mailboxes and recommends it for far fewerAny size, including large or phased moves
Move windowEveryone moves togetherBatches over weeks, with mailboxes in both places meanwhile
IdentitiesCloud accounts, no directory sync neededDirectory-synced identities from on-premises Active Directory
CoexistenceNone after the switchShared free/busy and mail routing between on-premises and cloud
After the moveExchange server can usually be removedA supported recipient-management method must be in place before the last server goes

How the project runs

  1. Assessment. Versions, mailbox sizes, archives, public folders, connectors, certificates and relays.
  2. Method decision. Cutover or hybrid, written down with the reasons.
  3. Relay redesign first. Apps and devices are moved to authenticated SMTP, direct send or a connector before the first batch, not after.
  4. Target readiness. Licensing, directory sync, MFA and Conditional Access checked.
  5. Pilot batch. A small group that includes delegates and shared mailbox users.
  6. Production batches. Planned moves with user notices and a known support channel.
  7. Mail flow cutover. MX and Autodiscover changes, then validation of Outlook, mobile and every relay sender.
  8. Decommission. What still needs a server, for how long, and the checklist to remove the rest.

More risks we plan for

RiskHow we handle it
Large mailboxes and archives slow batchesSizes measured in discovery and the largest mailboxes scheduled early
Old clients use basic authentication, which Exchange Online no longer acceptsClients and apps checked for modern authentication before cutover
Hybrid certificate expires mid-projectRenewal date and owner recorded during assessment
DNS changes take longer than expectedRecord TTLs lowered ahead of cutover

What we need from you

  • Exchange and Active Directory admin access, plus Microsoft 365 admin access
  • DNS access for your mail domains
  • Any list you have of apps and devices that send mail, and who owns them
  • A network or firewall contact if hybrid is used
  • Pilot users, including an assistant who manages someone else's calendar
  • Maintenance windows for cutover

How long it takes

Our Exchange Server exit package lists a typical duration of 4 to 10 weeks depending on mailbox count and relay dependencies, set after discovery.

Proof from similar projects

FAQ

Exchange migration questions

An Exchange Server to Exchange Online migration starts from $6,500 for up to 50 mailboxes. The final fixed price is set in a written proposal after a free scoping call. Mailbox count and size, public folders, the number of apps and devices that relay mail, and whether hybrid is needed drive the price. Open-ended work is billed at $125 per hour, or $115 per hour from a prepaid 50-hour block.
Our Exchange Server exit package typically runs 4 to 10 weeks depending on mailbox count and relay dependencies. The schedule is set after discovery.
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.
If they connect to Exchange Online, yes. Microsoft began disabling EWS in Exchange Online in October 2026 and plans to turn it off fully in April 2027. Apps need a vendor update or a move to Microsoft Graph. EWS on on-premises Exchange Server is not affected by this retirement.

Starting prices

  • Exchange Server to Exchange OnlineFrom $6,500Up to 50 mailboxes

Starting prices in US dollars for a typical small scope. The final price is set in a written proposal after a free scoping call.

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.