You've closed the deal. The champagne's flat, the LOI signed, and the wiring instructions confirmed. Now what?
Most operators discover the hard truth within weeks: the acquisition was the easy part. The real work-integrating two companies, aligning systems, keeping staff engaged, making sure the numbers consolidate-starts now. And if you've just completed your first or second acquisition, it's entirely normal to feel unsure where to begin.
Here's the brutal maths: 70–90% of acquisitions fail to deliver expected value. The culprit is rarely strategy-it's execution. Specifically, the messy, unglamorous work of combining companies after acquisition: migrating email, consolidating finance systems, communicating change, and earning trust from people who didn't ask to be acquired.
This article walks you through the integration spectrum-from full consolidation to near-autonomy-then zeroes in on what to tackle first, how to manage the people side, and the most common mistakes that erode value. We'll also cover when to bring in external help and answer the practical questions operators ask most often.
The Brutal Reality of Post-Acquisition Integration
Integration is where deals go to die.
You acquired the company for clear reasons-geographic expansion, bolt-on capacity, a talented team, or proprietary customer relationships. But value doesn't transfer automatically. It compounds or erodes based on what happens in the first 90 days.
The numbers don't lie. Most acquirers underestimate three things:
- Timeline complexity. Even a "simple" email migration takes 2–4 weeks if done properly-longer if data is messy or staff resistance is high.
- People dynamics. The acquired team didn't choose you. They're anxious, defensive, and watching for signs you'll break what works or make their jobs harder.
- Operational drag. Every day you run two separate finance systems, two CRMs, and two sets of processes is a day you're paying double license costs, delaying consolidated reporting, and compounding integration debt.
Integration debt behaves like technical debt: it accumulates interest. The longer you wait, the more entrenched workflows become, the more expensive migration gets, and the harder it is to carry out group-wide standards. It's common for roll-ups to defer integration for 18 months, only to discover that a straightforward CRM consolidation has ballooned into a six-month political nightmare because each site has built custom workarounds.
The good news? Integration is a known problem with known solutions. It doesn't require luck. It requires a clear-eyed assessment of what you're integrating, a realistic timeline, and disciplined execution.
The Four Critical Integration Dimensions You Must Orchestrate
Successful integration isn't a single project-it's the orchestration of four overlapping dimensions. Miss one, and value leaks.
Systems and Technology: Merging Two Companies Systems Without Breaking What Works
This is where most operators start, and rightly so. Systems are visible, measurable, and directly tied to cost and reporting.
Your goal isn't to rip and replace everything immediately-it's to unify the "spine" that enables group visibility and operational control:
- Email and communication (Google Workspace, Microsoft 365). Security baseline, quick win, visible to everyone.
- Finance and accounting (Xero, QuickBooks, Sage). CFO needs consolidated numbers for board reporting.
- CRM (Salesforce, HubSpot, Pipedrive). Sales pipeline visibility across the group.
- HR and payroll (BambooHR, Gusto, Breathe). Compliance, people data, benefits administration.
- ERP and operational systems (job scheduling, field service management). Deepest integration, often deferred or handled last.
The mistake most first-time acquirers make? Assuming all systems need to be unified immediately. They don't. Deciding the right integration level for each acquisition is a strategic choice, not a default.
People and Culture: Where Most Value Leaks
You can migrate systems faster than people change behaviour.
The acquired team is anxious. They've heard promises before ("nothing will change"), and they've seen new owners break those promises within weeks. If they're high performers, they're already fielding LinkedIn messages from competitors.
The people side isn't soft-it's the hardest part. And it's where most value erodes. Key actions:
- Communicate early, often, and honestly. Explain why changes are happening, not just what's changing. Silence breeds rumour.
- Identify and engage "digital champions" within the acquired company-respected peers who can model adoption and troubleshoot resistance.
- Acknowledge competence threats. Staff may worry that new systems expose skill gaps or reduce their autonomy. Address this directly in training and onboarding.
One practical truth: the acquired team will judge you on how well you understand their workflows before you ask them to change. Conduct department-head interviews. Shadow key roles for a day. Show you value what they've built.
Processes and Operating Model: Combining Companies After Acquisition
Processes are the connective tissue between systems and people. Even with unified technology, misaligned processes create friction, rework, and frustration.
Your first task is to map critical workflows across both companies:
- How do quotes become jobs?
- How do invoices get approved and paid?
- How does customer data flow from initial inquiry to completion?
Then decide: which processes will be standardised group-wide, and which can remain flexible? Full standardisation drives efficiency and comparability but can alienate acquired teams if imposed too quickly. Defer non-critical workflows (e.g., internal meeting cadences) and focus on the processes that directly affect reporting, compliance, or customer experience.
A practical rule: if a process touches finance, compliance, or customer data, standardise it. If it's internal and doesn't affect group visibility, let it run.
Deciding What to Integrate, What to Defer, and What to Leave Alone
Not every acquisition needs full integration. This is the single most liberating realisation for operators under pressure to "do everything."
We use a three-tier framework to match integration depth to strategic intent:
Full Consolidation (High-Touch)
Single ERP, single CRM, unified processes. Best for operationally similar acquisitions where standardisation drives clear synergies (e.g., shared pricing, cross-sell opportunities, consolidated vendor contracts). Timeline: 3–6 months.
Spine Integration (Medium-Touch)
Unify the "spine"-email, finance, HR-but keep operational systems flexible. Best for acquisitions with different service lines or superior niche tools you don't want to lose. Timeline: 2–3 months.
Example: You acquire a pest control company that uses a brilliant field service app your other sites don't have. Migrate their email and accounting into your group systems, but leave their scheduling tool in place while you evaluate whether to roll it out group-wide.
Light-Touch Integration (Low-Touch)
Connect only what's needed for financial reporting and basic security. Leave operations largely autonomous. Best for acquisitions where independence is part of the value (e.g., strong local brand, testing before deeper integration, or earn-out structures that reward autonomy). Timeline: 2–4 weeks.
Deciding not to integrate is still a decision. The key is making it consciously, not by default or delay. Many operators drift into low-touch integration accidentally because they're overwhelmed-then pay the price 18 months later when they want to carry out group-wide changes and face entrenched resistance.
A quick diagnostic: if you need consolidated numbers within 60 days and visibility into sales pipeline, you're looking at Medium-Touch minimum. If the acquisition is strategic (shared customers, cross-sell potential, operational efficiency gains), plan for High-Touch from day one.
The 100-Day Integration Roadmap That Actually Works
Let's talk execution. Integration happens in phases, and each phase has specific objectives, risks, and success criteria.
Days 1–30: Stabilise and Assess
Objectives:
- Establish communication channels (weekly update emails, Slack/Teams access for acquired staff).
- Conduct a full system inventory: what software, who uses it, how, and what data lives where.
- Interview department heads to understand workflows, pain points, and fears.
- Assess data quality (duplicate records, incomplete fields, formatting inconsistencies).
- Map stakeholders: who makes decisions, who influences adoption, who will resist change.
Deliverable: A written integration plan that specifies which systems will be unified, deferred, or left autonomous-with timeline, ownership, and risk assessment.
This phase is unglamorous but essential. Skipping discovery is the fastest way to derail a migration. A structured integration audit surfaces risks before they become crises.
Warning: Don't promise "nothing will change" if you know changes are coming. It destroys trust when staff discover the truth weeks later.
Days 31–60: Execute Core Integrations
Objectives:
- Email and file migration. Move the acquired company onto your group email platform (Google Workspace or Microsoft 365). Migrate files and ensure permissions are mapped correctly.
- Finance consolidation. Migrate chart of accounts, historical transactions (at least 12 months), and vendor/customer records into your group accounting system.
- CRM unification (if applicable). Consolidate customer records, deal pipelines, and contact history. Clean duplicates and validate data before go-live.
These are the "spine" systems-the ones that enable group visibility and reporting.
Key success factors:
- Data cleaning before migration. Garbage in, garbage out. Deduplicate, standardise formats, and validate critical fields.
- Parallel running (2–4 weeks). Don't switch off legacy systems immediately. Run old and new in parallel so staff can validate accuracy and build confidence.
- Role-based training. Don't train everyone on everything. Focus on the workflows each role actually uses.
Warning: The "Conversion Trap." Files created in Google Docs break when forced into Microsoft Office (and vice versa). Native formats don't survive migration cleanly. Plan for reformatting time.
Days 61–100: Validate, Train, and Transition to Business as Usual
Objectives:
- Monitor adoption and troubleshoot issues (hypercare period).
- Provide follow-up training for staff who struggled during onboarding.
- Validate reporting accuracy: do the consolidated numbers match legacy system outputs?
- Sunset legacy systems once parallel running confirms accuracy.
- Document processes and create a runbook for the next acquisition.
Deliverable: A fully operational, unified business with clean data, trained staff, and consolidated reporting.
By day 100, you should be able to answer these questions confidently:
- Can the CFO produce consolidated financial statements without manual spreadsheet gymnastics?
- Can sales leadership see the full pipeline across all sites?
- Are staff using new systems without constant IT intervention?
If the answer to any of these is no, you're not done. Extend hypercare support and address gaps before moving to business as usual.
Common Integration Traps and How to Avoid Them
Let's talk about where integration goes wrong. These are the patterns we see repeatedly:
Rip and Replace Disaster
Forcing acquired companies onto your systems immediately, without understanding their workflows or earning trust. Result: rebellion, talent loss, and a spike in support tickets.
Solution: Interview first. Understand workflows. Explain why changes are happening. Configure new systems to support their needs, not just yours.
"We'll Get to It Later" Drift
Postponing integration until complexity is unmanageable. By the time you're ready, the acquired company has built custom workarounds, staff have dug in, and what should've been a 60-day project is now a six-month ordeal.
Solution: Decide your integration level (High/Medium/Low-Touch) within the first 30 days. Communicate it clearly. Stick to the plan.
One Size Fits All
Applying the same playbook to a 3-person tuck-in and a 200-person strategic acquisition. Integration depth should match acquisition size, strategic intent, and cultural fit.
Solution: Use the integration spectrum. Not every deal needs full ERP consolidation.
IT Abdication
Dumping integration onto your IT team without resources, authority, or business context. IT is already stretched with helpdesk, security, and infrastructure. Integration is a different skillset-migration planning, change management, data cleaning, and stakeholder diplomacy.
Solution: Treat integration as a business project, not an IT ticket. Assign a dedicated integration lead (could be COO, Head of Ops, or external partner) with authority, budget, and executive air cover.
Data Quality Surprise
Assuming data will migrate cleanly, then discovering on migration day that 30% of customer records are duplicates, addresses are incomplete, and product codes don't match.
Solution: Run a data quality assessment during days 1–30. Clean and validate before migration, not during.
What Winners Do Differently in Company Integration After Merger
Operators who consistently deliver value from acquisitions share a few habits:
They Treat Integration as a Discipline, Not a One-Off Project
After your second or third acquisition, you start to see patterns. Successful roll-ups document what worked, build reusable checklists, and refine their playbook with each deal. Integration gets faster, cheaper, and less painful over time.
They Bring in Specialised Help Early
Your internal IT team is brilliant at keeping the business running. But migration planning, CRM consolidation, and change management are distinct skillsets. Winners recognise this and bring in experienced partners for the heavy lifting-then hand off to internal IT for steady-state support.
When should you consider external help?
- Your IT team is underwater with BAU work.
- You're integrating complex systems (ERP, multi-site CRM).
- You've had a failed integration attempt and need to rebuild trust.
- You're doing 3+ acquisitions a year and need repeatable processes.
They Communicate Relentlessly
Weekly update emails. Open Q&A sessions. Transparent timelines. Winners over-communicate because they know silence breeds anxiety and rumour. Even when there's nothing new to report, saying "no updates this week, migration still on track for 15 March" reassures staff.
They Measure Adoption, Not Just Go-Live
Go-live is a milestone, not success. Winners track adoption metrics: login rates, data entry compliance, support ticket volume, and user sentiment. If adoption is lagging, they intervene-additional training, process tweaks, or identifying and addressing specific blockers.
They Learn from Each Deal
After day 100, conduct a retrospective. What went well? What took longer than expected? What would we do differently next time? Capture lessons in a living playbook and share it with the team handling your next acquisition.
Where to Start When Integration Feels Overwhelming
Integration isn't glamorous. It won't feature in the deal announcement or the PE sponsor's victory email. But it's where value is made or lost.
If you've just completed your first or second acquisition, the path forward is simpler than it feels:
- Audit what you've acquired-systems, workflows, and people dynamics.
- Decide your integration level: full consolidation, spine integration, or light-touch.
- Tackle email and finance first-they're quick wins that enable group visibility.
- Communicate constantly, train thoroughly, and measure adoption.
- Document what you learn so the next deal is faster.
And if you're feeling overwhelmed? That's normal. Integration is hard. But it's a known problem with known solutions. You don't have to figure it out alone.
We help roll-ups integrate systems, migrate data, and train teams-so the business keeps running while the systems change. If you'd like to talk through your specific situation, reach out. No pressure, no pitch. Just a conversation about what's realistic, what's risky, and what's worth deferring.
