A post merger Microsoft consolidation saves USD 2.4M

This case study is an anonymised composite drawn from representative engagements. It names no real parties and uses approximate figures to illustrate typical outcomes.

This post merger microsoft consolidation saves usd 2.4m case study shows how reconciling two Microsoft estates before the true up removed double spend and avoided a repricing trap. Microsoft is consistently among the highest audit risks a buyer inherits, and a merger creates overlap that an Enterprise Agreement true up can quietly turn into cost.

Inside the post merger Microsoft consolidation saves USD 2.4M case study

Situation

This case study follows a merger of two mid sized services firms in North America, each with around 1,500 employees, combining into a single business. Both companies ran Microsoft heavily, each under its own Enterprise Agreement, with overlapping Microsoft 365 plans, per user and per device CALs and server licensing. The integration team was focused on operations, and the next true up anniversary was approaching for one of the agreements.

The combined business engaged us to reconcile the Microsoft estate and capture the consolidation opportunity safely, because a careless integration would have inflated the true up rather than reducing the run rate.

Risk faced

The immediate risk was the true up. Combining the two workforces without reconciling the agreements would have captured the combined growth at the next anniversary at list assumptions, producing a large unplanned bill. Beyond that, the two estates carried significant overlap: duplicate Microsoft 365 plans, mismatched CALs and parallel server licensing that the combined business was effectively paying for twice.

The trap was consolidating before reconciling. Moving users onto a single agreement without knowing the true combined position would have triggered the true up at list and risked breaking access for critical users.

Approach

We reconciled first. We built the combined Microsoft position across both companies, deduplicated users against a single combined directory, and identified where plans, CALs and server licensing overlapped. With the position in hand, we modelled the combined demand and timed the consolidation against the agreement anniversaries so the combined volume was negotiated rather than defaulted.

We then sequenced the consolidation to protect operations, removing the duplicates and right sizing the plans onto a single agreement at better volume terms, with critical users migrated only when their access was assured.

Outcome

The reconciliation and consolidation removed roughly 2.4 million dollars of run rate. The duplicate Microsoft 365 plans were retired, the CALs were right sized to the combined workforce, and the two Enterprise Agreements were consolidated into one at improved terms. The true up that would have captured combined growth at list was instead negotiated on combined volume, turning a repricing risk into a saving.

Because the savings sat on a reconciled estate, they held rather than reversing at the next renewal. The combined business also gained a clean Microsoft position that was defensible in any future true up or audit.

Lessons for buyers

The most common Microsoft surprise after a merger is not an audit; it is a true up that captures combined growth at list. Reconciling the combined position before consolidating is what turns that risk into a saving. Cutting spend before reconciling produces savings on paper that reverse at the next renewal.

The lesson is to reconcile before you cut, time consolidation against the agreement anniversaries, and negotiate from combined volume. Done in that order, post merger Microsoft consolidation is one of the most reliable software synergies available.

This outcome is the work of our integration and consolidation service, applied to the method in the license reconciliation guide. For the questions buyers ask most, see the FAQ below.