Post-merger integration: deciding how far to integrate, and doing it

First decide how far to integrate

Not every acquisition should be integrated fully. A long-standing framework from Philippe Haspeslagh and David Jemison's Managing Acquisitions (1991) frames the choice around two questions: how much the expected value depends on combining the two organisations (strategic interdependence), and how much it depends on the target keeping its own way of working (autonomy).¹ The answers point to four broad approaches:

The choice is rarely uniform. Finance and compliance may be absorbed on day one while product and engineering are preserved for a year. Write the choice down by function; it is the brief for every integration workstream.

The integration management office

An integration management office (IMO) runs the programme: the plan, the interdependencies, the issue log, the synergy tracking and the reporting to the steering committee. It works best when it is small, has a senior leader with authority on both sides, and owns the calendar rather than the content. Each functional workstream (finance, HR, IT, sales, operations, legal) has a named lead who owns the content and the result.

Synergies: plan them, track them, cost them

Synergies are the reason many acquisitions are priced the way they are, and the part most often missed. They become manageable when each one has:

• A baseline: the cost or revenue before integration, agreed with finance.
• An owner: a manager who will be measured on it, not the deal team.
• A date and a measure: when it will show in the accounts, and how.
• A one-off cost: severance, system migration, contract exits, rebranding. Integration costs that are left out of the case make every synergy look cheaper than it is.
• The dis-synergies: customers lost to disruption, people who leave, duplicate costs during migration.

Cost synergies are generally easier to plan and track than revenue synergies, which depend on customers and on sales teams changing behaviour. Track the two separately and be more conservative with the second.

Sequencing

• Day 1: continuity and control. See Day 1 readiness.
• First 100 days: the operating model decided by function, quick wins taken, the integration plan funded, key people retained.
• Months 3 to 18: the heavy lifting. Organisational changes, system migrations, contract consolidation, the synergies that need time.
• Close-out: the IMO hands remaining work to the line and reports what was delivered against the case.

IT integration

IT is usually the longest workstream and the one with the most dependencies. A practical order:

1. Identity and access

One way for people to sign in to what they need, with the acquirer's security controls applied. Directory trust or federation first, migration later. Until the target's security posture has been assessed and remediated, connect identity, not networks.

2. Email and collaboration

Calendars, shared documents and a combined address book make the organisation feel like one. Domain and mailbox migrations are well understood but disruptive; schedule them with the business.

3. Security posture

Bring the target's endpoint protection, monitoring, vulnerability management and incident response onto the acquirer's standard, starting with the findings from diligence.

4. Applications

For each application in both companies: keep, retire, migrate or merge. Decide by business process and operating model, not by which system is technically better. Watch licences: some terminate or need consent on a change of control, and some cannot be transferred between legal entities.

5. ERP and data

Moving finance, supply chain and customer data onto one ERP is usually the last and largest step. Data quality, chart-of-accounts mapping and historical reporting decide the timeline more than the software does.

People and culture

• Identify the people who carry critical know-how during diligence, especially in engineering and operations, and agree retention before closing.
• Communicate decisions as soon as they are made. Uncertainty is what makes good people leave.
• Be explicit about what is not changing. In a preservation or symbiosis integration, that is most of the message.

Customers

Customers notice integration through invoices, account managers, support lines and product changes. Plan each change from the customer's side, tell them before it happens, and watch churn and support volumes weekly during migrations.

Plan before closing

Integration planning starts during diligence and accelerates between signing and closing. Until closing, the buyer cannot direct the target's business, and competitively sensitive information is shared only through clean teams under counsel's guidance. What can be done is substantial: design the operating model, build the synergy case, draft the Day 1 and 100-day plans, and map the target's systems from the inventories in the data room.

The operating model, function by function

Writing down the end state for each function turns the integration approach into decisions people can act on:

A synergy register

Each synergy gets a row with: description; type (cost or revenue); baseline; target run-rate; one-off cost to achieve; owner; the month it should start to show; how it will be measured; and its status. Finance signs off the baseline and the measurement, so the register reports the same numbers as the accounts.

Integrating add-ons into a platform

Private equity platforms that buy several companies benefit from a repeatable playbook rather than a new programme each time: a standard Day 1 checklist, a fixed sequence for joining the group's finance, identity and security, a template synergy register, and a small team that has done it before. Each add-on is assessed against the playbook during diligence, so its exceptions (an unusual ERP, an unsupported system, a contract that blocks consolidation) are known and costed before signing.

Cyber risk during integration

Integration temporarily widens the attack surface: new connections between networks, new accounts, migrations, and employees who are unsure which emails are genuine. Keep the target's environment separate until its security posture is understood, bring it up to the acquirer's baseline before connecting, and expect phishing that imitates the new owner.

Measuring the integration

• Value: synergies delivered against the register, and one-off costs against budget.
• People: retention of named key people; voluntary attrition compared with before the deal.
• Customers: churn, support volumes and satisfaction during migrations.
• Milestones: the systems and organisational changes delivered on time.

Common pitfalls

• Integrating everything by default when the value depended on autonomy.
• Synergy targets owned by the deal team rather than by managers.
• Integration costs left out of the business case.
• Connecting networks before assessing the target's security.
• Choosing systems by technical preference instead of by operating model.
• Losing the engineers who understood the target's product.

Checklist

• Integration approach written down by function (absorb, preserve, symbiosis, hold).
• IMO leader named, with workstream leads on both sides.
• Synergy register with baseline, owner, date, measure and one-off cost.
• IT sequence agreed: identity, collaboration, security, applications, ERP and data.
• Change-of-control and transfer restrictions in software licences listed.
• Key people identified and retention agreed before closing.
• Customer-facing changes planned and communicated in advance.