Post-merger integration for the Integration Management Office
Post-merger integration (PMI) is the structured programme that takes a signed M&A deal through Day 1 readiness, the 100-day plan, functional integration, synergy delivery, and a clean handover to business as usual. This page shows the lifecycle as a BPMN process map for IMO leaders, integration consultants, and the executive sponsors who own the deal value.
By Jack Finnegan ยท Updated 21 May 2026
What post-merger integration actually is
Most PMIs run on slide decks and email threads
Four pieces of a working PMI
Pre-close planning and IMO
Stand up the Integration Management Office before close. Define the operating model, the integration thesis, the workstream structure, and the governance cadence.
Day 1 readiness
Communications, business continuity, customer/employee retention, regulatory filings. The bar for Day 1 is "nothing breaks" - integration value is built later.
Functional integration
Finance, HR, IT, operations, sales, legal. Run in parallel with explicit cross-workstream dependencies. The slowest workstream usually determines integration timeline.
Synergy tracking and close-out
Track delivery against the deal model on the agreed cadence; course-correct when workstreams fall off track; close out the IMO when the operating-model changes are in BAU.
The PMI programme as a process map
The canonical lifecycle - pre-close, Day 1, 100-day, functional integration, synergy tracking, close-out - with the explicit course-correction loop.
A post-merger integration programme as a process map
A canonical post-merger integration (PMI) programme rendered as a BPMN 2.0 process. Pre-close planning, Day 1 readiness, 100-day plan execution, functional workstreams, synergy tracking, and structured close-out.
- Pre-close: stand up the Integration Management Office (IMO) to define the operating model and integration thesis.
- Day 1 readiness: communications, business continuity, customer/employee retention, regulatory filings.
- Execute the 100-day plan - the high-priority integration workstreams.
- Run functional integration in parallel - finance, HR, IT, operations, sales, legal.
- Track synergy delivery against the deal model on the agreed cadence.
- If synergy delivery falls off track, course-correct functional integration. Otherwise integration runs to completion.
- Close out the IMO, hand operational ownership to business as usual, and capture lessons learned.
Frequently asked questions
What is post-merger integration?
Post-merger integration (PMI) is the structured programme that runs from deal close through to the completion of operating-model changes the deal thesis depends on. It typically includes pre-close planning, Day 1 readiness, the 100-day plan, functional integration across finance, HR, IT, operations, sales, and legal, and ongoing synergy tracking until the IMO hands over to business as usual.
What is the Integration Management Office?
The Integration Management Office (IMO) is the central programme function that runs the PMI. It typically combines an IMO leader (often a senior executive on a temporary assignment), workstream leads for each functional area, an analytics/PMO team for synergy tracking and reporting, and dedicated communications and change-management resources. The IMO usually runs for 12-24 months before handing off to BAU.
What goes into a 100-day plan?
The 100-day plan covers the high-priority integration workstreams that need to deliver visible progress in the first quarter post-close. Typical priorities: Day 1 communication and stabilisation, leadership team appointments, immediate cost synergies (e.g. duplicate vendor consolidation), priority customer-facing decisions, integration governance setup, and the early data collection for the deeper integration design.
How do you track synergies in PMI?
Synergy tracking compares actual run-rate cost reduction and revenue uplift against the deal-model assumptions, broken down by workstream and synergy lever. Best practice: define each synergy as a discrete initiative with an owner, a baseline, a target run-rate, and a delivery date; track progress against the baseline monthly; report at IMO steering and at the executive committee. Tracking should distinguish gross synergies from net (after one-off costs to achieve).
How does process mapping fit into PMI?
Process mapping is how the IMO makes integration workstreams visible. Each functional workstream has its own process - the migration of accounts payable from acquiree to acquirer, the consolidation of vendor master data, the merger of two HR systems. A BPMN map per workstream shows the steps, the cross-workstream dependencies, and the decision gates - which is much easier to brief, track, and course-correct than the equivalent slide deck. PMI is one of the highest-value use cases for process mapping in a typical large enterprise.
Does BA Copilot help with M&A integration?
Yes. BA Copilot speeds up the discovery work that PMIs depend on - capturing acquiree as-is processes (often poorly documented), modelling target-state operating model, and producing the BPMN diagrams that workstream leads use to run integration sprints. It does not replace the IMO's planning, synergy tracking, or governance functions; it accelerates the modelling work the IMO would otherwise do in Visio.
14 Years in BPMN
I'm Jack Finnegan. I've spent fourteen years working hands-on with BPMN, as an analyst, an engineer, and a product director, where I felt every sharp edge of legacy business process platforms.
BA Copilot is the platform I wanted on every one of these projects: AI-first process management, which treats BPMN as a first-class output rather than an export afterthought.
Make integration workstreams visible
Open the PMI lifecycle template, customise the workstream structure to your deal, and produce the BPMN maps the IMO uses to run integration sprints.