There is no useful single price for a Microsoft 365 migration. Anyone who quotes you one without seeing your environment is guessing. A ten-user business with simple IMAP mailboxes can be straightforward. A thirty-user business with old Exchange, messy public folders, file shares, poor DNS, unmanaged devices and no MFA can be far more involved. User count alone tells you almost nothing.
What actually drives cost is complexity. Here is how we think about it when we scope a migration project.
What drives the cost?
| Cost driver | Lower complexity | Higher complexity |
|---|---|---|
| Small mailboxes, no shared mailboxes, clean DNS. | Hybrid Exchange, large mailboxes, public folders, delegates, SMTP relay. | |
| Files | Small, clean file shares with clear owners. | Large file shares, broken permissions, duplicates, long paths, old archive data. |
| Identity | Cloud-only users or clean Entra Connect. | UPN mismatches, duplicate accounts, federation, sync errors. |
| Security | MFA already in place and admin roles understood. | No MFA, shared admin accounts, unmanaged devices, weak mail security. |
| Adoption | Users already comfortable with Microsoft 365. | Users moving from Google or legacy systems with limited training. |
Read the right-hand column honestly. If your business sits mostly in that column, the migration is not a weekend job and the quote should reflect that.
Typical project components
- Discovery and migration planning.
- Tenant setup and domain verification.
- Identity and licence configuration.
- Email migration to Exchange Online.
- File migration to SharePoint and OneDrive.
- Teams, SharePoint and security baseline configuration.
- User communications, training and post-migration support.
Cost ranges to discuss carefully
We are deliberately not going to plaster a fixed price on this page, because it would be dishonest. A small email-only move can be relatively modest. A full migration involving Exchange, file shares, SharePoint design, security baselines and adoption support needs proper scoping. What we will say is this: if a quote seems suspiciously cheap, check what has been left out. It is usually discovery, security setup and post-migration support, which is exactly where the value is.
Questions that affect the quote
- How many users, shared mailboxes and resource mailboxes are in scope?
- Is the source Exchange, Google Workspace, IMAP, POP, hosted Exchange or mixed?
- How much data is being migrated and where will it go?
- Are file shares being redesigned or copied as-is?
- Is Entra Connect already in place and healthy?
- Are MFA, Conditional Access and device management included?
- Is user training required?
- Is out-of-hours cutover support required?
If a provider does not ask you these questions, they are pricing blind. That rarely ends well for either side.
How to control migration cost
| Check | Why it matters | Evidence / decision required | Status |
|---|---|---|---|
| Clean up before migration | Reduces data volume and support issues. | Inactive users, redundant mailboxes, stale files. | |
| Decide the target design early | Prevents rework. | SharePoint IA, Teams structure, mail flow plan. | |
| Separate must-have from later improvements | Keeps the first project realistic. | Phase 1 and Phase 2 backlog. | |
| Pilot before bulk migration | Finds issues cheaply. | Pilot results and remediation list. |
Best commercial angle: a fixed-price assessment is easier to approve than a vague migration estimate. Use the assessment to produce the real scope, risks, timeline and implementation cost. You know exactly what you are committing to before the serious money is spent.
For the file side, Microsoft's migration planning guidance and the SharePoint Migration Tool overview are worth a read so you understand what the tooling does and does not cover.
Book a Migration Readiness Assessment
Need a realistic Microsoft 365 migration estimate? We can review your current environment and give you a clear, scoped migration proposal.
Book a Migration Readiness Assessment