70 to 90 percent of M&A deals fail to deliver their expected value.
Not "some" deals. Not "a few underperformers." The vast majority. And when researchers dig into why, the reasons aren't usually strategic. The thesis was sound. The market opportunity was real. The failures happen in execution.
Specifically, they happen in integration.
According to Bain & Company, 83% of M&A practitioners cite poor integration execution as the primary cause of deal failure. Not bad due diligence. Not overpaying. Execution. The part that happens after the champagne corks pop and the deal closes.
This article explores why technical integration is often the hidden value driver (or destroyer) in acquisitions, what's actually at stake when it goes wrong, and the common failure patterns to avoid.
This article is adapted from Chapter 1 of The Roll-Up Integration Playbook, our free guide to post-merger technical integration.
Roll-Up Integration Is Different
Post-merger integration (PMI) in the traditional sense conjures images of billion-pound corporate mergers: two mature organisations with established IT departments negotiating whose SAP instance survives.
That's not what most serial acquirers are dealing with.
If you're running a roll-up or buy-and-build strategy, you're not merging equals. You're a platform company scaling through acquisition, absorbing smaller, often owner-operated businesses. These acquired companies typically run lighter-weight tech stacks:
- Xero, Sage 50, or QuickBooks for accounting
- Google Workspace or Microsoft 365 for email and documents
- Pipedrive, HubSpot, or just Outlook and memory for customer management
- Excel for reporting, scheduling, and "everything else"
- Legacy systems, sometimes decades old, that nobody fully understands but everyone depends on
Your platform company might be running similar tools, or you might be standardising on more robust systems as you grow. Either way, you're now responsible for making multiple versions of everything work together (or deciding what to consolidate and when).
That gap is where integration work lives. And it's where value is either captured or lost.
What's Actually at Stake
Let's be direct about why this matters. Here's what happens when technical integration goes wrong:
Value Leakage
Every month you're paying for five different CRM licenses, three accounting systems, and duplicate software across every acquired entity, money walks out the door. These "stranded costs" add up fast.
It's not uncommon for platforms to burn £50K+ annually on redundant software alone. And that's before you count the operational inefficiency of maintaining parallel systems.
Opaque Reporting
Your board and investors want consolidated numbers. They want to understand customer concentration across the group, track revenue by service line, and monitor operational KPIs.
If your data lives in seven different systems with seven different definitions of "customer," you can't give them what they need. This erodes confidence and creates friction at board level, exactly when you need support for your next acquisition.
Operational Friction
When your sales team can't see a customer's service history because it's locked in a different system, they look unprofessional. When your finance team spends three days every month manually consolidating reports, they're not doing higher-value work. When your operations team can't schedule resources across entities because the systems don't talk to each other, you're leaving money on the table.
Research from PwC shows that only 57% of successful acquirers fully integrate systems and processes. The other 43% are living with some version of this friction, and paying for it.
Talent Attrition
Integration uncertainty is one of the top reasons employees leave after an acquisition. The numbers are stark: 47% of acquired employees leave within the first year, according to EY research. By year three, that number climbs to 75%.
If your acquired teams feel like they're being ignored, steamrolled, or left in limbo, your best people will start looking for exits. The institutional knowledge they take with them is often irreplaceable.
For more on the human side of integration, see Why Systems Don't Fail — Adoption Fails.
Integration Debt
The longer you wait, the harder it gets. Every month that passes, more data accumulates in disconnected systems, more workarounds become embedded, and more "temporary" solutions become permanent.
We call this "integration debt." Like technical debt, it compounds over time. And like technical debt, it eventually demands payment, usually at the worst possible moment.
Case in Point: The $556M Write-Down
Lightspeed Commerce, a Canadian tech company, grew rapidly through acquisitions but consistently deferred technical integration. "We'll consolidate later" became the default. By 2022, the accumulated technical debt across their portfolio had become so severe that the company took a $556M goodwill impairment charge. The acquisitions that looked valuable on paper couldn't deliver their expected synergies because the systems were never properly unified.
The Five Common Failure Patterns
Research and case studies reveal consistent patterns in failed integrations. Knowing what typically goes wrong can help you avoid the same traps.
1. The "Rip and Replace" Disaster
A platform acquires a company and immediately forces them onto the platform's systems. Same CRM, same processes, same everything, starting Monday.
The acquired team rebels. Productivity tanks. Customers notice the chaos. Key employees leave. Three months later, you've destroyed more value than you created.
Case in Point: Revlon's $64M Shipping Crisis
When Revlon rushed an SAP ERP cutover to hit synergy targets, they lost the ability to ship products for weeks. The result: $64M in lost sales, a 6.9% stock drop in a single day, and class-action lawsuits.
The technical migration might have worked with proper parallel running and testing. Instead, the pressure to move fast turned a manageable project into a catastrophe.
2. The "We'll Get to It Later" Drift
Integration feels hard and disruptive, so it keeps getting pushed back. "Let's focus on the next acquisition first." "We'll consolidate systems once we hit ten companies."
Meanwhile, complexity compounds. By the time you finally address it, you're untangling five years of accumulated mess across fifteen entities. The cost and disruption are now 10x what they would have been if you'd started earlier.
Deloitte research shows that 53% of acquirers experience delayed integration of core business functions like ERP and CRM, often because they underestimated the complexity or prioritised deal flow over integration.
3. The "One Size Fits All" Mistake
Every acquisition gets the same integration playbook: full system consolidation, 90-day timeline, no exceptions.
But not every acquisition is the same. The £500K tuck-in with three employees needs a different approach than the £10M strategic acquisition with superior operational systems. Treating them identically destroys value in both cases.
For a framework on matching integration depth to strategic intent, see How to Decide the Right Integration Level for Each Acquisition.
4. The "IT Will Handle It" Abdication
Integration gets dumped on the IT team without adequate resources, authority, or business context. IT does their best but makes technical decisions without understanding business implications.
The CRM migration is technically successful but breaks the sales process. The finance system works but nobody was trained. The integration is "complete" on paper but fails in practice.
According to Gartner, 84% of IT integrations fail or experience significant issues. The technical work is only part of the challenge. The business context and change management matter just as much.
5. The "Data Quality Surprise"
Everyone assumes the data will migrate cleanly. Nobody looks closely until migration day, when you discover that 30% of customer records are duplicates, half the contact information is outdated, and critical fields have been used for purposes nobody documented.
Research shows 83% of data migration projects fail or exceed their budget and timelines. Data quality issues are the most common culprit.
The timeline slips by months while you clean up the mess. For guidance on avoiding this, see The Post-Acquisition Integration Audit.
The Case for Minimum Viable Integration
Here's a principle that will save you significant pain: not every acquisition needs full integration.
We call this "Minimum Viable Integration" (MVI): doing enough integration to capture the value you need, without over-engineering or over-disrupting.
For some acquisitions, MVI might mean full system consolidation. For others, it might mean connecting only the financial reporting layer and leaving operational systems alone. The right answer depends on:
- What value you're trying to capture from this specific acquisition
- How similar or different the acquired business is to your platform
- Whether their systems are inferior, equivalent, or superior to yours
- How much disruption the business can absorb
- How long you plan to hold the asset
Integration is not binary. You have options along a spectrum. Choosing the right level of integration for each acquisition is one of the most important decisions you'll make.
Research backs this up: companies with programmatic acquisition strategies (structured, repeatable approaches) achieve 8.5% TSR growth compared to 3.7% for ad-hoc acquirers, according to Bain & Company. The difference isn't luck. It's having frameworks for decisions like integration depth.
Key Takeaways
- 70-90% of M&A deals fail to deliver expected value, and 83% of practitioners point to poor integration execution as the primary cause.
- Roll-up PMI is fundamentally different from traditional M&A integration. You're absorbing smaller, less mature tech environments into a growing platform.
- The stakes are real: value leakage from redundant systems, opaque reporting, operational friction, and talent attrition all compound when integration is handled poorly.
- Most failures follow predictable patterns: moving too fast (rip and replace), moving too slow (integration drift), applying one-size-fits-all approaches, abdicating to IT, or ignoring data quality.
- "Minimum Viable Integration" means matching your integration depth to your strategic intent. Not every acquisition needs full consolidation.
Get the Full Playbook
This article covered why technical integration matters and the common pitfalls to avoid. For the complete framework, including the High/Medium/Low-Touch decision framework, 100-day execution timeline, and ready-to-use checklists, download The Roll-Up Integration Playbook.
Download the Playbook
About PMI Stack
PMI Stack helps small-to-mid cap roll-ups unify systems, data, and workflows across their acquired companies. We specialise in the technical side of post-merger integration: data migration, system consolidation, and the change management that makes new tools stick.
If you're planning an integration and want to talk through your specific situation, book a free discovery call.
Statistics cited from McKinsey, Bain & Company, Deloitte, PwC, EY, and Gartner. For the full research compilation, see 50+ Post-Merger Integration Statistics (2026).
