How to Estimate Microsoft 365 Migration Costs Pre-LOI (Without Admin Access)

Every M&A deal team has had this conversation. The bid is due Friday, the M365 integration cost is the largest line in the synergy model, and the only data anyone has is a spreadsheet the seller put together. No admin access. No scans. No way to verify. This is the framework for putting a defensible number on the table anyway. 

The stakes are real. By the time your IT team finally gets Global Admin in the target tenant, the bid has already gone in. The price is locked. The escrow is sized. The TSA (Transition Services Agreement) clock is running. No wonder migration costs in complex deals routinely blow by 3 to 6x. Corp dev built the model on whatever the seller chose to share, with no real way to verify it. 

So, this is not another post-close cost-modeling exercise. It is a pre-LOI (Letter of Intent) bid-pricing framework, written for the person who must commit to a number before any real tenant-level data validation or technical analysis has been performed. 

Pre-LOI vs. Post-Signing M365 Cost Modeling 

Pre-LOI is a fundamentally different problem from post-signing cost modeling. You’re bounded by contractual access, not technical capability. Your numbers feed valuation and TSA terms, not project budgets. If you miss a cost line, you can’t go back and fix it with a tool. Your only remedies are reps, warranties, escrow, and TSA clauses. 

The data consistently shows a clear pattern across failed M&A deals. A large majority of deal failures are driven by poor integration execution, and a significant portion of market value can be lost within the first few months after closing. Research also highlights that most of the intended value in mergers is often destroyed during the integration phase rather than at the deal stage itself. The common issue behind this is timing: key decisions around purchase price, transition service agreements, integration budgets, and go-live timelines are finalized before teams have real access to validate whether the underlying assumptions are actually correct. 

Why You Can’t See the M365 Tenant You’re Buying 

Microsoft 365’s tenant isolation is doing exactly what it’s designed to do. It stops cross-tenant data exposure. Unfortunately, that same boundary also stops you from seeing the tenant you’re about to buy. 

There is no “due diligence mode.” No read-only auditor role. No anonymized export. Compliance Manager, Purview, and Secure Score all need active admin roles you don’t have. 

What you actually have pre-deal is an NDA (Non-Disclosure Agreement), a curated VDR (Virtual Data Room) , two to four weeks of calendar time, and a few scheduled interviews with seller IT. Every claim about user counts, mailbox sizes, license utilization, security posture, compliance, shadow IT, and hidden Power Platform dependencies is mediated through seller self-report. 

And here’s the part nobody likes to say out loud. In many mid-market deals and PE roll-ups, the seller doesn’t fully understand their own environment either. Sometimes the people who do know the most have active reasons not to tell you: deal-completion bonuses, retention worries, or plain reluctance to document their own technical debt. Your bid model has to live inside this reality; not pretend it doesn’t exist. 

Proxy Estimation Framework for Pre-LOI Bid Pricing

You can’t run scans, so you build from proxies and ranges. Never point estimates. Start with a baseline of user count × workload count × complexity multipliers, then apply industry multipliers: 1.5 to 2x for regulated industries, 2 to 3x for financial services, and 2 to 2.5x for pharma. Always express the bid as a range with a stated confidence level, and reserve 30 to 50% contingency for complexity that will only show up post-close.  
 
Size the escrow holdback against the upper bound of the range, not the midpoint. And use M&A-specific per-mailbox pricing of $12 to $25, which is 2 to 3x what a standard tenant migration costs. 

Double-Licensing: The Line Most Deal Models Skip 

Licenses are tied to tenant ID. They don’t transfer. So during migration, your users often need active licenses in both tenants at once. On top of that, Microsoft’s $15/user add-on migration license sits on top of E3/E5 on both sides. 

The math gets ugly fast. For a 5,000-user E3 migration, double licensing adds $150K to $450K over 2 to 6 months of overlap. For a typical 600-user M&A migration, the documented cost is $230,400+ over six months. Most deal models miss this entirely. 

What to do about it: put a real double-licensing line in the model with the specific add-on SKU, price 2 to 6 months of overlap explicitly, and start a conversation with Microsoft about a bridge EA. CSP monthly licensing also gives you flexibility during the transition. 

Specialist Consulting Costs in M&A Migrations 

M&A migrations almost always need specialist consulting outside both the buyer’s and seller’s in-house bench. The usual suspects: Power Platform rebuilds, Teams telephony porting, Purview compliance reconstruction, hybrid Exchange remediation, and Intune device re-enrollment. Specialist rates are high because specialist expertise is scarce. 

The case everyone in this space tells is the same one. A Fortune 500 manufacturer spent $1.8M on emergency consulting to rewrite a single payroll workflow discovered 48 hours before close. It was a citizen-developer Power Automate flow nobody had inventoried, nobody had priced, and that absolutely could not be allowed to break at cutover. That kind of surprise eats the contingency line. 

Here’s the move: build the consulting line by workload, with named specialists and pre-identified rate cards. Flag any niche skill, like telephony or industry-specific compliance, for premium budgeting now. 

TSA Extension Fees in M&A Tenant Migration 

When migration overruns the TSA, which statistically it does, sellers charge 1.5 to 3x the base TSA rate as extension fees. A 12-month TSA at $500K/month with a three-month extension is $2.25M to $4.5M on top of everything else. Most deal financials never model it. Sellers want migration done; the extension fee is a penalty, not a service. 

The fix: negotiate TSA terms with realistic timelines and a 30 to 50% buffer. Price extended TSA risk as a probability-weighted scenario. And lock in extension rates at signing, because once you’re at end-of-TSA, all the leverage has shifted to the seller. 

Productivity Loss at Cutover 

Post-cutover, users lose 1 to 4 weeks of productivity. The drivers are familiar: Outlook profile rebuilds, MFA re-registration, Teams cache problems, OneDrive re-sync, broken sharing links, and plain change fatigue. Helpdesk tickets spike 3 to 5x for 2 to 4 weeks. Productivity drops 5 to 15% for the same window. 

For a 5,000-user organization at $100K fully – loaded average cost, that’s $1M to $6M of value going out the door, and most deal models don’t have a line for it. 

What to do about it: put productivity loss in the financials explicitly, fund a hyper-care program, and phase migration so the impact spreads across quarters instead of landing in one bad month. 

Hidden Dependency Surcharges 

Every pain point you don’t surface pre-deal is a potential surcharge later. One undiscovered litigation hold can force you into third-party copy-migration tooling. One compliance gap can trigger specialist consulting. One Power Platform dependency can cost weeks of rebuild time. These compounds unpredictably, which is exactly why the contingency line and the escrow holdback exist. 

How to Size M365 Data Volume Without Scanning 

Volume is the second axis of the bid, and you can’t read seller telemetry directly. What you can do is convert each volume input into a specific data-room request. 

Mailbox Volume Without Admin Access 

Ask for mailbox-size distribution histograms, not averages. Long-tail mailboxes drive cost. 

SharePoint Storage and Version History 

Ask for site-collection storage with version-history overhead broken out separately. Version bloat is often 2 to 3x the visible content size. Ignoring it under-prices both migration time and double-licensing duration. 

OneDrive Per-User Distribution 

Don’t just look at total tenant size – look at how data is distributed per user. A small group of heavy users creates most of the migration risk. 

Teams Content and Private Channel Sprawl 

Ask for full Teams channel count, including standard, private, and shared channels. Private and shared channels introduce additional complexity in migration and compliance handling 

Archive Mailbox and PST Discovery 

Ask for the archive-mailbox inventory and any PST (Personal Storage Table) landscape data. PSTs sit outside the standard mailbox cost model and consistently surface as a post-close surprise when nobody asked pre-deal. 

Multi-Geo Footprint 

Ask for the satellite geo location list. Each satellite adds discrete scope and may turn into an architecture incompatibility you can’t price as a simple per-user line. 

License Rationalization: How M365 Migration Pays for Itself 

This is the slide CFOs (Chief Financial Officer) actually care about. License rationalization routinely funds entire integrations. 

One real example: an integration where duplicate Power BI Pro seats alone saved enough to fund the complete project. That’s not a rounding error. That’s the difference between an integration that drags on IRR (Internal Rate of Return) and one that earns its own keep. 

Reported headcounts usually diverge 20 to 40% from licensed users. Licensed users diverge again from people who’ve actually signed in within the last 90 days. Pre-deal, request three inventories and reconcile them yourself: HR-system active employees, Entra ID users with license assignments, and 90-day sign-in activity. 

The reconciled active-user number is your real bid denominator. The gap between licensed and active becomes a negative cost line in the model, the rationalization credit. Surfaced pre-deal, it’s a price-adjustment lever. Surfaced post-close, it’s just a write-off. 

E5 Sprawl: Premium SKU Without Utilization 

E5 licenses get assigned all the time without anyone actually using the E5-only features like Defender, Purview Premium, Power BI Pro, or Teams Phone. Ask for a feature-utilization report alongside the license inventory and put the downgrade-to-E3 opportunity in the bid as another negative line. 

Service accounts and shared mailboxes also bloat the licensed count without representing real migration scope. Net them out of your denominator. 

The Pre-LOI Bid Model Skeleton 

Here’s what a defensible pre-LOI bid looks like. Every line is a range, and every range carries a stated confidence level. 

Start with per-mailbox migration at $12 to $25 reflecting the M&A premium, then add double-licensing for 2 to 6 months of overlap with the explicit add-on SKU ($150K to $450K for 5,000 users; $230K+ for 600 users). Layer in specialist consulting by workload with named rate cards, plus a reserve sized against the $1.8M Fortune 500 precedent.  

Add a TSA-extension probability-weighted scenario at 1.5 to 3x base rate, a productivity-loss provision at 5 to 15% of fully-loaded cost for 2 to 4 weeks ($1M to $6M for 5,000 users), and a hidden-dependency contingency at 30 to 50% of baseline. 

Then, on the credit side: a license rationalization credit (the Power BI Pro story) and an E5 downgrade credit (premium SKU sprawl), both as negative lines. Finally, reserve against inherited audit and true-up exposure, since prior Microsoft audit history, SAM engagements, and unreconciled CSP (Cloud Solution Provider) billing all flag elevated post-close audit probability. And reserve 2 to 3% of inherited CSP run-rate (~$200K per $10M of CSP business) for billing reconciliation. 

Built this way, the bid produces a range, not a point estimate. An escrow recommendation tied to the upper bound. A defensible IRR floor for the IC. All pre-signing. 

PE firms have started baking minimum Secure Score (20+ points) requirements directly into term sheets, turning a technical assessment into a purchase-price adjuster. License rationalization works the same way. Surface it pre-deal and it becomes a deal-term lever. 

The M365 Pre-Deal Data Room Request That Backs This Bid 

Pre-deal cost confidence comes from artifacts, not interviews. Here’s the minimum set: 

• License inventory by SKU plus a feature-utilization report. 

• HR active-employee list, Entra ID user export with license assignments, and 90-day sign-in activity. 

• Mailbox-size distribution and archive/PST inventory. 

• SharePoint site-collection storage with version-history breakdown. 

• OneDrive per-user storage distribution 

• Teams channel inventory, including private and shared channels. 

• Multi-Geo satellite-geo list. 

• Power Platform environments, flows, and apps by run frequency and owner. This is how you find the next $1.8M payroll flow before it finds you. 

• Microsoft contract documents (EA, CSP, MOSP) with renewal dates, true-up history, and any open audit correspondence. 

• TSA draft with proposed timelines, exit conditions, and extension pricing. 

Pre-qualifying this request set against the master DD pain-point matrix surfaces 60 to 70% of integration risks before signing, when you can still price them into the bid, into SPA reps and warranties, or into the escrow holdback. 

Closing Thought 

Pre-deal is where M365 migration pain is bought, not built. The pre-LOI bid model is where you decide whether to price that pain in, push it back through the SPA (Sale and Purchase Agreement), or quietly eat it after close. The deals that still hit IRR a year later? Their bids did the first two, consistently. 

Once You Have Admin Access: What to Do Next 

Everything above is built for the pre-LOI window, when you can’t run scans, can’t query Graph, and can’t validate seller claims directly. The moment Global Admin is in your hands, the problem changes. You’re no longer pricing what you can’t see. You’re executing against what you finally can see. 

If you’ve crossed that line and want the detailed execution guides for what comes next, these pieces are written for the post-admin-access reader: 

• For post-signing cost modeling and tenant consolidation: The Real Cost of Microsoft 365 Tenant Consolidation in M&A . 

• For MSP-side licensing advisory and the four most common M&A licensing traps: Four Licensing Traps MSPs Must Avoid in M&A Tenant Migration  

• For seller-side proxy data and inventory mechanics by workload: Teams Pre-Migration Inventory ,  SharePoint Site Inventory Gaps , OneDrive Pre-Migration Inventory , Exchange Online Inventory Gaps and Power BI Pre-Migration Inventory  

• For the structural “no admin access” framing that anchors the entire pre-deal series: The M365 Pre-Deal Due Diligence Problem. 

Use the framework above to win the bid. Use these guides to deliver the integration.