Office 365 Migration Cost: What You Actually Pay in 2026

Nobody in this industry publishes migration pricing. Every competitor's page says "contact us for a quote," which usually means the price depends on how much they think you can pay. After 1.4M+ users migrated, here is the actual cost structure — our rates, the market's rates, the tool costs, and the numbers most quotes conveniently leave out.

The three cost components: labor, licenses, tools

Every Office 365 migration cost breaks into exactly three buckets. Vendors blur them together in quotes; keep them separate and you can compare any two proposals in five minutes.

The number that varies most — and where you can overpay by 3–4x — is labor. So let's start there.

Per-user labor pricing: market rates and ours

Market pricing for migration labor typically runs $25–$50 per mailbox from US-based consultancies, with SharePoint and Teams quoted separately, often as vague "project fees." Some shops quote hourly ($150–$250/hr) and estimate 15–30 minutes per mailbox plus project overhead — which lands in the same range but shifts all schedule risk onto you.

Our pricing, published because hiding it helps nobody:

Volume discounts: −15% at 100+ users, −25% at 500+. The per-mailbox work genuinely gets cheaper at scale because the fixed setup amortizes.

Why the $500 minimum exists

A 5-user migration is not one-eighth the work of a 40-user migration. Certain tasks cost the same whether you have 5 mailboxes or 500:

• Tenant hardening — a fresh Microsoft 365 tenant ships with defaults you should not run a business on. Security baseline configuration takes the same hours regardless of headcount.
• MFA and Conditional Access baseline — policies are per-tenant, not per-user.
• Discovery — inventorying the source environment, finding the PSTs and forgotten shared mailboxes, mapping what goes where.
• DNS cutover — MX, SPF, DKIM, DMARC, Autodiscover. Five records for 5 users, five records for 5,000.

Any vendor quoting a 5-user migration at pure per-seat rates with no minimum is either skipping the tenant security work or planning to bill you for "unexpected scope" later. Both are worse than an honest minimum.

What migration tools cost — and when you need them at all

Here is the part of the cost conversation most vendors get wrong, sometimes deliberately: for the majority of migrations, the right tool price is zero. Microsoft's native tooling is free and covers most real-world scenarios:

• Cutover and minimal hybrid migration — Exchange on-premises to Exchange Online, built into the Exchange admin center.
• SharePoint Migration Tool (SPMT) and Migration Manager — file servers, SharePoint on-prem, and Google Drive to SharePoint/OneDrive.
• IMAP migration — generic mail hosts, cPanel, GoDaddy email, Zoho.
• Google Workspace batch migration — native in the Exchange admin center for mail, calendar, and contacts.

Paid tools (BitTitan MigrationWiz, Quest, AvePoint — typically $10–$15 per user) earn their cost in two situations: tenant-to-tenant migrations, where Microsoft's native T2T tooling still has real gaps, and edge cases like Teams chat history, complex public folder structures, or sources with no native connector. We covered the full landscape in our Office 365 migration tools comparison.

When a paid tool is genuinely required, our model is BYOL: you buy the licenses directly from the vendor and we run them — no markup. A vendor who insists on reselling tool licenses at an undisclosed margin, or who quotes BitTitan for a straightforward cutover that native tools handle free, is padding the invoice. Ask them to justify the tool line item against Microsoft's free options; the answer tells you a lot.

Microsoft 365 license costs are separate

Licenses are an ongoing subscription, not a migration cost — but every budget conversation ends up including them, so be clear about the split. Business Basic runs about $6/user/month, Business Standard $12.50, Business Premium $22, with enterprise E3/E5 above that. The right plan depends on whether you need desktop Office, Intune, and the security stack — we broke the whole matrix down in our Microsoft 365 license comparison.

One real cost trap here: during a hybrid or staged migration you may pay for both the old environment and Microsoft 365 simultaneously for a month or two. Budget for the overlap; don't let it surprise you.

Hidden costs people forget

These are the line items that never appear in the competitor's quote and always appear in the actual project:

• Bandwidth and throttling time. Google caps mailbox export at roughly 1–2 GB/day per account, and Exchange Online throttles ingestion. A 30 GB mailbox can take two weeks of background sync. That's calendar time, and if you're paying hourly for someone to babysit it, it's money.
• PST hunting. Users have local PST archives on laptops, in desktop folders, on USB drives. Finding, collecting, and importing them is often 20–30% of total effort on older Exchange environments — and it's rarely in the initial quote because nobody surveyed for it.
• Rewriting workflows. Anything that talks SMTP to the old server — scanners, printers, line-of-business apps, scripts — needs reconfiguring. Each one is 15 minutes if inventoried, half a day of firefighting if discovered on Monday morning.
• User training. The top post-migration ticket is never technical. It's "where did my stuff go." A one-hour orientation eliminates most of the ticket volume; skipping it moves the cost to your helpdesk instead of removing it.
• Parallel-running the old server. Decommissioning takes planning. Most organizations run the old Exchange server or Google tenant 30–90 days post-cutover — hosting, licensing, and power for a box that's doing nothing.

Cost by company size: real numbers with the math

Assumptions: email plus OneDrive for everyone, a typical SharePoint footprint for the size, native tools where they fit. Licenses excluded (ongoing, not migration).

The ranges widen with size because complexity does: a 1,000-user org with one file server is cheaper than a 250-user org with 15 years of public folders, three legal holds, and a tenant-to-tenant twist. The math above is the starting point, not the quote — discovery is what turns a range into a number.

DIY cost vs. managed migration

DIY is a legitimate option — we published the tools and steps precisely so you can. But DIY is not free; it's paid in admin salary and risk instead of invoices.

Run the numbers honestly. A sysadmin at $95k/year costs roughly $46/hour fully loaded. A 50-user migration done carefully — discovery, tenant setup, security baseline, pilot with 10–20 users, staged sync, weekend cutover, a week of cleanup — is realistically 40–60 hours for someone doing it the first time. That's $1,800–$2,800 of salary, before counting the work that admin didn't do that month. Roughly what a managed migration costs, with one difference: we've done this 1,400+ times and your admin is on attempt one.

The risk side is harder to invoice but very real: in our experience roughly 45% of DIY cutovers miss their planned weekend window — usually throttling that wasn't pre-staged, DNS TTLs nobody lowered, or an Autodiscover record pointing at the corpse of the old server. A missed cutover means Monday morning with 50 people asking where their email is. Our managed process runs a pilot of 10–20 users first, pre-stages data ahead of a 2–4 hour weekend cutover window, checksums with SHA-256 verification, and includes 30 days of hypercare. That process is why we're at 99.8% on-schedule success and zero data loss across 1.4M+ users — and it's what the labor line item actually buys.

How to get an exact number

Two ways, both free:

1. Run the migration cost calculator. Enter your user count, workloads, and source platform; it applies the exact rates and volume discounts above and gives you a number in about a minute. No email gate.
2. Get a fixed quote. For anything with complexity — hybrid, T2T, compliance requirements — a 30-minute discovery call produces a fixed-price proposal from our Microsoft 365 migration services team. Fixed means fixed: the discovery is where we absorb the scope risk, not a change order in week three.

FAQ

How much does Office 365 migration cost per user?

Labor runs $12–$50 per mailbox depending on the vendor; ours starts at $12. Add ~$10/user for OneDrive and per-site pricing for SharePoint. Tools add $0 for most projects, $10–$15/user for tenant-to-tenant.

What does email migration cost for a small business?

A 10-user email-only move typically lands at the $500 project minimum with us, $1,500+ elsewhere. The minimum covers tenant security setup and DNS cutover — work that doesn't shrink with headcount.

Is Microsoft's migration tooling really free?

Yes. Cutover, minimal hybrid, IMAP, Google Workspace batch migration, and SPMT/Migration Manager are all included with your Microsoft 365 subscription. See Microsoft's mailbox migration documentation for the native options. Paid tools are for T2T and edge cases only.

Are Microsoft 365 licenses included in migration quotes?

They shouldn't be mixed in. Licenses are an ongoing subscription paid to Microsoft or a CSP; migration is a one-time project cost. Any quote that bundles them without a line-item split is hiding margin somewhere.