Why Acquisition Integrations Stall: A Systems Approach to Recovery

An acquisition integration is rarely incomplete because no one is working.

More often: everyone is working, but no one owns whether all the pieces actually come together.

Marketing owns brand integration. Operations owns process alignment. Finance owns consolidation. Technology owns system integration. Fulfillment owns inventory transitions.

Each function completes its piece.

The integration remains stuck.

The Fragmentation Problem

An integration typically involves:

• Product catalog consolidation (which SKUs go where?)
• Fulfillment transition (moving inventory and processes)
• Customer data migration (combining customer bases safely)
• Supplier and vendor transition (consolidating relationships)
• Process standardization (aligning operations)
• Team integration (roles, reporting, redundancy)
• System integration (connecting tools and platforms)
• Pricing and margin reconciliation (standardizing economics)

Each of these is a workstream. Each workstream has owners. But who owns the outcome?

If the answer is "everyone," the practical answer is often "no one."

The Integration Recovery Framework

Step 1: Define Done Objectively

Ask: What has to be true for this integration to be considered complete?

Vague answers: "Systems are integrated," "processes are aligned," "teams are working together."

Useful answers:

• All inventory is physically at the consolidated location
• Customer data is unified in a single CRM with no duplicates
• Both product catalogs are consolidated in a single system
• Supplier relationships are consolidated to single contracts
• Fulfillment is operating at target SLA from new location
• All processes are documented and can run without founder involvement
• Revenue reporting is unified
• Team redundancy is resolved

Write these down. Share them with stakeholders. Come back to this list 8 weeks from now—you'll either confirm completion or identify what's still missing.

Step 2: Establish Ground Truth

Do not ask teams: "How far along are we?"

Ask:

• What is 100% complete?
• What is partially complete (what % and what's left)?
• What has not started?
• What is waiting on an external dependency?
• What decision is needed to proceed?
• What problem emerged that changes timeline?

Document answers in a single source of truth (Google Sheet, Notion, Excel—doesn't matter, just one place).

Step 3: Map Dependencies

Create a simple dependency map:

Supplier Consolidation (8 weeks)
  ↓
Fulfillment Transition (6 weeks) — waits on supplier consolidation
  ↓
Inventory Migration (4 weeks) — waits on fulfillment transition
  ↓
System Cutover (2 weeks) — waits on inventory confirmation

Product Catalog Consolidation (8 weeks)
  ↓
Pricing Standardization (4 weeks) — waits on catalog consolidation
  ↓
Marketing Launch (2 weeks) — waits on pricing ready

Customer Data Migration (10 weeks) — independent of supplier work
  ↓
CRM Integration (4 weeks) — waits on data migration
  ↓
Sales Training (2 weeks) — waits on CRM ready

What controls the finish line?

Typically: supplier consolidation, fulfillment transition, and product catalog consolidation run longest and drive the overall timeline.

Step 4: Separate Workstream Ownership From Integration Ownership

One person must own the outcome: whether the entire integration crosses the finish line.

That person is NOT:

• The supplier consolidation owner
• The fulfillment owner
• The system integration owner
• The marketing owner
• Any single function

That person is responsible for whether all of these connect and produce a working business.

Titles: Integration Lead, VP of Integration, COO, Chief Integration Officer.

Whoever holds this role should be able to answer these 8 questions at any point:

1. Outcome: What are we integrating toward?
2. Current state: Where are we really right now?
3. Critical path: Which remaining items control the finish date?
4. Ownership: Who owns each major piece?
5. Dependencies: What is waiting on what?
6. Decisions: What unresolved decisions are blocking progress?
7. Risk: What could derail us?
8. Acceptance criteria: How do we objectively know we're done?

Step 5: Surface Decisions

Integrations often appear to stall due to execution when they actually stall due to decision paralysis.

Create a decision register:

Decision	Options	Owner	Deadline	Impact
Consolidate to Supplier A or Supplier B?	A (cheaper, slower), B (more expensive, faster)	COO	Week 3	If delayed, fulfillment transition starts late
Keep acquired company's fulfillment location or consolidate?	Keep (safer), Consolidate (cheaper)	Fulfillment lead	Week 2	Determines inventory migration schedule
Merge product catalogs before launch or run parallel?	Merge (simpler, riskier), Parallel (complex, safer)	Product/Ops	Week 4	Drives launch readiness timeline

Each unresolved decision should be visible as a project blocker with escalation path.

Step 6: Run From the Critical Path

Not everything in the integration is equally important.

The integration may have 40 open items.

But 5-6 control whether you launch on time:

1. Supplier consolidation
2. Fulfillment transition
3. Inventory migration
4. Product catalog consolidation
5. System cutover
6. CRM migration

Manage those aggressively. Everything else can move at a normal pace.

Weekly status on critical path only. Monthly updates on everything else.

Step 7: Weekly Integration Sync

15 minutes. Every Monday or Friday.

One person: the integration lead.

Questions:

• Did everything move as expected this week?
• Are any dependencies unblocked?
• Did any new risks emerge?
• Are any decisions pending owner response?

Document answers in a one-page integration status. Repeat weekly.

Common Integration Stalls (and causes)

Supplier consolidation is taking 16 weeks instead of 8:

• Likely cause: Renegotiating contract terms instead of standardizing quickly
• Fix: Accept that acquired company's terms may be worse initially. Lock in consolidation, renegotiate terms in Q2.

Inventory migration keeps slipping:

• Likely cause: No one owns the warehouse transition end-to-end
• Fix: Assign a dedicated fulfillment lead with authority to make logistical decisions

Product catalog consolidation is incomplete:

• Likely cause: SKU rationalization is being over-analyzed
• Fix: Decide SKU cuts 80% of the way there. Perfect rationalization can happen post-launch.

CRM data migration is stuck:

• Likely cause: Data quality is worse than expected. Trying to clean everything before migrating
• Fix: Migrate messy data first. Clean it post-migration in batches.

Systems are "integrated" but orders aren't flowing correctly:

• Likely cause: Integration lead didn't own end-to-end order flow testing
• Fix: Before declaring system integration done, run 100 test orders through the full flow.

The Integration Lead Checklist

Before the integration begins:

• Is there one person accountable for the outcome?
• Do we have a written definition of done?
• Do we have a dependency map?
• Do we have identified critical path items (5-6)?
• Do we have workstream owners assigned?
• Do we have a weekly sync scheduled?
• Do we have a decision register template ready?
• Do we have a communication plan for stakeholders?

If any of these is missing, the integration will stall.

If all are present, the integration will finish. It may not be perfect, but it will finish.