Synergy Tracking in M&A: How IT Integration Creates — and Destroys — Value

Every deal model has synergies. IT integration synergies are among the most credible — because they’re real, they’re quantifiable, and they come from actual asset consolidation rather than revenue assumptions.

But they’re also the most commonly overestimated, because the integration work required to realize them is systematically underestimated.

The IT Synergy Categories

Category 1: License Cost Synergies (Realizable in 90-180 days)

SaaS license deduplication: When two companies merge and both are using Salesforce, you cancel one. When both are using Microsoft 365 E3, you consolidate to E5. Typical realization: 60-90 days from Day 1, once user migration is complete.

Cloud optimization: Combined cloud spend is larger, which means better pricing from cloud vendors. Azure Reserved Instances, AWS Savings Plans, GCP committed use discounts — all of which require consolidated billing.

Vendor consolidation: Two companies with separate vendor relationships for the same service category (e.g., two different EDR vendors) consolidate to one. License savings plus operational simplicity.

Synergy magnitude: 20-35% of the combined IT run rate, realized over 12-18 months.

Category 2: IT Operations Synergies (Realizable in 180-365 days)

Help desk consolidation: Two separate IT help desks become one. The combined entity has more scale, which allows for better tooling and higher automation. Typical reduction: 1-2 FTE per 500 users consolidated.

Security operations consolidation: Two separate SIEMs, two separate EDR platforms, two separate vulnerability management programs — consolidated into one. License savings plus better security outcomes (fewer blind spots).

Network simplification: When the two companies’ networks are consolidated and the two ISPs are consolidated, the combined entity gets better pricing and simpler management.

Synergy magnitude: 10-20% of the combined IT run rate, realized over 18-24 months.

Category 3: IT Transformation Synergies (Realizable in 365+ days)

Cloud migration acceleration: Post-merger is often the forcing function that drives cloud migration, which reduces on-premises infrastructure costs. If the combined entity migrates to cloud faster than the individual companies would have, the resulting opex reduction is a synergy.

Application rationalization: The combined entity has fewer applications (some are retired, some are replaced). License savings plus reduced IT support burden.

Synergy magnitude: Variable. Depends on the scale of transformation undertaken.

How Synergies Get Overestimated

The error: Modeling “10% of combined IT spend” as a synergy, realized in year 1.

Why it’s wrong: IT synergies take time to realize because:

1. The integration work must be completed before synergies can be captured
2. Some synergies (like cloud optimization) require the full combined spend to be in place before the pricing improvements apply
3. IT integrations face unexpected delays — complexity is always higher than modeled

The realistic model: IT synergies are front-loaded with costs, back-loaded with savings. The cost of integration (labor, tooling, vendor transition) is concentrated in months 1-12. The savings start in month 6-12 and accelerate through month 24.

The IT Synergy Tracking Framework

Track at the Workstream Level

Assign each synergy to a specific IT integration workstream:

• License deduplication: Application Workstream
• Cloud optimization: Infrastructure Workstream
• Help desk consolidation: Operations Workstream

Track Monthly Against Baseline

Baseline: The combined IT spend of both companies in the 3 months pre-close.

Track monthly: Current IT spend vs. the pre-close baseline. The delta is the synergy realization (or the integration cost, depending on the direction).

The tracking should show:

• Total synergy target (from the deal model)
• Realized synergies to date
• Remaining synergies to be realized
• Integration costs to date (labor, tooling, vendor transition)

The Integration Cost Tracking Trap

Most IT integration cost tracking only tracks hard costs — the money spent on tools, vendor transitions, and consulting.

The real integration cost is:

• Hard costs (tools, vendor transitions, consulting)
• Internal labor cost (IT team time spent on integration instead of BAU)
• Productivity loss (users spending time on IT issues instead of their primary jobs)
• Opportunity cost (the synergies not captured because the integration took longer than planned)

For a 2,000-user integration, productivity loss alone can be $500K-$1M over the integration period. This is almost never tracked.

The 5 IT Synergy Traps That Kill Value

Trap 1: Synergy Double-Counting The deal model has “IT cost synergies” and the technology vendor is offering a “cloud optimization project” — and both are counting the same savings. The integration team needs to track which synergy is attributed to which initiative.

Trap 2: Integration Cost Underestimation The IT integration is estimated to cost $800K and take 6 months. The actual cost is $1.2M and takes 14 months. The deal model didn’t have $400K of unbudgeted integration cost, and it didn’t have 8 months of delayed synergy capture.

Trap 3: IT Synergy Attribution to Non-IT Functions The CFO models IT synergies as if they belong to the finance function. In reality, IT synergies are only captured when the IT integration work is completed — which depends on IT team bandwidth, not finance approval.

Trap 4: Not Modeling the BAU Tax During an integration, the IT team is working on integration projects. They are not working on business-as-usual improvements. The IT department’s BAU work (projects that would have improved operations in the normal course) stops during integration. This is a hidden cost that doesn’t appear in any budget.

Trap 5: Assuming Synergies Are Automatic The deal model says “IT synergies = $2M/year.” The integration team needs to actually do the work to capture those synergies. Every synergy has a to-do list. Until the to-do list is completed, the synergy is not realized.

The IT Synergy Tracker Template

The variance column tells the story. A tracker like this reviewed monthly by the IMO shows which synergies are on track and which are at risk — before the variance becomes permanent.