This post-merger integration checklist is built for a private equity add-on: a platform company buying a smaller business and folding it in during the first 100 days. It is organised by phase (before close, Day 1, the first 30 days, days 31 to 100) and by workstream, and every item has an owner and the evidence that proves it is done. Use it as the working document for the integration lead and the weekly review, not as a reading list.
Two rules make any M&A integration checklist useful. First, every line has one owner on the company side, even when an adviser does the work. Second, an item is closed by evidence, such as a signed decision, a reconciled report or a retired system, never by a status colour.
How to use the post-merger integration checklist
- Start from the value creation plan. Mark which items protect a number in the deal model (revenue retention, cost synergy, margin) and run those first.
- Cut what the thesis does not need. An add-on that keeps its brand and product does not need its website, CRM and finance stack merged in the first 100 days. Strike those rows and write down why.
- Assign owners before close. If a row has no owner on Day 1, it will not have one on day 30.
- Review weekly on one page. Decisions made, decisions blocked, risks with owners. The checklist is the source; the page is the summary.
Before close: the integration plan in four weeks
| Item | Owner | Evidence it is done |
|---|---|---|
| Integration thesis written: what gets combined, what stays separate, and why | Deal partner and platform CEO | One page signed off by both |
| Synergy case split into lines, each with one owner and a measurement method | Platform CFO | Synergy tracker reconciled to the deal model |
| Integration lead named, with the hours they will spend on it each week | Platform CEO | Named person, calendar blocked |
| Key people list for the target: who holds customer, product and system knowledge | Target CEO with HR | List with retention approach per person |
| Top customers list with relationship owner on each side | Heads of sales | Top 20 accounts mapped to named owners |
| Systems inventory for the target: CRM, billing, ERP, payroll, identity, hosting, key SaaS | Platform IT or CTO | Inventory with contract end dates and admin owners |
| Day 1 legal and access requirements: bank mandates, signatories, domains, admin credentials | Platform CFO and IT | Transfer plan per item with a date |
| Communication plan per audience: employees, customers, suppliers, partners | Platform CEO | Drafted messages, sender per audience, send time |
| Integration budget agreed, including advisers and one-off system costs | Platform CFO | Budget line approved by the board |
Day 1 integration checklist
Day 1 is about continuity. Nothing should break, everyone should know what changed for them, and the decisions that cannot wait should have owners.
| Workstream | Item | Evidence |
|---|---|---|
| People | All-hands at the target led by both CEOs; manager talking points sent the same hour | Session held, FAQ published internally |
| People | Retention conversations with the key people list started | Conversations logged, offers approved where needed |
| Customers | Top accounts contacted by the person they already know | Contact log for the top 20 |
| Customers | Customer-facing message live: website notice, support macro, sales talk track | Published and shared with every customer-facing team |
| Finance | Payroll, supplier payments and invoicing run without change | First cycle completed with no failures |
| Finance | Bank mandates and approval limits updated | Signed mandates |
| IT and security | Admin access to every critical system held by the platform; departed founders' access reviewed | Access review signed off |
| Governance | Decision list for the first 30 days with owners and dates | List circulated to the leadership team |
Days 2 to 30: the decisions that come before any migration
The first month is for decisions. Most failed add-on integrations started migrating systems before agreeing what the combined company would measure.
| Workstream | Item | Owner | Evidence |
|---|---|---|---|
| Leadership | Who runs each combined function decided and announced | Platform CEO | Org chart published |
| Commercial | Shared definitions of customer, opportunity, pipeline stage, churn and ARR or revenue | RevOps or sales operations lead | Definitions document signed by sales, finance and customer success |
| Commercial | Pricing and discount authority for both sales teams | Head of sales with CFO | Written policy |
| Commercial | Cross-sell motion defined: which products, which accounts, who sells | Head of sales | Target account list with owners |
| Systems | Decision on which CRM, billing, ERP and data model survive, with retirement dates for the others | CTO or IT lead with CFO | Decision log entry per system |
| Finance | Reporting calendar and chart of accounts mapping for the first combined month | CFO | Mapping approved; first combined flash report |
| People | Compensation, benefits and title differences documented with a harmonisation plan | HR lead | Gap analysis and dated plan |
| Baseline | Pre-close baselines captured: revenue by customer, churn, pipeline, win rate, headcount | CFO | Baseline file frozen and stored |
Days 31 to 100: execute and measure against the baseline
| Workstream | Item | Evidence |
|---|---|---|
| Commercial | Customer data migrated into the surviving CRM under the agreed definitions | Reconciliation of record counts and pipeline value before and after |
| Commercial | Churn and pipeline tracked weekly against the pre-close baseline | Weekly report with variance explained |
| Systems | First duplicate systems retired and their contracts ended | Cancellation confirmations, licence savings booked |
| Systems | Single sign-on and access management unified | Access review on the combined estate |
| Finance | Synergy tracker reconciled to actuals, line by line | Tracker signed off by the CFO |
| Operations | Supplier contracts consolidated where the synergy case assumed it | Signed contracts |
| People | Key people retained; leavers replaced or covered | Retention status per person |
| Governance | Handover plan for the remaining items to line management | Dated plan with owners |
The integration management office, sized for an add-on
Large mergers run an integration management office with workstream leads, templates and a steering committee. A mid-market add-on needs the function without the bureaucracy:
- One integration lead with protected time, usually 30 to 50 percent of a senior manager's week for the first 100 days.
- A weekly 45-minute review with the functional owners, run from this checklist.
- A monthly one-page update to the board covering synergy status, churn and pipeline against baseline, and decisions needed.
- A decision log, so nobody relitigates a system choice in month three.
If the platform team cannot spare that time, an outside integrator can run the cadence. Make sure they hand it back by a fixed date. Our guide on how to hire and judge a post-merger integration consultant covers the choice between an integration office, an independent integrator and a functional specialist.
Communication plan by audience
| Audience | Sender | When | What they need to hear |
|---|---|---|---|
| Target employees | Both CEOs together | Day 1, first hour | Why the deal happened, what changes for them now, what does not, who to ask |
| Platform employees | Platform CEO | Day 1 | Why the add-on fits the plan, who they will work with, what is expected of them |
| Top 20 customers | Their existing relationship owner | Day 1, by phone or in person | Continuity of service, contacts and contract terms; any new products they can use |
| Other customers | Account management, by email | Day 1 to 3 | Continuity, contacts, where to ask questions |
| Key suppliers and partners | Function heads | First week | Continuity of contracts and payment, any change of contact |
| Board and lenders | Platform CEO and CFO | First board meeting after close | Integration plan, synergy tracker, baseline, risks |
Integration budget lines
Integration costs are often underestimated because they are spread across functions. Put them in one budget and report against it monthly.
| Line | Typical items |
|---|---|
| People | Retention arrangements, severance, harmonisation of pay and benefits, recruitment for new roles |
| Systems | Data migration, integration work, licence overlap during dual running, contract exit fees |
| Advisers | Integration support, legal, HR, tax and IT specialists |
| Customer | Retention offers for at-risk accounts, rebranding of customer-facing materials |
| Facilities | Office consolidation, equipment, moves |
| Contingency | A reserve for items found after close |
Who owns what in an add-on integration
| Workstream | Accountable | Works with |
|---|---|---|
| Governance and the weekly review | Integration lead | Platform CEO |
| Customers and revenue | Head of sales or chief revenue officer | Customer success, RevOps |
| Synergy tracking | CFO | Each synergy owner |
| People and organisation | Head of HR | Function heads |
| Systems and data | CTO or IT lead | RevOps, finance systems |
| Legal, contracts and transition services | General counsel or external counsel | CFO |
| Operations and suppliers | COO or operations lead | Procurement |
When the add-on comes with a transition services agreement from a seller, give it an owner and an exit date for every service on Day 1. Transition services that run past their end date are one of the most common integration cost overruns.
Integration KPIs to review every week
| KPI | Why it matters | Warning sign |
|---|---|---|
| Gross revenue retention of the acquired customer base | Customers leave quietly during integrations | Any top-20 account in a renewal conversation without its usual contact |
| Pipeline coverage for the next two quarters | Sales teams spend time on internal change instead of selling | Coverage falling below the pre-close baseline for two weeks running |
| Synergy realised versus plan | The deal model assumed it | Synergies reported without a line owner or a source |
| Key people retained | Knowledge leaves with people | Resignations from the key people list |
| Systems retired versus plan | Dual running doubles cost and confuses reporting | Retirement dates moving without a reason |
| Open decisions older than two weeks | Integrations stall on decisions, not on work | The same decision on the list three weeks running |
Five items that sink add-on integrations
- Migrating CRM data before agreeing definitions. The combined pipeline looks bigger, the forecast gets worse, and the board loses two quarters of comparable data.
- No owner for the top customers. A competitor calls them in the first week. Someone they know should call first.
- Synergies counted in two places. One owner per line, one source of truth.
- Dual systems with no end date. Pick the survivor in the first 30 days and give the other one a retirement date.
- Founders' admin access left open. Domains, cloud accounts and payment systems often sit in personal accounts at small targets. Check them before Day 1.
Technology and data: the rows most checklists skip
Generic M&A integration checklists cover legal, HR and finance well and treat technology as one line. In a B2B add-on, technology and data carry much of the synergy case: cross-selling needs one customer view, cost synergies need retired licences, and the board pack needs consistent definitions. Add these rows if they are missing from your version:
- Domain, DNS, email and cloud account ownership transferred to company-controlled accounts.
- Customer data model and identifiers mapped across both companies before any migration.
- Integrations between billing, CRM and finance documented for both companies, with the people who maintain them.
- Security review of the target: access, backups, incident history, open vulnerabilities.
- Product and roadmap decisions for overlapping products, with a customer communication plan.
If the technology picture is unclear before close, a technical due diligence on the target answers most of these rows in a week. If the integration needs a technology leader the platform does not have, a fractional CTO can own the systems workstream for the hold.
After day 100
The integration is finished when the remaining items are owned by line management and the integration review becomes a monthly line in the operating review. Close the decision log, archive the checklist with the evidence attached, and keep the pre-close baseline: the next buyer's due diligence team will ask how the add-on performed after it joined, and this is where that answer lives.


