The integration that dismantles the deal case.

21.07.2026

3 min read

The deal case promises value. The integration delivers friction. If Day-1 to Day-100 is treated as an IT migration only, the thesis quietly collapses: duplicate systems, unclear ownership, delayed customer promises.

Key Takeaways

Thesis: Integration is the real deal. Closing day is only the starting gun for the most expensive phase.
Three Killers: unclear system ownership, benefit timelines without stage gates, and customer promises without an operating model.
Stage-Gate: Day-1 stability, Day-30 decision rights, Day-100 measurable system and process convergence-or thesis review.

What is Post-Merger Integration? Post-Merger Integration (PMI) is the controlled merging of systems, processes, data, and decision rights after closing. It tests whether the deal case’s value promises hold up in operations-using stage gates, ownership, and measurable convergence instead of mere project status.

Due diligence often speeds up: GenAI summarizes data rooms and synergy models kick in earlier. The integration work, however, remains physical. The pain of integration stays physical: people, contracts, data models, security baselines. That’s where the deal case topples when the slide deck is optimistic and operations are realistic.

Where the Thesis Silently Collapses

Three fracture lines appear in almost every post-merger IT landscape. First, the system landscape: two ERPs, two identity stores, two ticket universes. Second, decision rights: who halts a migration when the customer suffers? Third, the benefit clock: cost-take-out without process ownership breeds shadow work.

The classic mistake is parking integration as a project plan behind the signing. The thesis needs a negative list before closing: which systems stay dual, which must converge, and which customer processes are untouchable in the first 100 days.

In integration programs, the biggest value destroyer is often the delayed decision at the interface of the two legacy organizations. Speed without ownership is acceleration in the wrong direction.

Stage-Gate

Day-1 · Day-30 · Day-100

Stability, decision rights, measurable convergence. Miss one gate and the case slide is still just a slide.

Stage-gates that protect the deal case

Day 1: Identity, access, critical customer processes and security baseline. No big-bang ERP at closing weekend without a rollback.

Day 30: Decision rights for integration: budget stop, scope freeze, escalation owner per domain (data, security, customer, finance). Without named owners, the steering committee remains a status forum.

Day 100: Measurable convergence: which systems decommissioned, which processes single-threaded, which case effects cash-effective. What isn’t measurable must be removed from the thesis. Pushing to Q+2 without an update is self-deception.

“Deal assumptions are assumptions. Integration is the test. Whoever fails to steer the test has only signed the deal.”

What must be decided before signing

Timeline – Integration control

Pre-close: Light target operating model – domain owners, dual-run window, customer promises that must not break.
0–30 days: Stability and decision rights before feature roadmap. Kill switch for risky migrations.
30–100 days: Convergence with gate reviews. Thesis update if scope or timing breaks – publicly in the integration board.

Counterpoint: some deals deliberately need dual-run because customer contracts and regulation cap the pace. That’s legitimate. Dual-run without an end date and without a cost owner, however, is a silent thesis extension – and that’s where the deal case burns from within.

In practice, every benefit line in the case needs an integration owner with stop authority. Cost take-out without a process owner becomes an Excel fiction. Revenue levers in the case that lack a shared customer journey and data foundation remain press-release promises.

Data migration deserves its own negative list. Which master data stays dual, which must become the single source of truth, and which reports may remain incomplete for 100 days? Without that clarity, every dashboard escalates into a political weapon.

Security and identity are day-one obligations. Duplicate accounts, orphaned service accounts and unclear privileges later eat more budget than a cautious dual-run phase. Skimping here means paying in incidents and audit findings.

Customer communication is part of integration, not an appendix. Which promises from the deal announcement are operationally sustainable must be clear before the first joint sprint. Broken SLAs destroy the case faster than double license costs.

Frequently Asked Questions

Why does the deal case so often derail during integration?

Because benefit promises are optimistically modeled pre-closing and operated post-closing without stage gates or ownership. The friction lies in systems and decisions, not in the press release.

What absolutely belongs on the negative list before closing?

Systems and customer processes that may or must remain dual for the first 100 days. Plus: what will explicitly not be migrated. Without a negative list, scope creep emerges in operations.

Who needs to be on the integration board?

Domain owners with stop-rights: Data, Security, Customer, Finance, Tech. Status reporters without decision mandates are insufficient.

How should dual-run be handled?

With an end date, cost owner, and exit criteria. Dual-run without these three points is a hidden thesis expansion.

When must the thesis be formally revised?

As soon as a stage gate fails and scope or timing breaks the case assumption. Delaying without an update is self-deception with Excel.