SRCCUTOVERDESTIndependent · No vendor bias · Updated Apr 2026
Workload · Exchange -> Microsoft 365

Exchange to Microsoft 365 migration cost, 2026

The most common workload migration of the past decade. Per-mailbox pricing, cutover vs staged vs hybrid migration paths, FastTrack scope, third-party tooling economics, and a 500-mailbox worked scenario with the full cost breakdown including PSTs and archives.

Exchange to Microsoft 365 migration is one of the highest-volume migration workloads across the enterprise IT estate. The technology is well-understood, the toolchain is mature, and Microsoft heavily funds the work via FastTrack. Yet enterprise Exchange migrations still routinely exceed budget. The reasons are predictable: PSTs, public folders, third-party archive systems, and regulated discovery requirements all add cost that is rarely modelled at the start. This page is the 2026 cost reference for Exchange to Microsoft 365 migration.

Three migration paths and their cost shapes

Microsoft supports three primary migration paths from on-premise Exchange to Microsoft 365. Each suits a different estate size and risk profile.

Exchange to Microsoft 365 migration paths

PathEstate sizeDurationPer-mailbox costNotes
CutoverUnder 150 mailboxes2 to 4 weeks$15 to $40Single-weekend cutover; high user disruption
Staged150 to 2,000 mailboxes6 to 16 weeks$25 to $75Batched migration; some user disruption per batch
Hybrid2,000+ mailboxes6 to 36 months$50 to $200Extended coexistence; zero user disruption
IMAPNon-Exchange source2 to 8 weeks$10 to $50Lower fidelity (no calendar, no folder permissions)
Cross-tenant (M365 to M365)Any size4 to 26 weeks$30 to $120Post-acquisition tenant consolidation

Per-mailbox cost decomposition

The headline per-mailbox cost obscures meaningful variation in what is included. For a mid-market staged migration of 500 mailboxes, the typical cost decomposition:

Per-mailbox cost decomposition, 500-mailbox staged migration

Line itemPer-mailbox costTotal (500 mailboxes)Notes
Planning and assessment$8$4,000Discovery, sizing, mail-flow design
Migration tooling (Microsoft native or BitTitan)$5 to $20$2,500 to $10,000Native is free; third-party adds capability
Mailbox replication labour (per batch)$15 to $30$7,500 to $15,000Partner-led, includes troubleshooting
End-user communication and training$5 to $15$2,500 to $7,500Briefing materials, helpdesk preparation
Cutover support and hypercare (2 weeks)$8 to $20$4,000 to $10,000Post-cutover support window
Identity and licence provisioning$3 to $8$1,500 to $4,000Entra ID synchronisation, M365 licence assignment
Per-mailbox total (excluding PSTs/archives)$45 to $100$22,500 to $50,000Standard mailbox migration
PST ingestion (if 10 GB avg per user)$20 to $60$10,000 to $30,000Network Upload or third-party
Archive migration (if Mimecast/EV)$30 to $120$15,000 to $60,000Most expensive line on regulated estates
All-in per mailbox$95 to $280$47,500 to $140,000Including PSTs and archives

FastTrack for Microsoft 365, scope and limits

FastTrack for Microsoft 365 is included at no additional charge for customers with 150 or more eligible M365 seats. Microsoft provides FastTrack engineering resources to deliver planning workshops, data migration for eligible source systems (Exchange, Lotus Notes, IBM Domino, Google Workspace), and adoption support. The data migration coverage is the most material element for cost modelling; FastTrack will move mailbox content from eligible sources at no additional cost.

FastTrack does not cover everything. Third-party email systems (Zimbra, Kerio, Mailfence) require partner-led migration. Archive systems are explicitly out of scope. Custom mail flow rules, transport rules, hybrid configurations beyond the default, and decommissioning of the source Exchange estate are partner activities. For most mid-enterprise migrations the practical pattern is FastTrack-funded data movement plus partner-led configuration, integration, and decommission, with the cost shifting from Microsoft-funded to customer-funded at the boundary.

The FastTrack value

For a 500-mailbox migration, FastTrack typically covers $15K to $40K of equivalent partner-led migration cost at zero cash cost to the customer. For a 5,000-mailbox migration, FastTrack value typically lands at $150K to $400K. This is real cost displaced from the migration programme onto Microsoft's investment in customer adoption.

The PST problem

Personal Storage Tables (PSTs) are the single most underestimated line item in Exchange migrations. PSTs are local files containing email exported from Exchange, typically stored on user devices, network shares, or USB drives. Mid-enterprise estates often have 5 to 50 TB of PSTs scattered across the environment, accumulated over a decade of mailbox quota workarounds.

Microsoft provides Network Upload as a free tool to ingest PSTs into Exchange Online. The mechanics: customers upload PSTs to a Microsoft-provided Azure Storage account, then run an import job to ingest the content into target mailboxes. The tool is free but the operational discipline is significant: PSTs must be discovered, collected from user devices, validated, mapped to target mailboxes, and ingested without disrupting end-user productivity.

Third-party tools (BitTitan MigrationWiz PST, Quadrotech PST Flight Deck, Code Two PST Manager) automate the PST discovery, collection, and ingestion process. Pricing is typically per-PST or per-GB; mid-enterprise estates typically pay $20K to $80K in third-party tooling for PST migration alone. The trade-off is operational simplicity: the tools handle the user-device discovery and collection without manual touch, which avoids the deskside support cost of manual PST collection.

Archive systems, the hidden cost iceberg

Customers with third-party email archive systems (Mimecast, Veritas Enterprise Vault, Proofpoint Archive, Smarsh) face the most complex and expensive part of the migration. The archive system contains years of email history, often required to be preserved for regulatory or eDiscovery reasons. Migrating the archive into Exchange Online (or to a dedicated archive in Microsoft 365 Compliance) requires both data movement and metadata preservation (custodian, retention, legal hold status).

Archive migration cost typically lands at $80 to $250 per mailbox depending on the archive system, the volume of archived content per user, and the retention/eDiscovery requirements. Tools specifically designed for archive migration (Quadrotech ArchiveShuttle, AvePoint Fly, TransVault) are usually required; the migration is rarely feasible with Microsoft's native tools alone. For regulated estates (financial services, healthcare, legal) the archive migration is frequently the largest single line item in the entire Exchange to M365 programme.

Worked 500-mailbox staged migration scenario

A representative cost build for a mid-market 500-mailbox Exchange to Microsoft 365 staged migration, with PSTs (estimated 8 TB total), legacy Mimecast archive (15 TB), and standard public folder migration. Partner-led with FastTrack support for core data movement.

Worked Exchange to M365 cost build, 500 mailboxes, 16 weeks

Cost lineLow estimateTypical estimateHigh estimate
Assessment and planning$12,000$24,000$50,000
Microsoft 365 licence provisioning (one-time setup)$3,000$8,000$18,000
Hybrid configuration and identity sync (Entra Connect)$15,000$32,000$70,000
Mailbox migration labour (5 batches of 100)$35,000$75,000$150,000
FastTrack value (Microsoft-funded)($20,000)($35,000)($60,000)
PST discovery and ingestion (8 TB)$20,000$50,000$110,000
Mimecast archive migration (15 TB, Quadrotech)$45,000$120,000$280,000
Public Folder migration$8,000$18,000$45,000
Mail flow rule migration and transport audit$5,000$12,000$30,000
End-user training and change management$10,000$25,000$60,000
Cutover support and hypercare (4 weeks)$15,000$35,000$80,000
Source Exchange decommission$8,000$18,000$40,000
Contingency at 15 percent$24,000$57,000$130,000
Net total estimate$180,000$439,000$1,003,000

The typical-column number, $439K for 500 mailboxes over 16 weeks, works out at roughly $880 per mailbox all-in. That number is dominated by the archive migration ($120K of $439K) and the PST ingestion ($50K of $439K). The core mailbox migration itself is only $40K of the total (mailbox labour minus FastTrack). The cost discipline for Exchange migration is almost always about scope: which archives genuinely need to migrate, which PSTs can be retired rather than ingested, which historical content can be discarded under updated retention policies.

How to reduce Exchange to M365 migration cost

  1. Discover PSTs before scoping. Most estates have 30 to 50 percent more PST volume than expected.
  2. Apply retention policies before migration. Discarding email above retention age reduces archive migration cost proportionally.
  3. Use FastTrack for the core mailbox migration. Microsoft's funding covers a meaningful portion of the work.
  4. Consider whether the third-party archive needs to migrate at all. Some regulated estates can maintain the source archive in read-only mode for retention while running live email on M365.
  5. Choose third-party tooling deliberately. The right tool for the source system saves more than its cost; the wrong tool inflates cost without adding capability.
  6. Plan the cutover for low-traffic periods. End-user disruption during migration is the second largest hidden cost after archives, expressed as helpdesk volume and productivity loss.
  7. Decommission the source Exchange estate promptly. Every month of dual-running costs licensing, hardware support, and operational labour.

Exchange to Microsoft 365 migration is a well-understood workload with mature tooling and generous Microsoft funding. The cost overruns happen on the long tail: PSTs, archives, public folders, and the decommission discipline. The teams that succeed at Exchange migration cost are the ones that discover the long tail at assessment, apply retention policy aggressively to reduce migration volume, and treat the source decommission as part of the programme rather than a follow-up activity.

Q&A

Frequently asked

Q. How much does it cost to migrate Exchange to Microsoft 365?

A. Per-mailbox migration cost typically lands at $20 to $80 for a 500-mailbox cutover migration, $40 to $150 for a 500-mailbox hybrid migration with coexistence, and $80 to $250 for a regulated or complex estate (financial services, healthcare) with full eDiscovery and archive migration. The Microsoft 365 subscription cost itself starts at $6 per user per month for Business Basic and runs to $35+ for E5; this is the steady-state cost after migration, not the migration cost itself.

Q. Should I use cutover, staged, or hybrid migration?

A. Cutover migration moves all mailboxes in a single weekend; suitable for estates under 150 mailboxes. Staged migration moves mailboxes in batches over several weeks; suitable for estates of 150 to 2,000 mailboxes. Hybrid migration maintains coexistence between on-premise Exchange and M365 for an extended period; required for estates above 2,000 mailboxes or where regulatory constraints require gradual transition. Hybrid is more expensive to operate during the parallel period (typically 6 to 18 months) but produces zero user disruption.

Q. Is FastTrack for Microsoft 365 free?

A. FastTrack for Microsoft 365 is included at no additional cost for customers with 150+ M365 seats. It covers planning workshops, eligible migration data movement for mailbox content, OneDrive content, and SharePoint sites, and adoption support. FastTrack does not cover third-party migration tooling, custom integration work, or non-Microsoft data sources. Mid-market customers typically use FastTrack for the bulk of the migration and a partner for the complex tail (PSTs, archives, third-party email systems).

Q. What about Public Folders, PSTs, and archives?

A. Public Folders migrate via the Public Folder migration tool to either Modern Public Folders in Exchange Online or to shared mailboxes. PSTs are typically the most expensive line in any Exchange migration; mid-enterprise estates often have 5 to 50 TB of PST files scattered across user devices. Tools like Microsoft's Network Upload (free) or third-party tools (BitTitan, Quadrotech, AvePoint) handle bulk PST ingestion. Archive mailboxes from Exchange Online Archiving or third-party archive systems (Mimecast, Proofpoint, Veritas Enterprise Vault) require dedicated migration approaches and are typically the most complex and expensive part of the migration.

Q. How long does an Exchange to M365 migration take?

A. Cutover migrations complete in 2 to 4 weeks of elapsed time. Staged migrations of 500 to 2,000 mailboxes take 6 to 16 weeks. Hybrid migrations of 5,000+ mailboxes typically take 12 to 36 months from kickoff to full Exchange decommission. Most large enterprise migrations are timeline-bound by the rate of mailbox throughput (typical 4 to 20 GB per mailbox per hour over a hybrid connection) and by end-user readiness rather than by technology.

Q. What is the cost of third-party tools versus Microsoft's native tools?

A. Microsoft's native tools (Exchange Hybrid Configuration Wizard, the MRS mailbox replication service, the Public Folder migration tool, Network Upload for PSTs) are included with the M365 subscription. Third-party tools (BitTitan MigrationWiz, Quadrotech ArchiveShuttle, AvePoint Fly) typically charge per-mailbox or per-GB and add $10 to $60 per mailbox to the migration cost. The third-party tools earn their keep on complex migrations with non-Exchange sources, multiple coexistence requirements, or specialised archive systems.

Related

Read next

Updated 2 May 2026