Email Migration Cost Per Mailbox: 2026 Industry Pricing

You're putting together a budget for an email migration and every quote you read says something different. One vendor charges $12 per mailbox, an MSP quotes $180, and a colleague at another company swears theirs cost over $400 each. They are all telling the truth — they just aren't pricing the same thing. This post walks through the actual 2026 ranges, what's inside each number, and the variables that move the headline up or down.

What "cost per mailbox" actually measures#

There are three different per-mailbox numbers in circulation, and conflating them is how budgets blow up.

Tool license cost. What you pay the migration software vendor for the right to move N mailboxes. Roughly $5 to $25 per mailbox for SaaS in 2026, or a flat fee for desktop or self-hosted tooling that you spread across however many mailboxes you move.

Fully-managed MSP fee. What an MSP charges to deliver the entire project: discovery, comms, configuration, cutover, and post-cutover support. The tool license might be inside this number or separate. Typically $50 to $250 per mailbox for vanilla cloud-to-cloud work.

Total project cost per mailbox. Tool + MSP labor + your own internal time + licenses + comms + training. This is the only number that matters for budgeting. Almost no one quotes it, because no one knows your internal hourly rate.

Whenever someone gives you a per-mailbox cost, your first question is which of the three they mean.

Tool licensing ranges in 2026#

These are the categories you'll encounter when buying migration software.

SaaS per-mailbox platforms#

The dominant model: BitTitan MigrationWiz, CloudM, Quadrotech (now part of Quest), CodeTwo Office 365 Migration, SkyKick Cloud Manager, Cloudiway. You pay per mailbox, one-time, for a project license that's usually valid for 90 to 365 days.

Ranges in 2026:

• Under 100 mailboxes: $18 to $28 per mailbox.
• 100 to 500 mailboxes: $14 to $22 per mailbox.
• 500 to 2,000 mailboxes: $10 to $16 per mailbox.
• Over 2,000 mailboxes: $7 to $12 per mailbox, often via channel partner discount.

These are list prices. Channel partners and MSPs typically discount 15 to 30 percent off list. Direct buyers do not usually see those discounts unless they negotiate.

Self-hosted and desktop tools#

Tools that run on your own infrastructure or workstation: open-source utilities like imapsync, commercial desktop tools, and a small set of vendor-licensed on-prem options.

The pricing model is different — flat fee per license, sometimes time-bounded — so the per-mailbox equivalent depends entirely on how many mailboxes you migrate with one license.

• A $300 desktop license used for 30 mailboxes works out at $10 per mailbox.
• The same license used for 300 mailboxes is $1 per mailbox.
• For sub-10-mailbox projects, the per-mailbox math is poor; for over 100 mailboxes, it's the cheapest tool category by a wide margin.

For a deeper breakdown of what you trade off when you pick the cheapest tool, the free vs paid migration tooling comparison is the relevant deep-dive.

Microsoft-native tools#

The Exchange Online migration endpoints, Mailbox Migration Service, and Microsoft's own minimum-hybrid configuration come free with M365 tenant licenses. The per-mailbox tool cost is effectively zero. The labor cost to operate them is not.

Microsoft's tools work well within Microsoft's ecosystem. They're substantially less useful when the source is IMAP, when you need granular item-level reporting, or when you want a single console showing 300 mailboxes in flight at once.

Vendor-bundled migration#

Some destination providers (Google Workspace, Zoho Mail) include limited-feature migration tools at no additional cost. Useful for sub-50-mailbox moves. Limited control, limited error reporting, limited throughput. Per-mailbox tool cost: zero. Per-mailbox labor cost when something breaks: high.

Fully-managed MSP pricing in 2026#

When an MSP quotes you a per-mailbox fee, it includes labor and usually the tool license. Here is the realistic 2026 range, broken by complexity.

Tier 1 — vanilla cloud-to-cloud#

M365-to-M365 tenant-to-tenant, Google Workspace-to-M365, Google-to-Google. No on-prem footprint, no archive ingest, no public folders.

• $50 to $90 per mailbox at high volume (500+ mailboxes).
• $80 to $150 per mailbox at mid volume (100 to 500).
• $120 to $250 per mailbox at low volume (under 100).

The low-volume premium isn't price-gouging — the fixed cost of discovery, comms, and a cutover weekend is roughly the same whether you're moving 20 mailboxes or 100.

Tier 2 — IMAP source to cloud destination#

cPanel, GoDaddy IMAP, Rackspace Classic, hosted Zimbra, generic IMAP servers to M365 or Google Workspace.

• $100 to $200 per mailbox above 100 mailboxes.
• $150 to $300 per mailbox below 100.

IMAP throughput is generally lower than cloud-API throughput, so wall-clock time per mailbox is longer. Folder name conversion (UTF-7 quirks, special characters) adds rework. Source authentication is often weaker — app passwords, no OAuth — which means more manual intervention during cutover.

Tier 3 — hybrid Exchange to Exchange Online#

On-prem Exchange 2016 or 2019 with hybrid config, possibly public folders, possibly archive databases.

• $200 to $350 per mailbox at volume.
• $300 to $500+ per mailbox below 100.
• Public folder migration usually quoted as a separate $5,000 to $25,000 project regardless of mailbox count.

Hybrid is where the per-mailbox model starts to mislead. The work is largely fixed-cost — your AD sync, your hybrid config, your certificate work — plus a small per-mailbox component. A 50-mailbox hybrid and a 200-mailbox hybrid take roughly the same hours of engineering.

Tier 4 — tenant-to-tenant with compliance#

Acquisitions, divestitures, legal-hold preservation, journaling rehydration.

• $300 to $600+ per mailbox.
• Add line items for eDiscovery, retention policies, Teams chat migration, SharePoint and OneDrive.

This isn't really an email migration anymore. It's an identity-and-data migration with email as one of several streams.

Hidden costs that don't appear in the per-mailbox number#

A clean MSP quote breaks these out. A cheap headline quote rolls them into change orders mid-project. Either way, they exist.

Comms and change management#

User-facing email drafts, FAQ docs, manager briefings, training videos. 4 to 10 hours per project regardless of size. $400 to $1,500 as a flat line item.

After-hours and weekend work#

Most cutovers happen on Friday evening or Saturday morning. Weekend premiums add 25 to 50 percent to labor cost for the cutover window. Some MSPs bundle this into the per-mailbox fee; others bill it separately.

Post-cutover support window#

One calendar week minimum. 8 to 14 hours of engineering and helpdesk per 100 mailboxes. $1,500 to $3,500 if billed separately. Most reputable MSPs include it in the headline fee — see the MSP billing models guide for how this gets structured.

PST import#

If users have local PST files that need ingesting into the destination, add $20 to $60 per PST. PST corruption rate is non-trivial — expect 5 to 15 percent of PSTs to require repair before ingest.

Archive ingest#

Mimecast, Barracuda Cloud Archiving, Proofpoint Enterprise Archive, Veritas Enterprise Vault. Each is a separate project, priced per archive volume in GB rather than per mailbox. Cost varies widely; budget $50 to $200 per archived mailbox as a starting point and refine after discovery.

DNS, SPF, DKIM, DMARC#

Cutover always involves MX changes. Often discovers that SPF is broken, DMARC is in monitor mode, DKIM was never set up. Remediation adds 2 to 6 hours of engineering. $400 to $1,200 if billed.

Licensing transition#

Source license decommissioning, destination license assignment, group-based licensing setup. 4 to 12 hours of admin work. $600 to $2,000 if billed separately.

Training and enablement#

Recorded walkthroughs, live Q&A sessions, manager briefings. $500 to $3,000 per project, depending on depth.

When you sum these honestly, the "$50 per mailbox" headline number for a 200-mailbox project — $10,000 — is really $18,000 to $25,000 of work. Reputable MSPs surface that up front. Cheap quotes surface it as change orders.

What moves the per-mailbox number up#

Five variables move the price more than anything else. If your project has any of them, ask explicitly how the MSP is pricing them.

Mailbox size. Anything over 50 GB takes meaningfully longer per mailbox. Above 100 GB you're paying for human attention as much as machine time, because failed batches need intervention.

Item count. A 30 GB mailbox with 500,000 items is harder than a 30 GB mailbox with 50,000 items. Most tools throttle per-item, not per-GB, so item count is the truer cost driver.

Folder structure. Users with thousands of folders or deep nesting (15+ levels) trigger UTF-7 conversion errors and rate limits on the destination. Cleanup adds time.

Source authentication. OAuth-capable sources are cheaper to migrate than basic-auth-only sources, because the migration runs unattended for longer.

Cutover window pressure. A two-week window is cheaper than a 36-hour window for the same mailbox count, because you can throttle below provider rate limits and avoid weekend premiums.

What you should actually compare across quotes#

When you get three quotes, line them up on:

1. What's inside the per-mailbox number. Tool? Comms? Training? After-hours? Support window?
2. Tier classification. Is the MSP quoting Tier 1 when your environment is Tier 2?
3. Mailbox size assumptions. Did they ask, or did they guess? An MSP that didn't ask is mispricing your project.
4. Support window terms. Days included? Hour cap? Hourly rate beyond?
5. Change-control language. What triggers a change order? What's billed at T&M vs absorbed?

Don't compare the headline number first. Compare the assumptions, then compare the headline.

Benchmarking against industry averages#

For broader project-cost benchmarks — total cost rather than per-mailbox — the Office 365 migration cost guide lays out reference numbers for 25, 100, 500, and 2,000-mailbox projects with the line items behind each one. The complete email migration guide covers the planning side that drives most of the variance.

For tooling specifically, if BitTitan's per-mailbox license is your benchmark, the BitTitan pricing alternatives breakdown explains which tools target which use cases and where they actually save money vs where the saving is illusory.

The honest take#

The per-mailbox model is useful as a budget heuristic and dangerous as a comparison tool. It assumes a constant unit of work and the unit is never quite constant. The MSPs that price honestly will tier your project, separate the line items, and quote a range with the assumptions that take it from low to high.

The vendors selling tooling have it easier — their cost is closer to truly per-mailbox — but even there, what you pay depends on volume, channel, and how aggressively you negotiate.

If you're putting a budget together, assume:

• Tool license: $8 to $20 per mailbox.
• MSP labor for vanilla cloud-to-cloud: $80 to $180 per mailbox.
• Add 30 to 50 percent for complexity (IMAP source, archive, large mailboxes).
• Add another 20 to 40 percent for compliance overlay or hybrid Exchange.
• Add a project minimum of $2,500 to $5,000 for any project under 50 mailboxes.

Then add 15 percent for the things you didn't think to ask about. That contingency line is the difference between a project that comes in on budget and one that doesn't.