Microsoft 365 migration project economics: pricing, timelines and where the budget actually goes

The first number in an M365 migration quote is rarely the number that lands on the final invoice. Not because vendors are hiding costs, most aren't, but because the scope of an M365 migration expands in ways that are entirely predictable and almost never reflected in the initial estimate. This guide maps the real budget categories, typical AU day-rates, timeline expectations by migration type, and the specific decisions that determine whether a project comes in on scope or blows out.

What you're actually migrating

The phrase 'M365 migration' covers a wide range of work. The most common projects in the Australian market are:

• Tenant-to-tenant migration: one Microsoft 365 tenant to another, typically in M&A or divestiture. Highest complexity, longest timeline.
• On-premises Exchange to Exchange Online: legacy Exchange 2010/2013/2016 to Exchange Online. Common for businesses that deferred cloud migration.
• Google Workspace to Microsoft 365: switching productivity suite entirely. Data complexity varies significantly by how mature the Google environment is.
• File server to SharePoint: on-premises file shares migrated to SharePoint Online. Often runs in parallel with an Exchange migration.
• Hybrid configuration to cloud-only: cleaning up an existing Microsoft 365 hybrid deployment and moving identity management fully to Entra ID.

Most businesses are actually combining two or more of these. That's where scope grows.

Day-rates and effort: what to expect in AU market

Microsoft consulting services in Australia are priced by seniority. An L1 consultant (delivery, configuration, testing) runs $1,200–$1,600 per day. An L2 senior consultant (architecture, complex configuration, escalation) runs $1,800–$2,400 per day. An L3 principal or MVP-level (tenant design, edge case resolution, governance) runs $2,800–$4,000 per day. These are market rates as of early 2026 for capital-city engagements, regional work may carry a travel component on top.

Project management is typically billed separately, at $1,200–$1,800 per day for a PM with technical background. Don't accept a project manager who doesn't understand Microsoft 365 at a working level, they'll create more coordination overhead than they save.

Typical project budgets by migration type

These are indicative budgets for a 100-seat business migrating from a single source with a competent delivery team. Adjust upward for complexity, legacy technical debt, and scope additions.

• Exchange hybrid to Exchange Online: $15,000–$35,000 AUD. The range is driven by hybrid configuration complexity and the state of on-premises Active Directory.
• File server to SharePoint (single site): $20,000–$50,000 AUD. The lower end assumes clean file structure and minimal permission complexity. Legacy mapped drives with deeply nested NTFS permissions routinely sit at the top of the range.
• Google Workspace to Microsoft 365 (email + Drive): $30,000–$60,000 AUD. Google-to-Microsoft calendar data is lossy. Budget for user communication and re-training.
• Tenant-to-tenant (M&A): $60,000–$150,000+ AUD. Scope varies enormously based on whether Active Directory federation, identity, telephony and compliance history all need migration.

Where projects blow out, the five predictable scope expansions

Across most M365 migration engagements, the same five categories drive cost beyond the original estimate.

1. 1Discovery finds more than expected. Pre-migration data discovery almost always surfaces more data volume, more permission complexity, and more legacy applications with undocumented integrations than the initial scoping assumed. A two-day discovery phase before committing to a fixed quote is the single most reliable way to contain this.
2. 2Third-party app re-integration. CRM, finance, HR and document management systems that are integrated with Exchange or Active Directory need re-configuration after a migration. Each integration is typically a half-day to two-day effort that wasn't in the original scope.
3. 3Identity remediation. A migration is a forcing function for cleaning up Active Directory or Entra ID. Guest accounts, inactive users, stale groups, duplicate accounts, all need remediation before migration. This work is almost never included in a migration quote.
4. 4Parallel running costs. The period after cutover where the source system is still running (for fallback, for users who weren't ready, for compliance holds) costs real money in licences, infrastructure and admin time. Budget explicitly for this period.
5. 5Adoption and training. End-user disruption is the most underestimated cost category. Users who can't function during or after cutover generate helpdesk volume, productivity loss and sometimes executive escalations. Structured training, a communication program, and a dedicated adoption sprint in the first two weeks post-cutover all cost money, and all pay back more than they cost.

Timeline expectations, what's realistic

Every vendor proposes an aggressive timeline and most projects slip. Here are realistic timelines for a 100-seat business with a competent team and no major blockers.

• Exchange hybrid to cloud: 6–10 weeks from kick-off to decommission of on-premises Exchange
• File server to SharePoint (single site): 8–14 weeks including discovery, architecture design, wave migrations and adoption period
• Google to Microsoft 365: 10–16 weeks, the extra time is user readiness and parallel running
• Tenant-to-tenant: 16–26 weeks for a clean M&A case; up to 12 months for a divestiture with complex compliance requirements

Add four weeks if Active Directory needs significant remediation before the migration starts. Add eight weeks if the business has a hard change freeze (common in March/April for financial year-end clients). Subtract four weeks if the migration is Exchange-only with no file share component and a clean source environment.

Getting the quote right

Request fixed-price quotes only after a paid discovery phase. Time-and-materials quotes protect the vendor, not the buyer. Ask for the quote to break out work by phase (discovery, design, build, migrate, cutover, adoption), by resource type, and by assumption, the list of assumptions underlying the price is where the scope risk lives. Any assumption that turns out to be wrong is a scope change.

Ask specifically: 'What is not included in this quote?' A competent vendor will produce a clear exclusions list. A vendor who says 'everything is included' either hasn't scoped the project carefully or will use change control aggressively once work starts.