Exchange Migration Services and Tools: The Real Cost IT Directors Need to Budget For

This article is sponsored by ShareGate.

You quoted finance $35,000. Then you found 400 archive mailboxes you hadn’t scoped, a handful of Litigation Holds, and a coexistence window that stretched from two weeks to six. Now you’re back in front of leadership explaining why the number moved. Most Exchange migrations don’t go over budget because the tools are expensive but because they go over budget because the project is under-scoped from the start.

Exchange tenant-to-tenant migration pricing looks simple on paper. Per-mailbox fees, clean line items, predictable math. The reality is messier, and most of the variance comes from things vendors don’t put in the Statement of Work (SoW). If you’re running anything beyond a small tenant, per-mailbox pricing is usually a trap. Your real costs will come from discovery, rework, and coexistence, not licensing.

This piece walks through where Exchange migration money actually goes, the scope items that get missed during planning, and how to build a cost model that survives a CFO review.

Why does Exchange Online migration cost more than the tool license?

Vendor quotes for tenant-to-tenant Exchange migration look clean: per-mailbox fees, predictable line items, easy math. The actual project cost lands well above that number. The 2025 DevOps Migration Index found platform migrations run an average 18% over budget, with the typical project losing $315K to overruns. Internal IT time, rework, archive scope, and post-migration support are where most of that variance lives, and it rarely shows up on the SOW.

IT Directors who budget only for the migration license miss most of what the project will actually cost. The license fee is the easy part. Everything else takes longer to surface and hits harder when it does.

Three categories drive most of the overrun:

• Internal IT hours spent planning, executing, validating, and troubleshooting. Often the largest single line item, almost always underestimated.
• Extended coexistence. When migrations run in waves, both source and target tenants stay operational, doubling the support and admin burden until cutover finishes.
• Post-migration tail. Helpdesk volume spikes for weeks after cutover. Folders disappear, delegates lose access, recurring meetings duplicate or break.

Finance wants a number you can defend. The rest of this piece breaks down what to put behind it.

Five sources of mailbox migration rework that blow up Exchange migration budgets

Rework is where budgets quietly die. Something breaks mid-migration, you re-run a batch, re-investigate a failure, or re-explain a delay to leadership. Every rework hour is an hour you already budgeted somewhere else.

Most Exchange Online migration rework traces back to five sources. Catching them during assessment costs less than catching them during cutover.

1. Identity mismatches: the fastest way to stall a migration mid-cutover

Mismatched identities between source and target tenants surface mid-cutover, not during planning. When user mapping fails (mismatched UPNs, unresolved SMTP proxies, or missing target accounts), Mailbox Replication Service stalls, and manual remediation follows.

Identity readiness means your Entra ID objects (users, security groups, distribution groups, mail-enabled contacts) are aligned, licensed, and resolvable in the target tenant before mailbox copy starts. The Microsoft Learn cross-tenant mailbox migration documentation lists the prerequisites in detail. If your identity layer isn’t right, no mailbox tool can compensate for it on the way through.

2. What actually breaks after cutover (and why users notice first)

Not everything makes the trip intact. Mailbox-side artifacts (server-side rules, recurring meetings, delegate relationships, automatic replies) frequently survive the move with subtle differences that surface as user issues days or weeks later.

The downstream cost is helpdesk volume, often for weeks. Common breakage points:

• Folder hierarchy: subfolder paths can flatten or rename in transit, confusing users who built their own organization scheme.
• Server-side (Inbox) rules: rules referencing source-tenant addresses or shared folders fail silently in the target tenant. Automated workflows stop without anyone noticing for a sprint or two.
• Recurring meetings: organizer changes, calendar permission shifts, and meeting series re-anchored at new instances produce duplicates or orphans.
• Delegate relationships: assistants lose Send-on-Behalf or Send-As access to executive mailboxes. That call comes fast.

3. Archive mailboxes: the scope mistake that triggers budget conversations

In-place archive mailboxes get missed during scoping more often than any other Exchange Online artifact. They’re commonly enabled in regulated tenants and in any environment with retention or eDiscovery requirements, but they don’t surface in the same Get-Mailbox reports admins typically run for headcount estimation. You need Get-Mailbox -Archive or PowerShell that filters on ArchiveStatus to see them.

Per-mailbox migration tools usually treat archives as separate billable scope. Auto-expanding archives push the data volume even higher in tenants where users hit the default 100GB primary archive limit. Discovering several hundred archives late in project scope is a budget conversation nobody wants to have.

4. Litigation Hold: where migrations fail silently or become compliance risks

Litigation Hold preserves mailbox content for legal or regulatory reasons. Hold state lives on the mailbox object itself, and Microsoft 365 enforces it independently of any migration tooling. The most common cross-tenant failure mode: when a source mailbox is on Litigation Hold and its Recoverable Items folder exceeds the default 30GB quota, Mailbox Replication Service moves fail because the target quota is too small. The fix involves enabling Litigation Hold on the target MailUser and expanding the Recoverable Items quota to 100GB before the move (using Set-MailUser -EnableLitigationHoldForMigration $TRUE for non-hybrid tenants, or transitioning ELC flags via Azure AD Connect for hybrid).

When moves fail silently, you have a rework problem. When the hold state isn’t preserved, you have a compliance problem. Neither is recoverable on the cheap.

5. Why most migration issues aren’t found until weeks after cutover

Without pre-migration diagnostics and post-migration validation, broken mailboxes get discovered weeks after cutover. That’s also when fixing them costs the most: users have moved on, helpdesk tickets pile up, and the project team has rolled off.

Migration tooling that includes built-in assessment and validation closes most of this gap. ShareGate Migrate’s Assess workflow surfaces inactive content, permission anomalies, and structural issues before execution, with a parallel Organize phase for post-cutover validation. Tools without that workflow push the discovery and remediation work back onto the IT team or onto the partner doing delivery.

Per-mailbox or fixed-fee: which Exchange migration pricing model is right?

Two pricing models dominate the Exchange Online migration tooling market.

Per-mailbox pricing charges separately for each primary mailbox, archive, shared mailbox, and Microsoft 365 Group mailbox. BitTitan MigrationWiz, Quest On Demand Migration, and SkyKick all use variations of this model. The headline number is straightforward, but the billable scope expands as you uncover archives, groups, and shared mailboxes during execution. A 1,000-user tenant typically contains a meaningful number of additional billable objects once everything is counted, often pushing total billable scope well above the headcount number.

Fixed-fee licensing gives you a known budget number on day one. ShareGate Migrate uses a fixed-fee model with no per-mailbox add-ons. The complexity and the discovery risk move to the vendor’s side of the contract.

Factor	Per-mailbox pricing	Fixed-fee licensing
Budget certainty	Low (scope-dependent)	High (known upfront)
Archive handling	Often separate charge	Typically included
Shared/Group mailboxes	Additional units	Typically included
Common vendors	BitTitan, Quest, SkyKick	ShareGate Migrate
Best for	Small, well-scoped projects	Complex, enterprise migrations

Per-mailbox can be cheaper for small, well-scoped projects. Fixed-fee gets safer as scale, complexity, and regulatory scope increase, particularly when archive mailboxes and held mailboxes are in play.

What Exchange migration scope do IT Directors miss at planning?

Four scope items are most often missed during migration planning, and they cost real money when they show up late. Not all scope gaps are equally damaging. In most Exchange migrations, coexistence and archive mailbox discovery are the two issues most likely to break the budget. Litigation Hold is the next major risk in regulated environments, while group mailboxes, shared mailboxes, and recurring meetings are usually secondary scope expansion items.

Coexistence and staged cutover requirements

Most cross-tenant migrations don’t happen in one weekend. Coexistence means that both source and target tenants remain operational while you move mailboxes in waves, often over 4 to 12 weeks. Mail flow, calendar free/busy, and directory resolution all need to work across both tenants during that window.

Tools without delta or incremental migration capability force re-execution of entire mailbox sets when changes accumulate between an initial copy and the cutover. ShareGate Migrate supports delta migration, so subsequent passes sync only the changes that occurred since the previous run, keeping cutover windows short and predictable.

Archive scope in regulated tenants: why sizing mistakes get expensive fast

Archive mailboxes are commonly enabled across Microsoft 365 E3 and E5 tenants, especially where retention policies, eDiscovery, or industry compliance requirements drive long content retention. Archive size directly affects migration duration because archive content passes through the same throughput as primary mailbox content. Per-mailbox migration tools usually charge for archives as separate billable units.

Litigation Hold and target-tenant validation

Mailboxes under Litigation Hold can fail to move when the migration path doesn’t handle hold state, and hold-aware migration is non-negotiable in regulated environments. Hold state lives on the mailbox object and is enforced by Microsoft 365 itself, so the migration tool’s job is to move the mailbox without violating hold constraints, not to manage compliance configuration in the target tenant. Verify hold state in the target tenant as part of cutover validation.

The “small” mailbox types that quietly expand your billable scope

Microsoft 365 Group mailboxes, shared mailboxes, and recurring meetings are easy to overlook during scoping but each adds billable units in per-mailbox pricing models. Recurring meetings deserve special attention since their behavior is governed by Exchange Online’s recipient resolution and meeting-series logic, not by anything the migration tool can override. Test a representative set in a pilot wave before scaling.

Important: Retention policies, Litigation Hold enforcement, and compliance configuration are Microsoft 365’s responsibility, not the migration tool’s. Migration tooling handles scope inclusion and mailbox movement; verify retention and hold state independently in the target tenant as part of cutover validation.

How to build a migration cost model finance won’t challenge

A defensible Exchange migration cost model accounts for more than the sticker price. Five line items, in this order:

Step 1: Calculate tooling and service licensing

Start with the vendor quote. Note whether it’s per-mailbox or fixed-fee. If per-mailbox, get explicit clarity on what counts as a billable unit: primary mailboxes only, or are archives, shared mailboxes, and Microsoft 365 Group mailboxes counted separately?

Step 2: Estimate internal IT hours

Account for migration owners, Exchange admins, identity admins, project managers, and helpdesk staff. Multiply estimated hours by loaded labor cost (salary plus benefits and overhead, typically 1.3 to 1.5x base salary). For most enterprise migrations this line is larger than the tool license.

Step 3: Add partner or consultant hours

If you’re using a partner or external consultant, include their hourly rates and a defined scope. McKinsey’s cloud migration research found systems integrator spending is the most-cited cost overrun outside change management, which is why scope accuracy at the contract stage matters more than rate negotiation.

Step 4: Build in a rework reserve

Projects rarely go exactly to plan. The 2025 DevOps Migration Index found an average 18% project cost overrun across platform migrations, with $315K typical overrun. Standard practice is to add 15 to 25% for rework, failed moves, and discovery-phase scope additions, and to defend that reserve explicitly when you present the budget.

Step 5: Budget the post-migration support window

Helpdesk surge, user retraining, delegate and shared-access fixes, and broken-rule remediation. The post-migration support tail typically runs four to eight weeks for a mid-size enterprise migration, longer in regulated environments. Finance wants to see this line item explicitly so they aren’t surprised by sustained T2 ticket volume after cutover.

Choose a migration approach that makes your budget predictable

The pattern is predictable. You get a per-mailbox quote, start the project, discover archives, hold mailboxes, and shared scope you didn’t price, and go back to leadership for more money.

Two structural changes reduce that risk: assessment before execution, and pricing that doesn’t depend on object count. The first turns archives, hold mailboxes, and group artifacts into known scope before contracts get signed. The second eliminates the per-unit math that makes late discoveries expensive.

Before signing with any Exchange Online migration tool or partner, ask:

• What counts as a billable unit, and is that defined in writing?
• Does the tool support delta migration for staged cutovers, or does each run start from scratch?
• How does the tool handle mailboxes under Litigation Hold? The right answer is: respects hold state, doesn’t require removal, and doesn’t claim to manage compliance.
• What pre-migration assessment is included, and what does the validation report look like at the end?
• How is archive mailbox scope priced and handled?

ShareGate Migrate is a fixed-fee, tenant-to-tenant Microsoft 365 migration tool built for this scope, with pre-migration assessment, delta migration support, archive mailbox coverage, and Litigation Hold-aware migration across SharePoint, Teams, OneDrive, and Exchange Online. See how ShareGate Migrate handles mailbox migration.

Frequently asked questions about Exchange tenant-to-tenant migration