Post-Merger Integration Checklist: Day 1 to Day 100

Key Takeaways

A PMI checklist is built before close, not after. Day 1 readiness has to be tested while there is still time to fix what’s missing.
Nine workstreams cover most integrations, each with a named owner. Items without an owner and a date are aspirations, not checklist entries.
Day 1 is a narrow set of must-work items: people can log in and get paid, customers know who to call, and the legal entity can transact.
The first 100 days carry the decisions that need to be visibly made early: org structure, systems roadmap, and brand.
Culture and communications need an owner and deliverables like any other workstream. Treated as an attitude rather than a workstream, they get dropped.

A post-merger integration checklist is a document created during the M&A process that spells out the steps to integrate the merged or acquired companies. It is used to help smooth out the process after the company has gone through the entire merger cycle. Understand it’s not simply about the company’s assets and processes, but about the employees as well. There is always a lot of uncertainty among the staff whenever there’s any type of merger or acquisition, mainly because there is often a certain amount of overlap and, in many cases, staff cuts are made, due to redundancy.

For most companies undergoing a merger or acquisition, it’s an uncertain time where there are many moving parts and a lot of things are in flux for a while, so once the dust of the transaction has settled, it’s important for the company to be able to focus on its goal in the post-merger era. Knowing how to handle the post-merger integration is key.

What makes a checklist work? The difference between a checklist that gets used and one that gets filed is usually three things: every item has a named owner, every item has a date tied to the timeline rather than a vague phase, and the list is built before close so Day 1 gaps surface while there’s still time. A post-merger integration checklist assembled after closing is a record of what you forgot.

This checklist is organized the way integration teams actually run: by workstream, sequenced against a Day 1 to Day 100 timeline. Adapt it: no two integrations have the same shape, and the right level of integration depends on the deal thesis. If you’re still deciding how to integrate rather than what to do first, start with our guide to M&A integration types and strategy.

The Post-Merger Integration Timeline

Integration work is sequenced, and most of what goes wrong is a timing failure rather than a planning one, the right task done a month too late.

Pre-close (signing to Day 0)

The planning window, and the only period when the integration can be designed without simultaneously running the combined business. Workstream leads named, the Day 1 checklist built and tested, the 100-day plan drafted.

One constraint governs everything here: until the deal closes the two businesses remain competitors, and antitrust rules limit what commercially sensitive information can pass between them. The standard mechanism is a clean team: a small ring-fenced group, often including third parties, permitted to see sensitive data and produce planning analysis without exposing it to the operating businesses. Set this up with counsel early.

Day 1

A deliberately narrow set of things that must work. The test is simple: can employees log in and get paid, do customers know who to call, can the legal entity transact, and has leadership said something.

Day 1 is as much a communications event as an operational one. What people hear on the first morning sets expectations for the following year.

Days 2–30

Stabilize. Governance operating on a fixed cadence, workstreams reporting, immediate people questions answered, customers contacted. The priority is that nothing breaks while the bigger decisions are worked through.

Days 31–100

Decide and communicate. Org structure, systems roadmap, brand direction, policy harmonisation. These need to be visibly made in this window — uncertainty past 100 days is where attrition accelerates.

Beyond 100 days

Execution and tracking. Systems migration, synergy delivery against the register, and cultural work that cannot be compressed. Full integration typically runs one to three years depending on approach and scale.

Post-Merger Integration Checklist by Workstream

The existing eight categories map onto the brief’s nine workstreams, all existing items retained and redistributed. Two deliberate changes of form:

Questions converted to actions. Five of the eight existing categories are lists of questions (“Are all the executives on the same page with business strategy?”). Questions work for a diagnostic; they don’t work as checklist items, because you can’t tick them and nobody owns them. Each is converted to an action with an implied owner, substance intact.
Timing added. Every item tagged to a phase so the list connects to the timeline above.

1. Governance & Integration Management Office (IMO)

Appoint a named integration leader, ideally full-time and senior enough to decide rather than relay (pre-close)
Stand up the IMO and confirm workstream leads from both organizations (pre-close)
Establish the steering committee and its meeting cadence (pre-close)
Agree decision rights and the escalation path before they are needed (pre-close)
Build the synergy register with named owners and target dates (pre-close)
Draft a timeline and an action plan for the overall integration plan (pre-close)
Finalize and maintain detailed integration checklists (ongoing)
Set the reporting rhythm and a single source of truth for status (Day 1)

2. Human Resources & People

Identify flight risks and put retention arrangements in place (pre-close)
Develop an organizational chart for the post-merger company (pre-close, announce by Day 30)
Identify and plan to eliminate redundancies, which includes drafting severance documents (pre-close)
List hiring needs for both the short-term (temporary workers) and the long-term (permanent employees) (Days 2–30)
Prepare packages for new hires that include onboarding documents and a benefits overview (Day 1)
Create lists of any benefits or compensation packages that will be changing post-merger (pre-close)
Communicate all HR policy changes to employees and stakeholders (Day 1 onward)
Confirm payroll runs correctly for every employee in the combined entity (Day 1 — test pre-close)
Harmonise benefits, leave policies and job architecture (Days 31–100)
Confirm the leadership team is aligned on business strategy and equipped to lead the combined organization (pre-close)
Assess how the merger affects middle and front-line management, including new reporting lines (Days 2–30)
Identify the behavioral traits each team needs, whether that talent exists internally, and whether to hire from within or outside (Days 31–100)

3. Finance & Accounting

Confirm banking, treasury and payment capability from Day 1 (Day 1)
Map the combined chart of accounts (pre-close, implement by Day 100)
Agree the close calendar and reporting pack for the combined entity (Days 2–30)
Tie every synergy in the register to a named budget line and owner (Days 2–30)
Confirm audit, tax and statutory reporting obligations for the new structure (Days 31–100)
Align budgeting and forecasting cycles (Days 31–100)
Consolidate insurance and confirm continuous coverage across both entities (Day 1)

4. IT & Data

Complete the systems and application inventory for both organizations (pre-close)
Ensure network access, email and core tools work for everyone (Day 1)
Transfer all employee data in tandem with HR (Day 1)
Partner with key IT stakeholders to merge systems, including HR and payroll (Days 2–100)
Ensure that all data and systems are fully merged and functional in the post-merged company (beyond 100 days)
Decide which systems survive, which retire and what runs in parallel (Days 31–100)
Review software licences and enterprise agreements for change-of-control terms — many do not transfer automatically (pre-close)
Align security posture, access controls and incident response (Days 2–30)
Agree data governance: definitions, ownership and master data (Days 31–100)

5. Legal & Compliance

Confirm entity structure and that all closing filings are complete (Day 1)
Identify contracts requiring assignment, novation or consent — whether they transfer automatically depends on the deal structure (pre-close)
Transfer or reapply for licences, permits and registrations (pre-close to Day 30)
Confirm regulatory notifications and approvals are satisfied (pre-close)
Consolidate IP registrations and confirm ownership (Days 31–100)
Harmonise compliance policies, delegation of authority and the code of conduct (Days 31–100)
Plan entity rationalisation where the structure permits (beyond 100 days)

6. Communications

Draft a timeline and action plan for public-facing changes (pre-close)
Prepare Day 1 messaging for each audience: employees, customers, suppliers, partners, media (pre-close)
Brief managers before the announcement, they will field the questions (pre-close)
Open a channel for questions and answer them visibly (Day 1)
Set a regular update cadence and hold to it even when there is nothing new — silence is read as bad news (Days 2–100)
Sequence external announcements against customer and partner outreach (Day 1)

7. Sales, Marketing & Customer / GTM

Contact key customers directly, before they hear it elsewhere (Day 1)
Confirm every account has a named owner through the transition (Day 1)
Align territories, quotas and compensation plans (Days 31–100)
Identify and resolve channel or partner conflict (Days 2–30)
Agree the combined product and service narrative (Days 31–100)
Review pricing alignment and overlapping contracts (Days 31–100)
Consolidate marketing assets, domains and digital properties (beyond 100 days)

8. Operations & Procurement

Confirm supply chain continuity through the transition (Day 1)
Consolidate the vendor list and identify duplicate suppliers (Days 2–30)
Renegotiate key contracts on combined volume (Days 31–100)
Review the facilities and real estate footprint, including lease obligations (Days 31–100)
Align operational processes, SLAs and quality standards (beyond 100 days)

9. Culture & Change Management

Retained from “Communicating Company and Brand Culture” and “Organizational Structure”, converted from questions to actions.

Assess whether the two organizations have different corporate cultures and where they clash (pre-close)
Decide which cultural elements carry forward, and say so explicitly (Days 2–30)
Define how that culture will be encouraged, rewarded and reinforced (Days 31–100)
Confirm the organizational structure fits the post-merger entity, whether strategy needs adjusting, and whether the structure allows room to grow (Days 31–100)
Give culture a named owner, a budget and deliverables like any other workstream (pre-close)
Identify and equip change champions across both organizations (Days 2–30)
Measure sentiment at intervals rather than assuming it (Days 31–100 and beyond)

Your post-merger integration checklist should include all the high-level items that your company requires when merging. Of course, you will have to adapt certain things to your particular situation. Open communication in these uncertain times is definitely one of the keys to success.

How a Virtual Data Room Supports Post-Merger Integration

No matter what type of M&A transaction your company is going through, one important tool for the process is a virtual data room (VDR).

A VDR is a secure, online location where companies involved in an M&A are able to store and share all the required documentation, including a post-merger checklist. All VDRs feature highly secure access and include enterprise-level encryption, multiple layers of security and user-friendly admin controls. Data that is stored on a VDR is protected by version control, which allows only parties involved in the transaction to access only the appropriate documents.

During integration specifically, the requirement changes shape. Diligence involves a handful of reviewers looking at a fixed set of documents. Integration involves dozens of contributors across nine workstreams, producing documents, for months, and much of that material is more sensitive than anything in the diligence file:

Clean team operation before close. A defined group needs to analyse competitively sensitive data and produce planning output without that data reaching the operating businesses. Granular permission control is the entire requirement, and general-purpose file storage does not provide it.
Workstream separation. The IT workstream does not need severance documents. The commercial workstream does not need compensation bands. Role-based permissions let nine workstreams operate from one environment without seeing each other’s material.
The most sensitive documents in the deal. Severance schedules, retention packages, redundancy plans and org charts pre-announcement. Rights management keeps control attached after download, which matters more here than in diligence, because far more people have access.
An auditable record. Audit trails showing who accessed what and when, the evidence base if a clean-team or gun-jumping question is ever raised.
Continuity from diligence. The due diligence room already holds much of what integration teams need. Carrying it forward means the findings that should drive the plan are already where the plan is being built. See also our due diligence checklist.
Structured Q&A. Routing questions between workstreams to the right owner, answered once and recorded, rather than the same question answered four ways across four email threads.

Why CapLinked Is the Right Tool for Post-Merger Integration

For any company working on (or even planning) an M&A and a post-merger integration, partnering with a trusted third-party VDR provider will help streamline the process, both logistically and financially. CapLinked VDRs include a user-friendly interface and the ability to work on virtually every type of computer or internet-connected device, which matters during integration when contributors span two organizations, several countries and whatever devices each side already issued.

What that looks like against the checklist above:

Permissioning by workstream. Nine workstreams, one environment, each seeing only its own material.
Control after download. FileProtect keeps access control attached to severance schedules and pre-announcement org charts once they leave the room.
EZ Q&A. Cross-workstream questions routed, answered once, recorded.
Audit trails and secure sharing. A complete record across a process running months rather than weeks.
Concierge. Having the structure built and maintained for you — often the difference between a live checklist and a stale one.
Integrations and the CapLinked API. Connect to the systems both organizations already run, during the period when nobody is certain which system wins.

See the full feature set or review pricing.

Build the checklist before close, and put it somewhere every workstream can work from. Start your free trial today.

Post-Merger Integration Checklist FAQs

What is a post-merger integration checklist?

A post-merger integration checklist is a working document setting out what must happen, by whom and by when, to combine two organizations after a deal closes. It is organized by workstream: HR, IT, finance, legal, commercial, operations, communications and culture, and sequenced against a Day 1 to Day 100 timeline.

When should you create a PMI checklist?

Before the deal closes, during the period between signing and closing. This is the only window when integration can be planned without simultaneously running the combined business, and it allows Day 1 gaps to surface while there is still time to fix them.

What must be ready on Day 1 of a merger?

A narrow set of must-work items: employees can access systems and payroll runs correctly, customers know who to contact, the legal entity can transact and banking is live, and leadership has communicated to every audience. Everything else can follow in the first 30 days.

What is a 100-day integration plan?

A 100-day plan sets out the decisions that must be visibly made in the first hundred days: organizational structure, systems roadmap, brand direction and policy harmonization. It does not cover the whole integration, which typically runs one to three years, but it resolves the uncertainty that drives attrition.

Who owns the post-merger integration checklist?

The Integration Management Office holds the master checklist, while each workstream owns its own items. A named integration leader, ideally full-time, is accountable overall. Items without a named owner and a date tend not to get done, regardless of how well the list is written.

What is a clean team in M&A?

A clean team is a small ring-fenced group, often including third parties, permitted to review competitively sensitive information before a deal closes and produce analysis for integration planning without exposing that data to the operating businesses. It exists to allow planning while managing antitrust and gun-jumping risk.