Office 365 Migration Cost: The Real Total in 2026

You're putting an Office 365 migration budget in front of a CFO and the number they want is "all-in." Not the tool license. Not the per-mailbox MSP rate. The whole thing — licenses, labor, comms, training, the support tail, the contingency. This post breaks the M365 migration budget into the line items it actually has, the 2026 reference numbers behind each, and what the total comes out to for projects of 25, 100, 500, and 2,000 mailboxes.

What's actually in the budget#

An honest M365 migration budget has nine line items. Six of them are reliable. Three are the ones that blow projects up.

1. M365 destination licenses (and any parallel-running source licenses).
2. Migration tool licensing.
3. Discovery and planning labor.
4. Configuration and provisioning labor.
5. Migration delivery labor (the actual move).
6. Cutover labor, often at weekend premiums.
7. Comms and training.
8. Post-cutover support window.
9. Contingency.

Skip any of the last three and your project will look cheap on paper and cost more in practice. We'll walk each one in turn, then build the totals.

Microsoft 365 license cost during migration#

The M365 license itself is the easiest line item to forget when you're focused on the migration mechanics, and the one that hits a CFO hardest because it recurs.

2026 list prices for the most common SKUs (USD, per user per month):

• M365 Business Basic: $7.20.
• M365 Business Standard: $12.50.
• M365 Business Premium: $22.00.
• M365 E3: $36.00.
• M365 E5: $57.00.
• Exchange Online Plan 1: $4.00.
• Exchange Online Plan 2: $8.00.

For migration budgeting, the question isn't only what the steady-state license costs — it's how long you run both source and destination licenses in parallel.

Most migrations require at least one full billing month of overlap. You provision destination tenants 2 to 4 weeks before cutover, you don't decommission source licenses for 1 to 2 weeks after, and the billing cycles rarely line up. Budget 4 to 6 weeks of dual licensing.

For 100 users on M365 Business Standard, that's roughly $1,250 to $1,875 of overlap cost. For 2,000 users on E3, it's $72,000 to $108,000. Big enough to matter.

Migration tool licensing#

Detailed breakdowns of tool pricing are in the per-mailbox cost guide and the BitTitan alternatives breakdown. For budget purposes, use these planning numbers:

• SaaS per-mailbox license (BitTitan, CodeTwo, SkyKick, Cloudiway, others): $8 to $25 per mailbox depending on volume.
• Desktop or self-hosted tooling: flat fee, typically $300 to $2,000 per license, amortised across all mailboxes in the project.
• Microsoft-native: zero license cost; absorbed in M365 licensing.

For an all-in budget, assume $12 per mailbox as a central planning number unless you have a specific vendor quote.

Discovery and planning labor#

Before the move, the work that protects the rest of the budget:

• Source environment inventory (mailboxes, sizes, public folders, shared mailboxes, distribution lists, mail-enabled apps).
• Destination tenant setup (domains, DNS, identity, security baselines).
• Hybrid configuration if relevant.
• Cutover plan, rollback plan, communication plan.

Realistic hours by project size:

• 25 mailboxes: 8 to 16 hours.
• 100 mailboxes: 16 to 32 hours.
• 500 mailboxes: 40 to 80 hours.
• 2,000 mailboxes: 100 to 200 hours.

At a blended rate of $150 to $200 per hour (MSP labor, US/UK rates), this is the line item where bigger projects benefit from economies of scale — but only if you do discovery properly. Skipping it doesn't save time; it converts discovery work into mid-project firefighting at a worse hourly rate.

Configuration and provisioning labor#

Standing up the destination tenant, provisioning users, configuring conditional access and MFA, setting up DKIM and DMARC, mapping shared mailboxes and distribution lists.

• 25 mailboxes: 8 to 16 hours.
• 100 mailboxes: 24 to 48 hours.
• 500 mailboxes: 60 to 120 hours.
• 2,000 mailboxes: 150 to 300 hours.

This scales sub-linearly with mailbox count because most of the configuration is per-tenant, not per-user. The biggest variable is how many existing groups and shared mailboxes need to be carefully reconstructed in the destination.

Migration delivery labor#

Operating the migration tool, watching for errors, retrying failed batches, communicating progress.

• 25 mailboxes: 12 to 24 hours.
• 100 mailboxes: 40 to 80 hours.
• 500 mailboxes: 120 to 240 hours.
• 2,000 mailboxes: 300 to 600 hours.

Delivery labor is more linear with mailbox count than the upstream phases. The variance is driven by mailbox size, item count, and source authentication quirks. Mailboxes with hundreds of thousands of items, deep folder nesting, or basic-auth-only sources eat hours.

Cutover labor and weekend premiums#

The actual moment of switching DNS and finalising the move. Usually a Friday night through Monday morning event.

• 25 mailboxes: 6 to 12 hours, single engineer.
• 100 mailboxes: 12 to 24 hours, one or two engineers.
• 500 mailboxes: 24 to 48 hours, two to four engineers.
• 2,000 mailboxes: 60 to 120 hours, four to eight engineers across a longer window.

Weekend premium: 25 to 50 percent over standard rate. Bake this into the line item explicitly so the CFO doesn't see a surprise overtime bill.

Comms and training#

The line item most internal projects underspend and most MSPs price as a flat fee:

• Pre-migration user comms (3 emails, FAQ, manager brief).
• A 20 to 30 minute recorded walkthrough of the new environment.
• A live Q&A or office-hours session in the week after cutover.
• IT champion enablement so the helpdesk can answer day-two questions.

Cost ranges:

• 25 mailboxes: $500 to $1,200.
• 100 mailboxes: $1,000 to $2,500.
• 500 mailboxes: $2,500 to $6,000.
• 2,000 mailboxes: $6,000 to $15,000.

These look like big numbers next to small per-mailbox costs. They are the single highest ROI line item in the budget because every hour you put into comms saves three hours of helpdesk traffic in week one.

Post-cutover support window#

One calendar week minimum. Realistic engineering and helpdesk hours:

• 25 mailboxes: 4 to 8 hours.
• 100 mailboxes: 12 to 20 hours.
• 500 mailboxes: 40 to 70 hours.
• 2,000 mailboxes: 120 to 220 hours.

The volume is dominated by Outlook profile re-creation, mobile device reauth (OAuth flows on iOS Mail and various Android clients), shared mailbox auto-mapping, calendar permission regressions, and send-as / send-on-behalf-of issues on shared mailboxes.

If your MSP rolls support into the per-mailbox fee, ask what's included and what triggers T&M. If you're running this internally, plan for at least one engineer at 50 percent capacity for the support week. The end-to-end migration timeline guide covers how the support phase fits into the overall project plan.

Contingency#

10 to 20 percent of the total. Lower end if you've done many migrations and the source is well-known; higher end if there are unknowns in scope (especially around archives, public folders, or compliance overlay).

Reference totals by project size#

These are 2026 all-in budget ranges for vanilla migration into M365. They exclude the M365 license itself going forward (that's a steady-state cost, not a migration cost). They include 4 to 6 weeks of source/destination license overlap, all migration tooling, all labor, comms, training, and a 15 percent contingency.

25 mailboxes — vanilla source to M365#

• Migration tool license: $300 to $625.
• Discovery and planning labor: $1,200 to $3,200.
• Configuration and provisioning: $1,200 to $3,200.
• Migration delivery: $1,800 to $4,800.
• Cutover (with weekend premium): $1,400 to $3,200.
• Comms and training: $500 to $1,200.
• Post-cutover support: $600 to $1,600.
• License overlap: $400 to $1,200.
• Contingency: ~15 percent.

All-in: $9,000 to $22,000. Per-mailbox equivalent: $360 to $880.

The per-mailbox math looks expensive because the project has a fixed-cost floor. Below 25 mailboxes, ask for a per-project minimum quote, not a per-mailbox one.

100 mailboxes — vanilla source to M365#

• Migration tool license: $1,200 to $2,500.
• Discovery and planning: $2,400 to $6,400.
• Configuration and provisioning: $3,600 to $9,600.
• Migration delivery: $6,000 to $16,000.
• Cutover: $2,400 to $5,600.
• Comms and training: $1,000 to $2,500.
• Post-cutover support: $1,800 to $4,000.
• License overlap: $1,500 to $3,000.
• Contingency: ~15 percent.

All-in: $23,000 to $58,000. Per-mailbox equivalent: $230 to $580.

This is the band where per-mailbox MSP pricing starts to make sense. The fixed-cost floor is amortising, the delivery line is significant but not overwhelming, and the support tail is manageable.

500 mailboxes — vanilla source to M365#

• Migration tool license: $5,000 to $11,000.
• Discovery and planning: $6,000 to $16,000.
• Configuration and provisioning: $9,000 to $24,000.
• Migration delivery: $18,000 to $48,000.
• Cutover: $4,800 to $10,800.
• Comms and training: $2,500 to $6,000.
• Post-cutover support: $6,000 to $14,000.
• License overlap: $8,000 to $15,000.
• Contingency: ~15 percent.

All-in: $70,000 to $170,000. Per-mailbox equivalent: $140 to $340.

At this scale, hybrid Exchange becomes a real architectural choice rather than an automatic no. The fixed cost of hybrid (AD sync, hybrid configuration wizard, certificates) is justifiable when amortised across 500 mailboxes if your source environment makes hybrid the cleaner path.

2,000 mailboxes — vanilla source to M365#

• Migration tool license: $16,000 to $40,000.
• Discovery and planning: $15,000 to $40,000.
• Configuration and provisioning: $22,500 to $60,000.
• Migration delivery: $45,000 to $120,000.
• Cutover: $12,000 to $30,000.
• Comms and training: $6,000 to $15,000.
• Post-cutover support: $18,000 to $44,000.
• License overlap: $36,000 to $72,000.
• Contingency: ~15 percent.

All-in: $210,000 to $480,000. Per-mailbox equivalent: $105 to $240.

At this scale, you should be running tiered project management, not a single project lead. The cutover is a multi-engineer, multi-shift operation. The comms and training programme is a real change-management workstream rather than a few emails.

For the operational structure of projects at this size, the complete email migration guide covers how the phases sequence; the Office 365 migration guide covers the M365-specific destination configuration in more depth.

What pushes the number up#

Six factors push you toward the high end of every range:

• Archive ingest. Mimecast, Proofpoint, Barracuda, Veritas Enterprise Vault. Each is essentially its own project.
• Public folders. Migration is non-trivial, throughput is low, and reorganisation usually happens at the same time.
• PST imports. 5 to 15 percent of PSTs need repair before ingest.
• Compliance overlay. Legal hold, eDiscovery, retention policies that need to translate from source to destination structure.
• Teams chat migration. Tenant-to-tenant moves often need Teams chat history alongside email; this is a distinct workstream.
• Multiple geographies. Coordinating cutover across 3+ time zones turns a single weekend into a phased rollout.

What can push the number down#

Three factors that materially reduce cost if you have them:

• Source authentication that supports modern auth / OAuth. Cuts delivery labor by 20 to 35 percent compared to basic-auth-only sources.
• Clean mailbox sizing. If 95 percent of mailboxes are under 25 GB, delivery is faster, more parallel, and less error-prone.
• Strong internal IT champion. A client-side IT lead who can drive user enablement and triage tier-1 tickets reduces post-cutover support spend significantly.

How to present the budget to a CFO#

Three things to do that change how the budget is received:

Show the line items, not the total only. A single big number invites cuts. Nine clear line items invite informed prioritisation.

Separate one-time from recurring. Migration is one-time. M365 licensing is recurring. Don't combine them, even though they're both M365-related cost.

Show a contingency line explicitly. Budgets without contingency get blown. Budgets with a labelled 15 percent contingency rarely need more than the contingency.

The CFO will respect the structure even when they push on the total. The per-mailbox cost guide has the cost-per-mailbox benchmarks you may need to defend the numbers against external comparisons.

A final note on what you're really buying#

The line items above are the budget. The value is something subtly different. You're buying a date — the day after cutover when people open their laptop and email works. The cost of getting that date right is the budget in this post. The cost of getting it wrong — productivity loss across the company, lost trust in IT, repeat migrations to undo data damage — is materially higher.

Spend the budget on the things that protect the date: discovery, comms, the support tail, and the contingency. Save where you reasonably can on tooling, but never at the cost of making the date wobble.