Gantt Chart for M&A Integration Planning

Structure a 100-day M&A integration plan with a Gantt chart covering Day 1 readiness, systems integration, org design, and parallel workstreams for small deal teams.

Gantt Chart for M&A Integration Planning

The deal closes on Friday. On Monday morning, the acquired company's employees come to work and expect answers: Does my health insurance still work? Who do I report to? Is my email address changing? Can I access the combined company's systems? If the integration team hasn't done the work before close, Monday morning is the beginning of a trust crisis that compounds into talent attrition over the following months.

M&A integration is project management under pressure, with decisions that have outsized human consequences. A Gantt chart for an M&A integration doesn't just track tasks — it creates the parallel workstream structure that allows a team of 5–15 people to manage an integration that would otherwise require 40. This guide covers the 100-day integration plan structure, the Day 1 readiness checklist, and how to run integration workstreams without creating dependencies that serialize what should be parallel work.

Integration Planning Starts Before Close

The most common integration failure is waiting until deal close to start planning. By the time the deal closes, the integration team should have a Day 1 playbook that is essentially ready to execute — not a blank Gantt chart.

Integration planning begins during due diligence. The due diligence process reveals the complexity of what you're integrating: the acquired company's systems, org structure, customer contracts, vendor relationships, and cultural norms. Use that information to build the integration plan while due diligence is still underway.

Legal constraints: Most jurisdictions prohibit exchanging competitively sensitive information before close (gun-jumping rules). Integration planning in pre-close uses non-sensitive information — org charts, system inventories, process documentation — not pricing data, customer lists, or competitive strategy. Get outside counsel to define the information boundary early.

Integration management office (IMO)

Name the integration leader and the IMO team before close. For mid-market deals (acquisition price $50M–$500M), the IMO is typically 3–5 people: an integration lead (often the CFO or COO of the acquirer), workstream leads for each integration track, and a project coordinator who owns the master Gantt chart.

The IMO meets weekly during the first 100 days and biweekly from day 101 through full integration. Every workstream reports status in the same format: RAG status (red/amber/green), open issues, decisions needed, and tasks completed since last meeting.

Day 1 Readiness: The Non-Negotiable Baseline

Day 1 is the first business day after deal close. The following items must be complete before Day 1 — not in progress, not planned — complete.

Employee communications

CEO announcement to all employees of both companies, sent at market open on Day 1
Manager talking points — every people manager knows what to say when their team asks "what does this mean for me?"
Employee FAQ document — covers compensation, benefits, reporting structure, and what stays the same
HR contacts named for each acquired company location

HR and benefits

Payroll confirmed — acquired company employees receive their next paycheck from the correct entity
Benefits bridge — acquired employees' health insurance, dental, vision, and 401k coverage continues without interruption through the transition period (typically 90 days)
PTO balance confirmation — employees' accrued PTO is documented and will be honored
Offer letters (if employment terms are changing) — delivered before Day 1, not on Day 1

IT and access

Email access — acquired employees can receive and send email; they know their email address going forward
VPN and remote access — if applicable, acquired employees who need it have access
Critical systems access — any system an acquired employee needs to do their job on Day 1 is accessible
Laptop/device policy — employees know whether their devices are changing and when

Customer and vendor communications

Key customer communication — top 10–20 customers notified before or on Day 1, by the CEO or the relationship owner, not by a mass email
Critical vendor notification — any vendor whose contract must be novated or whose service is critical to operations
Change of legal entity for payments — vendors who invoice the acquired company know where to send invoices

Legal and compliance

Bank accounts — operating accounts are accessible, wire transfer authority is confirmed
Insurance coverage — D&O, E&O, and property insurance is in effect on Day 1
Regulatory notifications filed if required by the deal structure or industry

The 100-Day Integration Plan

The 100-day plan is the operational integration plan — not a strategic vision document, but a task-level project plan with owners, due dates, and success criteria for each deliverable.

Structure it around workstreams. Each workstream is a parallel track within the master Gantt chart. For a mid-market acquisition, typical workstreams are:

Workstream	Lead	Primary Deliverable by Day 100
Finance and Accounting	CFO	Single financial reporting process, consolidated chart of accounts
Human Resources	CHRO	Unified benefits, compensation bands rationalized, org structure confirmed
IT and Systems	CTO / IT Director	Systems integration roadmap, critical systems integrated or bridged
Sales and Revenue	CRO	Combined pipeline in single CRM, customer coverage model defined
Operations	COO	Operational processes documented and standardized
Legal and Compliance	General Counsel	Key contracts novated, regulatory filings complete
Communications	VP Marketing or Comms Lead	Internal and external messaging aligned

Each workstream operates largely in parallel. The IMO's job is to identify cross-workstream dependencies — where one workstream's output is required by another — and ensure those hand-offs happen on time.

Days 1–30: Stabilize and Assess

The first 30 days are about stability, not transformation. The organization has just experienced significant change. Employees are anxious. Customers are watching. This is not the time to announce major structural changes that add to the uncertainty.

What to accomplish in days 1–30:

HR workstream

Complete the HR data audit: confirm headcount, compensation data, role titles, reporting lines, and benefits elections
Identify roles with significant differences in compensation between the two companies — this becomes an equity issue quickly if not addressed
Conduct stay interviews with key talent — ask directly: "What would make you want to stay for the next 2 years?"
Finalize the org structure plan (even if not yet announced)

Finance workstream

Establish a consolidated financial reporting process — even a manual bridge that combines the two companies' P&Ls weekly
Reconcile the acquired company's bookkeeping against the financial statements from due diligence
Establish a single expense reporting and approval process
Begin vendor contract review — identify contracts that need novation, renegotiation, or termination

IT workstream

Complete the systems inventory: every application the acquired company uses, who uses it, what it costs, and whether the acquirer has an equivalent
Assess email and identity: is there a long-term plan to merge into a single email domain?
Implement interim solutions for any Day 1 gaps discovered (VPN access, shared folder access)
Begin integration architecture design for the highest-priority systems (usually CRM and ERP)

Sales workstream

Load acquired company opportunities into the acquirer's CRM (or create a manual bridge for pipeline reporting)
Assign coverage model for existing customer relationships — who owns which customers?
Conduct joint sales calls for at-risk accounts where the acquisition creates uncertainty
Train acquired sales team on the combined product portfolio

Days 31–60: Design and Decide

The second 30 days move from assessment to decisions. By day 60, the following must be decided — not still in discussion:

Org structure: Final reporting relationships confirmed and communicated
Systems roadmap: Decision on which systems survive long-term and which sunset
Integration model: How tightly integrated will the two companies become — full merger, partial integration, or subsidiary model?
Brand: Will the acquired company's brand continue, be phased out, or immediately retire?

These decisions are often contentious. They require executive sponsorship to make and communicate. The integration team's job is to present options with clear trade-offs — not to defer decisions because stakeholders disagree.

The org structure decision

Announcing the final org structure by day 45 reduces attrition significantly. Employees who don't know where they stand make their own decisions — usually the ones you can least afford to lose leave first, because they have options.

The org structure decision requires:

Total headcount the combined organization can support at current revenue run rate
Skills inventory — who has capabilities needed in the combined organization
Geography — remote, hybrid, or on-site requirements for each role
Retention plan for critical talent — retention bonuses, accelerated vesting, or expanded scope

The systems integration roadmap

A typical mid-market acquisition has 30–80 overlapping SaaS applications. The systems decision framework:

Category	Decision	Timeline
Mission-critical (ERP, CRM, HRIS)	Choose one system; migrate the other	6–18 months
Productivity tools (email, docs, collaboration)	Standardize on acquirer's platform	30–90 days
Department tools (project management, design, support)	Evaluate on case-by-case basis	60–180 days
Redundant / unused	Terminate	Immediate

System consolidation reduces SaaS spend by 20–35% in most integrations. Document the savings as part of the integration value case.

Days 61–100: Execute and Measure

The third 30 days move from decisions to execution: systems migrations begin, org changes take effect, and integration value starts to be measurable.

Systems integration execution

Systems integration projects run as sub-projects within the master integration Gantt. Each system migration follows its own project plan — similar to a data migration project — with discovery, field mapping, ETL development, UAT, and cutover phases. (See the data migration Gantt chart guide for the full methodology.)

Priority system integrations for a typical acquisition:

CRM — single view of all customer relationships, combined pipeline, unified reporting
HRIS — single employee record system, unified payroll, benefits management
Finance/ERP — consolidated general ledger, AP/AR, expense management
Identity (SSO/directory) — single identity provider, unified access management

Do not attempt all four simultaneously with a team of 5 people. Sequence them or parallelize with additional integration resources (systems integrator, implementation consultant).

Value realization tracking

By day 100, integration progress should be measurable against the deal thesis. Common value drivers and how to track them:

Value Driver	Measurement
Revenue synergies	Pipeline attributable to cross-sell, new accounts from combined reach
Cost synergies	Headcount reduction, SaaS consolidation savings, facility savings
Operational efficiency	Process metrics compared to pre-acquisition baseline
Customer retention	Net Revenue Retention for acquired company's customers, 90 days post-close

If value realization is not tracking against the deal thesis at day 100, this is the time to investigate and correct — not at month 18 when the integration budget is gone.

Running Integration With a Small Team

A 5–10 person integration team managing 6 parallel workstreams is standard for mid-market deals. The bandwidth constraint means discipline about what the IMO manages directly versus what it delegates to the business.

What the IMO owns:

Master Gantt chart and weekly status reporting
Cross-workstream dependencies and escalations
Communication cadence (weekly IMO meeting, monthly all-hands update)
Decision log — every integration decision recorded with rationale and date
Risk log — issues that could delay or threaten the integration

What the IMO delegates to workstream leads:

Day-to-day task management within each workstream
Vendor coordination for systems implementations
Functional-level decision-making (finance process design, HR policy alignment)
Subject matter expert interviews

The IMO's meeting structure matters. A 90-minute weekly integration review that covers all workstreams takes 5 hours of the integration lead's time per week (prep + meeting + follow-up). A 30-minute meeting per workstream across 6 workstreams takes 12 hours. The consolidated model wins — but only if workstream leads prepare standard status updates in advance.

Building the Master Integration Gantt

In gantt-chart.io, structure the M&A integration as a master project with workstream sub-sections:

Pre-close planning — Day 1 readiness tasks, each with a hard deadline of deal close date
Days 1–30: Stabilize — assessment tasks per workstream, communications milestones
Days 31–60: Decide — decision milestones (org structure announced, systems roadmap approved)
Days 61–100: Execute — systems migration projects, process standardization tasks
Post-100-day: Full integration — longer-horizon system migrations, facility consolidations, brand migrations

Key milestones to highlight:

Deal close (anchor date — everything else is relative to this)
Day 1 communication sent
Org structure announced (target: day 45)
Systems integration roadmap approved (target: day 60)
CRM integration complete
HRIS integration complete
100-day review with board/investors

For presentations to the board or executive team, export the master Gantt as a slide. slide-deck.io can structure integration status updates with the Gantt chart as the centerpiece, alongside value realization scorecards.

FAQ

How much integration work can a team of 5 actually do?

A 5-person IMO can manage a mid-market integration effectively if the team members are senior, have clear workstream ownership, and are not carrying full-time day-jobs alongside integration work. The failure mode is when the "integration team" is 5 people who are also each running their functional departments — integration becomes a side project, and it shows.

When should we announce the org structure?

No later than day 45. Day 30 is better. Employees make decisions during uncertainty — and the first people to update their LinkedIn profiles are usually the ones you most want to retain. The org structure announcement should be preceded by individual conversations with anyone whose role is significantly changing.

How do we handle customers who are nervous about the acquisition?

Assign every significant customer account a named contact from the combined organization immediately. The relationship owner (from either company) makes proactive outreach within 48 hours of deal announcement. The message is simple: your account is a priority, your team is staying, here's who to call if you have questions. Do not wait for customers to ask.

What happens if the integration runs into trouble at day 60?

Stop and reset. A day 60 integration review that reveals significant delays or issues is valuable information — not failure. Common causes: the deal thesis assumed synergies that aren't materializing, key talent departures are affecting execution capability, or a systems integration is more complex than estimated. Diagnose the cause, revise the 100-day plan with realistic timelines, and communicate the revised plan to the board. A credible revised plan is better than an optimistic original plan that everyone knows is wrong.