Post-Merger Integration Checklist: The 90-Day Plan That Actually Works

Most mergers and acquisitions are sold on the numbers. The synergy projections look clean. The deal logic makes sense on paper. Then the ink dries and someone has to actually run the integration — and that is where the wheels come off.

Post-merger integration fails more often than it succeeds. Studies consistently put the failure rate between 50 and 85 per cent, depending on how you define failure. In my experience, the failures rarely come from a bad deal. They come from poor execution in the first 90 days — when the organisation is disoriented, teams don’t yet know who they report to, and everyone is waiting for someone to tell them what happens next.

A structured 90-day post-merger integration checklist does not guarantee success. But it does replace chaos with a cadence. It gives leadership a communication rhythm, gives teams a delivery framework, and gives the integration program somewhere to point when things go sideways — which they will.

This is the structure I’ve used across integration programs of varying complexity. It is not a methodology deck. It is a working checklist.

What a 90-Day Post-Merger Integration Actually Covers

Before the checklist, a scope note. The 90-day window is not the full integration timeline. A complex post-merger integration — particularly one involving digital systems, brand consolidation, or legal entity changes — can run 12 to 18 months. The 90-day plan covers the stabilisation and alignment phase: the period where you prevent the organisation from fragmenting, establish the workstreams, and build enough momentum that the longer integration can proceed without haemorrhaging talent and trust.

The four domains that need to be addressed in every integration, regardless of deal type, are:

1. People and leadership — who is in charge, who has a role, who doesn’t
2. Brand and communications — what the combined entity is called and how it speaks
3. Operations and process — how work actually gets done day to day
4. Digital and technical — systems, data, infrastructure, and integration points

Not all four will be equally complex in every deal. A talent acquisition of a ten-person startup will have a very different technical integration burden than the consolidation of two mid-market companies with separate CRMs, codebases, and customer databases. Weight the checklist accordingly.

Days 1–30: Frame and Stabilise

The first 30 days are about preventing damage. You are not building yet. You are protecting.

Leadership and governance

• Appoint an integration lead with clear authority and a direct line to the CEO or equivalent
• Define the Integration Steering Committee: who sits on it, how often it meets, and what it decides versus escalates
• Establish a single source of truth for integration status — one dashboard, one meeting cadence, one place where decisions are logged
• Define decision rights: who approves what, and at what level does a decision require committee sign-off
• Agree on a “Day 1 message” — what employees, customers, and suppliers will hear and when

People

• Identify all roles across both organisations and flag redundancies before rumours do it for you
• Communicate the retention plan for key personnel — silence is interpreted as a threat
• Stand up an integration team: workstream leads, project coordinator, communications lead
• Schedule 1:1s between integration lead and all senior leaders within the first two weeks
• Define reporting lines for the transition period — temporary is fine, but nothing should be undefined

Brand and communications

• Audit all customer-facing and external communications to identify what needs to change immediately and what can wait
• Agree on the interim brand position: are you operating under a single brand, a dual brand, or maintaining both until a migration date?
• Draft and distribute an employee communication explaining the deal rationale, the 90-day priorities, and what employees can expect
• Identify any regulatory or contractual communications that must be sent within specific timeframes
• Establish a communications rhythm: weekly employee update, biweekly customer communication (if needed), monthly external statement

Digital and technical

• Inventory all core systems in both organisations: CRM, ERP, HRIS, financial systems, development infrastructure
• Identify Day 1 access requirements — what do people in the combined entity need access to on the first day of operations?
• Freeze any major technology projects in either organisation until integration dependencies are understood
• Appoint a technical integration lead and brief them on the 90-day scope
• Identify and mitigate immediate security risks from the integration of two separate IT environments

Days 31–60: Integrate and Align

By Day 30, the organisation should be stable enough to start building. This phase is where the actual integration work begins: merging workstreams, aligning culture, and making the decisions about what the combined entity will look like.

Operations and process

• Map the end-to-end operating model for the combined entity across all key functions
• Identify process conflicts: where both organisations do the same thing differently, decide which approach wins — or design a new one
• Rationalise the vendor and supplier list: contracts that overlap, relationships that need to transfer, agreements that need renegotiation
• Establish shared project management tooling and reporting standards across the integration workstreams
• Begin integration of financial reporting: unified chart of accounts, consolidated reporting cadence, agreed KPI set

People and culture

• Run structured listening sessions across both organisations — not surveys, actual conversations
• Identify cultural tension points early: working styles, communication norms, performance expectations, and decision-making culture often differ substantially
• Define the cultural north star for the combined entity — this does not need to be a values document, but it does need to be a clear articulation of how this organisation will operate
• Confirm the org structure for the first 12 months and communicate it — even if it will change, having a clear interim structure is better than ambiguity
• Begin onboarding integration: systems access, benefits alignment, induction programs for employees crossing between entities

Brand consolidation (if applicable)

• Complete the brand audit: all customer touchpoints, signage, digital assets, product packaging, legal documentation
• Agree on the brand migration timeline and the order in which touchpoints will be updated
• Brief internal teams and external agencies on brand transition requirements
• Update customer-facing digital properties according to the agreed timeline
• Track brand migration progress in the integration dashboard alongside operational workstreams

I’ve run this phase across a corporate rebrand involving four automotive brands and a revenue portfolio north of $120M — the temptation is always to move too fast on the visible brand work before the operational foundation is in place. Brand migration on top of an unstable operation creates customer confusion and internal noise at the worst possible time. The sequencing matters as much as the work itself.

Digital and technical

• Begin data migration planning: what needs to move, what can stay, what needs to be rebuilt
• Assess integration architecture: point-to-point integrations, API dependencies, and data flows that will be disrupted by the integration
• Establish a unified security posture: access controls, credential management, and data governance across the combined entity
• Define the long-term technology stack — this is a decision, not a default; defaulting to the acquiring company’s stack without assessment leads to avoidable technical debt
• Begin decommissioning planning for systems that will be retired

Days 61–90: Optimise and Hand Off

By Day 60, the major integration decisions should be made. The final 30 days are about embedding the changes, measuring progress, and setting the integration program up for the months ahead.

Performance and measurement

• Assess integration progress against the original success criteria defined in the project charter
• Identify workstreams that are on track, at risk, and behind — and escalate or re-resource accordingly
• Conduct a mid-point pulse survey with employees to assess sentiment, identify unresolved concerns, and surface risks before they become problems
• Report to the Integration Steering Committee on the state of play and any scope changes required for the next phase

Operational embedding

• Transition any Day 1 workarounds to permanent process: temporary reporting lines, interim systems access, and manual workarounds should have a documented sunset plan
• Confirm all regulatory filings, legal entity changes, and contractual updates are on track
• Complete financial consolidation milestones agreed for the 90-day window
• Hand supplier and vendor relationships to the appropriate owners in the combined entity

Planning the next phase

• Define the 90-to-180-day integration roadmap based on what has been learned in the first 90 days
• Update risk register with new information and change the risk posture of any items that have been resolved or escalated
• Document decisions made during the 90-day window in a decision log — this will matter six months later when someone asks why a call was made
• Brief the incoming leadership team or operational owners on integration status, outstanding items, and known risks

Handover and documentation

• Produce a 90-day integration summary: what was done, what was not done, and why
• Create a handover pack for each workstream lead: status, decisions, open items, and recommended next actions
• Conduct a retrospective with the integration team — what worked, what did not, what would you do differently
• Archive all integration documentation in a single location accessible to the ongoing program team

Every integration program I have run has found something unexpected in the first 90 days — a system dependency nobody documented, a customer relationship that had been managed entirely by one person who left in week two, a financial commitment that did not appear in the original due diligence. The checklist does not prevent surprises. It creates the structure that lets you absorb them without losing the program.

Where Post-Merger Integrations Fall Apart

In almost every integration program that goes off track, one of the following is the root cause.

No single integration lead with real authority. Integration by committee is integration by consensus, and consensus is slow. Someone needs to own the program, make calls when agreement stalls, and carry the accountability.

Communication is too slow or too corporate. Employees fill information vacuums with rumour. The communication cadence needs to be relentlessly consistent, and the messages need to be honest — even when honest means “we don’t know yet.”

The technology integration is underestimated. Every organisation has more technical debt and more undocumented system dependencies than its own IT team realises. Allow significantly more time and resource for digital integration than the initial estimate suggests.

Culture is treated as an HR program. Culture integration is an operational challenge that touches every workstream. If it is delegated entirely to HR and treated as a parallel track, it will not land. It needs to be embedded in the operational decisions being made across the 90 days.

The 90-day plan tries to do too much. The goal of the first 90 days is stabilisation and alignment, not full integration. Teams that try to compress a 12-month integration into 90 days tend to produce an organisation that looks integrated on the surface and is fragmented underneath.

Using This Checklist

This is a starting framework, not a final specification. Every integration program has its own complexity, deal context, and organisational constraints. The right approach is to adapt this checklist to the specific deal and use it as the foundation for the more detailed workstream plans that sit underneath it.

If you are currently planning or managing a post-merger integration and want a second opinion on the approach, I am happy to have a conversation. The work I do is typically as a contract integration lead or fractional program director — brought in to run the integration alongside an existing leadership team, or to stabilise a program that has gotten away from them.

Get in touch →

---

Aaron Darke is a Senior Project and Program Manager with 25+ years’ experience running complex integrations across technology, brand, and operations. He is available for contract engagements across Australia, New Zealand, the United States, and Mexico.