M&A Is Surging. Your Procurement Stack Isn’t Ready.

Global M&A activity is on pace to hit $6.4 trillion in 2026, according to Morgan Stanley. That means thousands of companies are about to inherit tech stacks they did not build, ERPs they do not understand and procurement processes that contradict their own. Post-merger procurement integration is where deal value goes to die, and most organizations do not realize it until the damage is done.

Announced deals surged 64% year over year in Q2 2026. Completions rose 33%. Software, utilities, energy and healthcare are leading the charge. For finance, operations and procurement leaders, the question is no longer whether a merger will touch their systems. It is how fast they can unify procurement operations across entities that were never designed to work together.

The conventional playbook says to consolidate your enterprise resource planning (ERP) systems first. That advice is wrong, and this post explains why.

By Lihi Lutan, Co-Founder and CEO

Co-Founder and CEO of Opstream, previously COO of StokeTalent (acq. Fiverr) and VP Operations at Taboola where she helped scale the company from $8M to $1B in revenue.

View LinkedIn profile →

The 2026 M&A Boom Is Creating a Procurement Problem

Deal volume is accelerating faster than organizations can absorb. Morgan Stanley analysts noted that a lighter regulatory environment and buoyant equity markets have made the M&A backdrop “more constructive” than at any point since 2021. Alternative asset managers alone are sitting on approximately $4.3 trillion in available capital.

For procurement and finance teams, every closed acquisition creates an immediate operational problem. The acquired company brings its own ERP, its own vendor master, its own approval workflows and its own contract repository. None of it maps cleanly to the acquirer’s systems.

The result is predictable:

• Duplicate vendors coded differently across systems, making spend analysis impossible
• Broken approval chains where the acquired entity’s hierarchy does not match the parent’s governance model
• Zero spend visibility across entities for weeks or months after close
• Compliance gaps where security reviews, insurance validations and vendor questionnaires fall through the cracks

Order-to-cash and procure-to-pay workflows are typically the first to break. When procurement systems are not integrated or stabilized, downstream problems cascade into billing, cash flow, vendor management and inventory.

What Happens to Procurement Systems After a Merger?

The short answer: procurement becomes chaotic. Two organizations with different purchasing processes, different vendor databases and different ERP systems must suddenly operate as one. In practice, they rarely do.

Most companies face three scenarios post-close:

• Full ERP consolidation: Migrate the acquired entity onto the parent’s ERP. This takes 12 to 24 months and costs millions. Procurement waits in limbo.
• Parallel operation: Run both ERP systems indefinitely. Procurement teams toggle between systems, duplicate data entry and lose visibility.
• Orchestration layer: Deploy a platform that sits above both ERPs, unifying procurement workflows, vendor data and spend analytics without replacing either system.

Most organizations default to option one or two. Option three is the fastest path to operational continuity, yet it is the least discussed in the market.

Why ERP Consolidation Is the Wrong Starting Point

ERP consolidation is necessary eventually. It is also the slowest, most expensive and most disruptive path to procurement continuity. Starting there is a strategic mistake.

Here is what the data shows:

• Full ERP integration takes 12 to 24 months for enterprise companies. Mid-market deals average 12 to 18 months.
• 50% of ERP implementations fail on their initial attempt due to poor planning, according to industry benchmarks.
• Disparate naming conventions, inconsistent hierarchies and duplicated records disrupt reconciliation, delay reporting and increase audit exposure across departments.

During those 12 to 24 months, procurement teams operate in a fog. They cannot see consolidated spend. They cannot enforce consistent approval policies. They cannot identify duplicate vendors across entities. Every month of delay erodes the synergy targets that justified the acquisition.

The orchestration layer does not eliminate the need for ERP consolidation. It removes the urgency. Procurement teams get cross-organization spend visibility, unified approval workflows and vendor management from day one, while IT plans the ERP migration on a reasonable timeline.

How Long Does Post-Merger Procurement Integration Actually Take?

It depends entirely on the approach. Organizations that lead with ERP consolidation typically wait 12 to 18 months before procurement systems are stable. Companies that deploy an orchestration platform first can achieve operational procurement continuity in weeks.

Here is a realistic timeline for orchestration-first post-merger procurement integration:

• Days 1 to 14: Connect both ERPs. Map vendor masters. Establish unified intake for all procurement categories.
• Days 15 to 30: Deploy approval workflows that respect both entities’ governance structures. Enable centralized procurement with entity-specific routing.
• Days 31 to 60: Activate spend analytics across both entities. Identify duplicate vendors, overlapping contracts and consolidation opportunities.
• Days 61 to 90: Begin contract renegotiations with combined purchasing power. Establish vendor performance baselines across the merged organization.

Compare that to the traditional approach, where the first 90 days are consumed by ERP assessment and migration planning. No procurement improvements ship during that window.

Companies that complete financial consolidation within 30 days realize procurement and supply chain synergies two to three months faster than those that wait for full ERP integration.

The Orchestration Layer: Unifying Procurement Without Replacing Your ERPs

An orchestration layer connects to multiple ERPs, CLMs, HRIS tools and compliance systems simultaneously. It does not replace any of them. Instead, it creates a unified data model that normalizes vendor records, contract terms, spend data and approval hierarchies across every connected system.

This approach solves the three most urgent post-merger procurement problems:

• Entity resolution: The platform automatically identifies and merges duplicate suppliers, contracts and purchase orders across systems. Same vendor coded as “Acme Inc.” in one ERP and “ACME Incorporated” in another? Resolved automatically.
• Unified governance: Approval policies, spend thresholds and compliance requirements are enforced consistently across both entities from day one, without waiting for ERP migration.
• Real-time spend visibility: Finance teams see consolidated spend across all entities, categories and vendors in a single view. No manual data reconciliation.

Opstream connects to 120+ enterprise systems including SAP, Oracle, NetSuite, Workday and Microsoft Dynamics. For organizations running multiple ERPs post-acquisition, this means integration capabilities that work across every system in the stack, not just the primary one.

What PE Roll-Ups and Serial Acquirers Already Know

Private equity portfolio companies and serial acquirers live this problem at scale. A PE firm that acquires five companies in 18 months inherits five ERPs, five vendor databases and five sets of procurement workflows. Full ERP consolidation across the portfolio is a multi-year, multi-million dollar project. Some firms never complete it.

The ones that move fastest have learned a counterintuitive lesson: stop trying to consolidate ERPs and start orchestrating above them.

The orchestration-first approach gives PE-backed portfolio companies three advantages:

• Faster synergy capture: Procurement savings start in weeks, not quarters. Combined purchasing power becomes actionable immediately.
• Lower integration cost: No ERP migration fees, no data cleansing projects, no retraining programs. The existing systems keep running.
• Portfolio-wide visibility: Fund-level analytics across every portfolio company, every vendor and every spend category. This is the kind of visibility that drives better acquisition due diligence on the next deal.

Organizations that need to unify indirect and direct procurement across multiple entities find this approach particularly effective. It works across every procurement category: services, hardware, consulting, facilities and software.

About the Author

Lihi Lutan

Co-Founder and CEO, Opstream

Lihi Lutan is the Co-Founder and CEO of Opstream, changing the way companies buy.

Throughout her career, Lihi built and scaled business operations at startups and large corporations. Early in her career, Lihi was with Cyota (acq. RSA Security) as a team leader and project manager before moving to Thomson Reuters and Fundtech to manage global projects. Later, Lihi joined Taboola (NSDQ: TBLA) as employee 15, as VP Professional Services and Operations, leading the department as the company scaled from $8M to $1B in revenue. Transitioning from Taboola to StokeTalent (acq. Fiverr), Lihi served as the company’s COO.

Lihi holds an LLB of Law and BSc of Computer Science from Tel Aviv University.

Connect with Lihi on LinkedIn →