You've just closed acquisition number eight. The deal team celebrates. The target's managing director shakes hands. The wire clears. And then everyone looks at you and asks: "So, what happens Monday morning?"
If you're reaching for a generic M&A integration plan template downloaded from a consultancy's lead-gen library, you already know the problem. Those templates give you swimlanes and Gantt charts that look impressive in a steering committee deck but tell you nothing about who migrates the email on Day 12, how you extract financial data when their accountant uses desktop QuickBooks, or what to do when the acquired MD says "our CRM is Excel and it works fine."
This merger integration plan template is built from the ground up for roll-up operators who need execution clarity, not strategy theatre. It covers pre-close preparation, Day 1 actions, quick wins in Weeks 1–2, foundational work in Month 1, core migrations in Months 2–3, and optimisation beyond Month 3. Critically, it maps to the High/Medium/Low-Touch integration framework so you can adapt depth and speed to each deal's strategic intent. This isn't a one-size-fits-all checklist. It's a starting point you can bend, prune, and deploy.
Why Most Integration Templates Fail (and What Yours Must Do Differently)
Most 100-day plan templates fail because they're built for the boardroom, not the operations floor. They assume clean data, cooperative stakeholders, and a blank calendar. The brutal reality: your acquired company's "CRM" is three overlapping spreadsheets. Their finance director is on holiday for two weeks post-close. The previous owner took the Wi-Fi password with him.
Generic templates also treat every acquisition identically. A three-person tuck-in gets the same 47-step checklist as a 200-employee platform merger. That's where integration plans become integration theatre-lots of activity, minimal value capture. Research from KPMG (2023) found that 83% of deals failed to boost shareholder returns, and the cause is almost never strategy. It's execution: poorly sequenced tasks, accountability black holes, and optimistic timelines that ignore ground truth.
Your template must do three things differently. First, it must start before close. Waiting until Day 1 to begin planning guarantees you'll spend the first month firefighting instead of executing. Second, it must assign clear owners and decision rights at the task level-not "IT will handle it," but "Sarah completes email migration cutover by Friday Week 2, with rollback plan documented." Third, it must be modular and adaptive, allowing you to dial integration depth up or down depending on whether this deal is a full system consolidation (High-Touch), a spine-only unification (Medium-Touch), or a light reporting overlay (Low-Touch).
Templates aren't inherently bad. Rigid, context-free templates are. Build yours to flex.
The Core Components of an Effective M&A Integration Plan Template
An effective post-merger integration roadmap template contains five structural layers: objectives and success measures, governance and decision rights, workstream task lists with owners and dates, risk and dependency tracking, and progress scorecards. Each layer serves a distinct purpose. Objectives answer "what does good look like?" Governance answers "who decides?" Task lists answer "who does what, when?" Risk tracking answers "what might go wrong?" Scorecards answer "are we on track?"
Let's break down the must-have components within each phase of your 100-day plan after acquisition.
Pre-Close Integration Blueprint
Integration starts the moment you sign the Letter of Intent, not when you get the keys. Pre-close work focuses on three activities: discovery, planning, and Day 1 preparation.
Discovery means auditing the target's systems, data, and workflows while still in due diligence. Which accounting software? Cloud or on-premise email? Who holds admin credentials? What's the data quality in their customer records? If you can't answer these questions before close, you'll spend Month 1 finding out instead of executing. Integration audit work done pre-close pays dividends in speed and risk reduction.
Planning means building your integration roadmap and defining workstreams. Will you consolidate systems fully (High-Touch), unify the financial and HR spine but leave operations autonomous (Medium-Touch), or connect reporting only (Low-Touch)? Document this decision and communicate it clearly to avoid scope creep. Assign workstream owners for Finance, IT, HR, and Operations. Set success criteria: for example, "consolidated financial reporting in Xero by Day 45" or "all staff migrated to platform email by Day 30."
Day 1 Preparation means scripting the first 48 hours. Who sends the welcome email? When do new staff get platform credentials? What communications go to customers and suppliers? When does payroll cutover? Day 1 is a signal-it sets the tone. A smooth Day 1 builds trust: a chaotic one seeds doubt and resistance.
Day 1 Operational Readiness Checklist
Day 1 is about continuity, communication, and control. Your checklist should include:
- Legal and financial close confirmed: Contracts signed, funds transferred, regulatory filings complete.
- Communications deployed: Welcome email to acquired staff, announcement to customers, message to suppliers, internal memo to platform team.
- Access and credentials provisioned: Key staff have email accounts, VPN access, and necessary system logins.
- Payroll and benefits: Confirmation that next pay run will proceed without disruption. Benefits continuity communicated.
- Customer continuity: Service delivery continues uninterrupted. Customer-facing contacts know who to escalate issues to.
- IMO (Integration Management Office) established: Recurring stand-up meetings scheduled, shared tracker (e.g., SharePoint or Monday.com) live, escalation path clear.
Day 1 is not the day to attempt CRM migration or rebrand the website. It's the day to prove the business still works.
30–60–90 Day Integration Milestones
Break the first 100 days into three phases, each with a distinct focus.
Days 1–30: Foundations and Quick Wins
- Establish governance (weekly integration stand-up, clear escalation).
- Complete system and data inventory.
- Migrate email and file storage (if Medium or High-Touch).
- Extract financial data and connect to platform reporting (even if manual initially).
- Identify and engage digital champions within the acquired company.
- Communicate integration roadmap to acquired staff-transparency reduces anxiety.
- Achieve at least one visible quick win (e.g., unified supplier login, single customer portal, consolidated reporting dashboard).
Days 31–60: Core Migrations and Process Alignment
- Begin CRM and ERP migration (High-Touch) or establish integration layer (Medium-Touch).
- Standardise finance and HR workflows (chart of accounts, approval hierarchies, onboarding process).
- Conduct role-based training for acquired staff on platform systems.
- Sunset legacy systems with clear end dates and off-boarding support.
- Track and report early synergy realisation (e.g., vendor consolidation savings, duplicate licence elimination).
Days 61–90: Stabilisation and Optimisation
- Complete core system migrations and validate data integrity.
- Shift to hypercare mode: intensive user support, daily check-ins, rapid issue resolution.
- Measure adoption (login rates, process compliance, support ticket trends).
- Document lessons learned and update playbook for next acquisition.
- Transition from integration mode to business-as-usual operations.
System Consolidation and IT Roadmap
Your IT workstream is the backbone of integration. Sequence migrations in this order to minimise risk and maximise momentum:
- Email and collaboration tools (Google Workspace or Microsoft 365). Fast, high-visibility, creates unified communication from Day 1.
- File storage and document management. Migrate to shared drives or cloud storage. Avoid the conversion trap (Google Docs ≠ Word files).
- Finance and accounting systems. Consolidate chart of accounts, migrate transactions, connect bank feeds. This gives you financial visibility.
- HR and payroll. Unified employee records, benefits administration, and pay runs. (Choosing your depth of system unification depends heavily on whether acquired operations are homogenous or differentiated.)
- CRM and customer data. High risk, high value. Clean, deduplicate, and migrate carefully.
- ERP and operational systems. Slowest and most complex -- defer unless synergies are material.
For each migration, your roadmap must specify: current state, target state, owner, timeline, rollback plan, training needs, and success criteria.
Building Your 100-Day Plan After Acquisition: The Critical Path
The critical path is the sequence of tasks that, if delayed, push out your entire integration timeline. Identifying it is the difference between finishing on Day 100 and still firefighting on Day 180.
Start by mapping dependencies. Email migration can't complete until you've provisioned user accounts. CRM migration can't start until you've cleaned and deduplicated records. Financial consolidation can't close until chart of accounts harmonisation is done. Payroll can't cut over until employee records are migrated and validated. Visualise these dependencies-use a simple flowchart or Gantt chart if it helps-but don't let the tool become the work.
Next, identify your longest-lead-time tasks. These are usually:
- Data cleaning and deduplication (often 2–4 weeks for CRM/ERP).
- ERP migration and testing (8–12 weeks for complex systems).
- Third-party vendor coordination (e.g., telephony, logistics software, industry-specific tools).
- Regulatory or compliance approvals (especially in healthcare, finance, or regulated industries).
These tasks go on the critical path. Everything else is parallel work that can flex around them.
Now assign owners with real authority. "IT" is not an owner. "Stephanie (IT Manager) with authority to engage contractors and override legacy system access" is an owner. Make sure owners have three things: clarity on the desired outcome, authority to make decisions or escalate blockers, and protected time (i.e., their day job workload is adjusted).
Finally, build in buffers. A 100-day plan should have 110 days of calendar. Migrations slip. People go on holiday. Acquired staff push back. Discovered issues surface. Optimism is not a risk mitigation strategy. Prudent operators plan pessimistically and execute optimistically.
Post-Merger Integration Roadmap Template: Structuring Governance and Accountability
Governance is where good plans succeed and weak plans collapse. Without clear decision rights, escalation paths, and progress visibility, your integration drifts into a slow-motion negotiation between acquired managers protecting their turf and platform leaders demanding compliance.
Establish an Integration Management Office (IMO) with a single owner-your Integration Manager, COO, or a senior operator with cross-functional authority. The IMO does not do all the work: it orchestrates, tracks, and unblocks. Run a weekly integration stand-up (30 minutes, no status updates-exceptions and blockers only) and a fortnightly steering committee (senior leaders, score progress against plan, make go/no-go decisions on major milestones).
Use a shared tracker that everyone can see. A spreadsheet works. SharePoint works. Monday.com or Asana work. The tool doesn't matter: transparency and accountability do. Every task should show: description, owner, due date, status (not started / in progress / complete / blocked), and any notes or blockers. Understanding who should handle different parts of integration helps clarify whether to staff tasks internally, hire contractors, or engage a specialist partner.
Integration Workstreams and Owner Assignment
Typical workstreams for a roll-up integration include:
- Finance: Chart of accounts mapping, bank account consolidation, financial reporting integration, vendor and contract rationalisation.
- IT and Systems: Email/file migration, CRM/ERP consolidation, network and security integration, software licence audit.
- HR and People: Payroll cutover, benefits alignment, org chart updates, onboarding and culture integration.
- Operations: Process documentation and standardisation, customer handover communications, service delivery continuity.
- Commercial: Sales pipeline integration, pricing and contract alignment, brand and marketing unification (if applicable).
Each workstream needs a named owner, a deputy (for holiday/absence cover), a budget (even if notional), and decision authority within defined bounds. "Finance workstream can approve software spend up to £5,000: anything above escalates to CFO" is clearer than "check with finance."
Tracking Synergy Realisation and Value Leakage
Synergies don't realise themselves. Track them with the same rigour you track integration tasks. Common synergy categories in roll-ups:
- Cost synergies: Duplicate software licences eliminated, vendor consolidation rebates, back-office headcount reduction, insurance and banking fee savings.
- Revenue synergies: Cross-sell opportunities, geographic expansion, customer concentration reduction.
- Operational synergies: Shared best practices, consolidated purchasing, standardised workflows.
Build a simple synergy tracker: Initiative | Owner | Estimated Annual Value | Realisation Date | Actual Value Captured. Update it monthly. If synergies aren't landing, investigate why. Often the issue is not strategic-it's execution (e.g., licence not cancelled, contract not renegotiated, process not enforced).
Value leakage is the silent killer: customer attrition during integration chaos, key staff departures, delayed invoicing, compliance fines from missed regulatory deadlines, or brand damage from service failures. Track leading indicators like employee engagement scores, customer complaint rates, and overdue receivables. Spot the trend before it becomes a crisis.
Adapting Your Template for Deal-Specific Realities
No two acquisitions are identical, so your merger integration plan template must flex. The High/Medium/Low-Touch framework is your adaptation mechanism.
High-Touch Integration is full consolidation: single ERP, single CRM, unified processes. Use this when the acquired company is operationally similar to your platform, when standardisation drives clear cost and quality synergies, or when the target's systems are end-of-life and must be replaced anyway. Timeline: 3–6 months. Risk: high disruption, potential talent loss if poorly managed. Mitigation: invest heavily in change management, training, and hypercare.
Medium-Touch Integration unifies the financial and operational "spine" (finance system, email, HR, reporting) but leaves niche operational tools autonomous. Use this when the acquired company serves a different customer segment, operates in a different geography, or uses superior specialised software you don't want to lose. Timeline: 2–3 months. Risk: moderate complexity managing hybrid state. Mitigation: clear criteria for what integrates and what stays. Document integration boundaries.
Low-Touch Integration connects only what's needed for visibility-financial reporting, basic security, maybe email. Operations stay autonomous. Use this for early-stage tuck-ins, earn-out scenarios where management independence is contractually required, or when you're testing the acquisition before deeper integration. Timeline: 2–4 weeks. Risk: delayed synergy capture, integration debt compounds if you never progress beyond Low-Touch. Mitigation: set a decision date (e.g., 12 months post-close) to revisit integration depth.
Adapt your template by dialling task intensity and scope up or down per workstream. A Low-Touch deal skips CRM migration entirely but still completes email migration for security and communication. A High-Touch deal includes full ERP cutover, process reengineering, and brand unification. Write your template with tiered task lists so you can toggle components on and off without rebuilding from scratch.
Finally, adapt for industry-specific realities. If you're in healthcare, add compliance workstreams (CQC registration transfers, patient record migrations, safeguarding checks). If you're in facilities management, add client contract novation and H&S documentation. If you're in pest control, add technician scheduling system integration and chemical inventory tracking. Generic is fine as a starting skeleton: specific is what makes it useful.
Frequently Asked Questions
Can we really complete integration in 100 days?
It depends what you mean by "complete." Email, file migration, and financial reporting integration? Absolutely, often faster. Full ERP consolidation with complex data migration, custom integrations, and process reengineering? Rarely. The 100-day milestone is about achieving operational stability and visibility, not perfection. Most operators find that financial visibility and communication unification in the first 60 days captures the majority of early value: deeper system work can run in parallel or sequence after.
What if the acquired company resists integration?
Resistance is normal and often rational. Their systems work for them: yours are unfamiliar and may be inferior for their specific workflows. Manage resistance by communicating early and honestly (what's changing, why, when, and what support they'll receive), involving their informal leaders (digital champions) in planning and testing, delivering quick wins that make their lives easier (e.g., single sign-on, better reporting), and providing intensive hands-on training and hypercare post-cutover. Resistance drops when people feel heard, supported, and see tangible benefits.
Should we use the same plan for every acquisition?
No. Your template should be modular, not monolithic. Maintain a master template with all possible workstreams and tasks, then prune it per deal based on integration depth (High/Medium/Low-Touch), size, complexity, and strategic intent. A three-person tuck-in doesn't need a formal IMO or steering committee. A 150-employee strategic acquisition does. Adapt ruthlessly.
How do we avoid integration debt piling up across multiple deals?
Integration debt-deferred consolidation that compounds complexity-is the silent value killer in roll-ups. Avoid it by setting and enforcing a Sunset Policy: clear criteria and timelines for when legacy systems must be replaced. For example, "All acquired companies move to platform email within 30 days, platform finance system within 90 days, platform CRM within 6 months." Allow exceptions only with written executive approval and a documented plan to converge later. Saying no to integration is a valid decision: deferring the decision indefinitely is not.
Do we need outside help or can our internal team handle it?
It depends on your team's bandwidth, skills, and the complexity of the integration. Internal IT teams at roll-ups are typically 2–3 people managing helpdesk, infrastructure, and security for 200+ users. Every acquisition adds integration work they don't have capacity for. Specialist partners can step in to execute complex migrations (CRM/ERP data, email cutover, workflow automation) while your internal team focuses on business-as-usual and governance. Strategy consultants will give you a plan. Technical execution partners focus on actually doing the migration work.
Your Template Is Only as Good as Your Execution
A good merger integration plan template doesn't guarantee success, but a bad one-or no template-guarantees costly drift. The template we've outlined here is designed to be practical, modular, and adapted to the messy realities of roll-up integrations. It starts before close, assigns clear ownership, sequences work to minimise risk, and maps directly to the High/Medium/Low-Touch framework so you can tune integration depth to strategic intent.
Use it as a skeleton. Add your industry-specific workstreams, adjust timelines based on your team's capacity, and refine it after every acquisition. The goal isn't to follow the plan slavishly-it's to make smart calls under pressure, learn fast, and capture value before it leaks away.
If you'd like a ready-to-use Excel version of this roadmap -- with workstream tabs, task owners, and progress tracking -- grab the full toolkit from our integration resources hub. And if your next acquisition needs a technical partner to handle the migration work while you focus on operations, we're here when you're ready.
