The question we get asked more than any other: what is this going to cost us? And the honest answer is: it depends on things you probably haven't measured yet. This article breaks down the real cost drivers, gives you realistic per-mailbox and project-level numbers, and tells you what will push your quote up or down.
Short answer for quick reference: Most organizations with 50–500 mailboxes pay $5,000–$40,000 in professional services for a complete Microsoft 365 migration, depending on scope, migration type, and identity complexity. Healthcare environments with HIPAA requirements typically run 20–40% higher.
In This Article
How Microsoft 365 Migration Professional Services Are Priced
There are three common pricing structures in the Microsoft 365 migration market:
Per-Mailbox Pricing
The most common model. A per-mailbox rate covers the migration of each email account from the source environment (Exchange on-premises, Google Workspace, another cloud) into Exchange Online. Per-mailbox rates typically run $25–$75 per mailbox for a standard cutover or staged migration, with rates decreasing at volume (500+ mailboxes).
Watch for narrow scope: Some per-mailbox quotes cover mailbox data migration only. SharePoint, OneDrive, identity (Entra Connect), DNS changes, security configuration, and post-migration support may be billed separately. Always ask what's in scope before comparing quotes.
Flat-Fee Project Pricing
A fixed price for the full engagement — assessment through post-migration support. Better for organizations that want budget certainty. Flat-fee projects are more common for mid-market and enterprise engagements where scope is well-defined upfront. Most of our engagements are scoped this way.
Hourly / Time and Materials
Common for advisory work, one-off configurations, or complex troubleshooting. M365 engineering rates range from $150–$300/hr depending on seniority and specialization. Rarely the best model for a full migration — the risk of scope creep lands on you.
Cost by Migration Type
| Migration Type | Typical Org Size | Professional Services Range | Notes |
|---|---|---|---|
| Cutover (Exchange) | Under 150 mailboxes | $3,000–$12,000 | Fastest to execute; single cutover event; minimal coexistence. |
| Staged (Exchange) | 150–2,000 mailboxes | $8,000–$40,000 | Batched migration over weeks; requires Entra Connect for directory sync. |
| Hybrid (Exchange) | 500+ mailboxes | $15,000–$80,000+ | Permanent or long-term coexistence; most complex; highest risk if done wrong. |
| Google Workspace to M365 | Any | $35–$65/mailbox | Google Drive to OneDrive scope adds significant time; identity provisioning is different. |
| Tenant-to-Tenant | Any (M&A, restructure) | $20,000–$100,000+ | Moving between two existing M365 tenants; complex identity and permissions work. |
What Drives Microsoft 365 Migration Cost Up
The per-mailbox numbers above assume a reasonably clean source environment. Here is what will push your actual quote significantly higher:
Active Directory and Identity Issues
UPN mismatch between Active Directory and your email domain is the single most common cause of migration delays. If your AD UPNs are user@corp.local but your email is user@company.com, every user needs to be remediated before synchronization. This is hours of work in large environments and often requires staged rollout to avoid breaking existing authentication.
Hybrid Exchange Coexistence
Organizations that cannot move everyone at once — or that have on-premises applications authenticating against Exchange — need hybrid coexistence. This requires running an on-premises Exchange server indefinitely (even if you move all mailboxes to the cloud), maintaining Entra Connect, and managing two mail routing environments. The engineering overhead is substantial.
SharePoint and File Share Migration
SharePoint Online and OneDrive migration from on-premises SharePoint or from Windows file shares is often the most time-consuming part of an M365 engagement — more so than mailboxes. File permissions, metadata, deep folder structures, and SharePoint customizations all require careful handling. Budget $5,000–$30,000 for SharePoint scope depending on data volume and complexity.
Compliance and Security Configuration
A secure M365 tenant doesn't come configured out of the box. Conditional Access policies, legacy-authentication blocking, DLP rules, retention policies, audit logging, and sensitivity labels all need to be built. Organizations with HIPAA, GDPR, or PCI DSS requirements must get this right before migration completes. Add $3,000–$15,000 for compliance scope in regulated industries.
Application Dependencies
Line-of-business applications that authenticate via Exchange Web Services, SMTP relay, or Active Directory will break unless reconfigured before cutover. Discovery and remediation of these dependencies is often missed in vendor quotes and surfaces as emergency work mid-migration.
The pre-migration assessment is where this is caught. A real assessment — not a sales conversation — identifies app dependencies, UPN issues, mailbox sizes, and directory health before a single mailbox moves. If a vendor is quoting you without spending meaningful time in your environment first, that's a warning sign.
What Should Be Included in a Complete M365 Migration Quote
A complete professional services engagement should cover:
- Environment assessment — directory health, mail flow, app dependencies, bandwidth
- DNS changes — MX, autodiscover, SPF, DKIM, DMARC setup
- Entra Connect setup or remediation (for hybrid and staged migrations)
- Migration tool configuration — SkyKick, BitTitan, Quest, or native tooling
- Pilot migration — test group of 5–20 mailboxes before production
- Production migration in waves
- Outlook profile reconfiguration — manual and Autodiscover
- Post-migration support window — typically 30 days
- Runbook and documentation handoff
Separately priced in most engagements:
- SharePoint Online / OneDrive migration
- Intune / endpoint management setup
- Microsoft Purview and compliance configuration
- Security baseline (Conditional Access, MFA, Defender for 365)
- Training and change management
Microsoft 365 Licensing Costs
Professional services are separate from your Microsoft 365 subscription cost. Common plan prices as of 2026:
| Plan | Per User / Month | What's Included |
|---|---|---|
| Microsoft 365 Business Basic | $6 | Exchange Online, Teams, SharePoint, OneDrive. No desktop Office apps. |
| Microsoft 365 Business Standard | $12.50 | Above + desktop Office (Word, Excel, PowerPoint, Outlook). |
| Microsoft 365 Business Premium | $22 | Above + Intune, Defender for Business, Azure AD Premium P1, Purview basics. |
| Microsoft 365 E3 | $36 | Enterprise tier. Azure AD P1, Compliance Manager, Purview (limited). |
| Microsoft 365 E5 | $57 | Full compliance, Defender XDR, Azure AD P2, Power BI Pro, advanced eDiscovery. |
Healthcare licensing note: HIPAA compliance features (audit logging, hold policies, DLP with PHI classifiers, advanced message encryption) are gated behind E3/E5 or Microsoft 365 Business Premium. If your organization handles PHI and you're being quoted on Business Basic, ask specifically what you'll do about HIPAA scope.
Healthcare and Regulated Industry Pricing
Healthcare organizations add complexity that almost always pushes project cost above standard commercial rates:
- HIPAA Business Associate Agreement (BAA) — Microsoft provides one, but your tenant must be configured to honor it. BAA-compliant configuration includes specific data residency, audit, and access settings.
- EHR/EMR integration — Epic, Cerner, Meditech, and other clinical systems may authenticate via Exchange or require specific mail routing. Discovery and remediation takes time.
- On-site assessment requirement — Hospital IT departments often require vendor on-site time for HIPAA vetting, access provisioning, and to meet their BAA obligations. Remote-only vendors can't deliver this.
- Change control boards and maintenance windows — Healthcare cutover windows are tightly constrained. A migration that fails at 2am in a standard commercial environment can be rolled back. In a clinical environment, that window is smaller and the stakes are higher.
For healthcare organizations, budget 20–40% above standard commercial rates for equivalent mailbox counts. A 200-mailbox hospital migration that would cost $15,000 commercially may run $18,000–$22,000 with proper HIPAA-compliant configuration, on-site time, and clinical-environment risk handling.
Hidden Costs Most Vendors Don't Quote
Legacy Protocol and App Remediation
When you block legacy authentication (which you should — it disables MFA), every device and application using Basic Auth over IMAP, POP3, or SMTP AUTH will stop working. Printers, scanners, ERP systems, and legacy CRM applications all need to be reconfigured. Discovery of these systems is usually billed as extra scope or absorbed into emergency work during the migration window.
Post-Migration Drift
Tenants don't stay in the configuration you put them in. Conditional Access policies get modified, licenses get reassigned, DLP rules get exceptions added. Ongoing administration or an annual configuration review is worth budgeting for — especially if compliance is a requirement.
User Adoption and Help Desk Spike
Expect a 2–4x spike in help desk volume in the first two weeks after cutover. If your IT team is small, this hits them hard. Factor in either extra help desk capacity or a temporary contract for the period immediately after migration.
MX TTL Planning
If your current MX record has a long TTL (24–48 hours), lowering it requires planning time before cutover — not something you want to discover at 11pm on cutover night. Not a direct cost, but a scheduling dependency that can force delays.
How to Get an Accurate Quote
The single best thing you can do before collecting vendor quotes is to know your own environment. Before any vendor conversation, have these ready:
- Current mailbox count (active only — exclude shared and resource mailboxes for per-mailbox pricing, but understand they still need to be migrated)
- Current email platform and version (Exchange 2013, 2016, 2019, Google Workspace, etc.)
- Whether you have Active Directory and its current UPN domain suffix
- Any on-premises SharePoint sites and approximate data volume
- Applications that send or receive email or authenticate via Exchange
- Any regulated data requirements (HIPAA, GDPR, PCI DSS, PIPEDA)
- Target timeline and any hard cutover date constraints
A vendor who gives you a firm quote without asking most of these questions is either very experienced with your specific migration pattern, or they're quoting scope that will expand significantly once they get into your environment.
Get a scoped quote — no guessing
We assess your environment before we quote. The assessment is free, it's real engineering work, and you'll leave with a clearer picture of what's involved regardless of whether you hire us.
Request a Free AssessmentWhat 365 Consultants Charges
We scope every project before we price it. We don't publish per-mailbox rates because in practice, two 200-mailbox environments can be completely different projects. What we can tell you:
- Our assessments are free and involve real review of your environment — not a sales call
- We price to scope, not to mailbox count, because mailbox count is a poor proxy for complexity
- Healthcare and regulated environments get the same engineer throughout — no handoffs to offshore teams after the sales cycle
- Our quotes include documentation and runbook handoff at project close
If you want a realistic number before going through a full assessment, reach out with your mailbox count, source platform, and any compliance requirements. We'll give you a rough range in 24 hours.