What happens when your automation tool gets acquired

Every infrastructure tool you depend on will eventually be acquired, merged, or taken private. This isn't pessimism. It's pattern recognition.

The history of enterprise software follows a rhythm as predictable as the tides: a startup builds something useful, customers build their operations around it, a larger company or private equity firm acquires it, and the economics shift. Not gradually. Abruptly. The tool that once competed on value starts extracting it.

We've watched this cycle play out across databases, CRMs, virtualization platforms, and ERP systems for three decades. But the current wave of consolidation in workflow automation - the layer that connects every other system a business runs - carries a specific and underappreciated risk. When ownership of that layer changes, the blast radius covers the entire operation.

The acquisition playbook

The pattern has four stages. They don't vary much.

Stage one: acquire the platform while it still has competitive pricing and a loyal user base. Stage two: restructure the pricing model - rename units, bundle features, shift from perpetual to subscription. Stage three: raise prices, gradually at first, then dramatically once migration costs exceed the increase. Stage four: lock customers deeper into the ecosystem through proprietary formats, bundled services, and exclusive integrations.

Oracle wrote this playbook in 2004 when it launched a hostile takeover of PeopleSoft for $10.3 billion. PeopleSoft's customers were so alarmed that the company created an unprecedented Customer Assurance Program - promising two to five times their money back if Oracle reduced product support. Oracle completed the acquisition anyway. Within days, it laid off half of PeopleSoft's workforce. Customers who'd built their entire HR and financial operations on PeopleSoft found themselves paying escalating maintenance fees - eventually reaching 22% of the original license cost annually - for software that was no longer being actively developed.

The maintenance trap became the template. Don't kill the product. Let it decay. Charge more to keep it alive.

Salesforce refined the model in 2018 with its $6.5 billion acquisition of MuleSoft, the iPaaS leader. MuleSoft continued operating, but its product direction tilted sharply toward the Salesforce ecosystem. MuleSoft Composer for Salesforce launched in 2020 - a tool designed to deepen Salesforce integration, not to serve the open-market iPaaS customers who'd built on MuleSoft for its neutrality. The integration platform became a moat reinforcement for its parent company.

Boomi followed a similar arc. Dell acquired it in 2010, grew it inside the corporate machine, then sold it to private equity firms Francisco Partners and TPG Capital for $4 billion in 2021. Informatica took the private equity path too - Permira and CPPIB acquired it for $5.3 billion in 2015, took it public, and ultimately exited through an $8 billion sale to Salesforce in 2025. Each transaction optimized for the acquirer's returns. The customers' operational continuity was a secondary concern at best.

We can argue about whether any individual deal was good or bad for customers. But the structural incentive is consistent: financial buyers acquire infrastructure tools to extract margin, not to invest in product innovation.

What happened to Integromat

The case study that matters most for our industry is Integromat.

In October 2020, Celonis acquired Integromat - a Czech-built automation platform with over 11,000 customers and a reputation for being the affordable, technically capable alternative to Zapier. The deal was valued at over $100 million. Celonis described the acquisition as an acceleration of its "execution management" vision.

Integromat was rebranded to Make in 2022. The user interface got a refresh. The positioning shifted from scrappy underdog to enterprise automation layer.

Then the pricing started moving.

Make's billing model switched from operations to credits in August 2025. The conversion was nominally one-to-one - one operation equals one credit. But the new credit system introduced variable costs. AI modules, complex API calls, and bulk data processing started consuming multiple credits per action. A scenario that once cost 100 operations could now consume 150 to 200 credits depending on complexity. Community members called it "a real jab at non-enterprise creators." Users reported that iterators burned through credits faster than they'd expected, and that bulk data processing had effectively become a premium feature.

In November 2025, Make adjusted overage pricing again. The pattern was familiar: incremental changes, each individually defensible, collectively amounting to a fundamentally different cost structure than the one customers originally chose.

Celonis itself was valued at $7.7 billion. Make contributed roughly $52.6 million in ARR - a small fraction of the parent company's revenue. That ratio matters. When your platform is a subsidiary generating less than 7% of the parent's revenue, your interests as a customer don't set the corporate agenda. You're a line item, not a priority.

The Broadcom playbook comes to automation

But the most instructive case didn't happen in automation at all. It happened in virtualization.

In November 2023, Broadcom completed its acquisition of VMware - the company whose hypervisor ran the majority of enterprise workloads worldwide. What followed became the defining cautionary tale of infrastructure acquisition in the 2020s.

Broadcom eliminated perpetual licenses entirely. Every VMware customer was forced into subscription-based pricing. The company consolidated dozens of individual products into a handful of bundles, requiring customers to pay for capabilities they didn't need. Minimum core counts jumped from 16 to 72, meaning small deployments paid for licenses that far exceeded their actual usage.

The price increases were staggering. European customers reported increases of 800% to 1,500%. AT&T faced a proposed increase of 1,050%. A UK university watched its VMware support costs surge from 40,000 pounds to 500,000 pounds - a 1,250% increase in a single renewal cycle. A CloudBolt survey found that 99% of VMware customers were concerned about the acquisition's impact, with 76% expressing extreme or high concern.

Gartner projects VMware's market share will likely fall from 70% in 2024 to 40% by 2029. But that decline will take five years. The customers who can't migrate quickly enough will pay the premium for years while they plan their exit. That's the trap. Migration takes longer than price increases.

This is the blueprint that should concern every automation buyer. Not because Broadcom is acquiring Make or Zapier, but because the economic logic is identical. Infrastructure tools with high switching costs and captured customer bases are ideal targets for price extraction. The automation market - where workflows are deeply embedded in daily operations, export formats are proprietary, and migration means rebuilding from scratch - fits the profile perfectly.

The private equity playbook for software is well documented: acquire, cut costs, expand margins, raise prices. Research from OpenView Partners shows that optimizing pricing alone can improve a software company's bottom line by 11% to 25%. For a financial buyer with a five-year hold period, that math is irresistible.

How to build acquisition-proof workflows

The businesses that survived the VMware repricing weren't the ones who predicted the acquisition. They were the ones who'd built optionality into their infrastructure from the start. The same principle applies to automation. And the time to build that optionality is before the acquisition announcement, not after.

The first defense is format portability. Workflows stored in open, documented JSON formats can be exported, analyzed, and rebuilt on another platform. n8n and Activepieces store workflows as portable JSON. Node-RED uses a documented flow format. Zapier, Make, and most proprietary platforms store workflows in formats that are partially or fully locked to their runtime. Before you build a critical workflow, ask whether you can export it in a format another platform could import.

The second defense is open-source foundations. When the code is open, an acquisition can't eliminate access to the technology itself. n8n operates under a Sustainable Use License - free self-hosting for internal use. Activepieces is MIT-licensed - the most permissive option available. Windmill is open-source and used by over 3,000 organizations. These projects can be forked, self-hosted, and maintained independently of whatever happens to the commercial entity behind them. That's a structural advantage no proprietary platform can offer.

n8n's $2.5 billion valuation and $180 million Series C - led by Accel with NVIDIA's venture arm participating - demonstrates that open-source automation can attract serious capital without sacrificing the self-hosting escape hatch. The company serves Vodafone, Delivery Hero, and Microsoft on its cloud platform. But the community edition remains free with unlimited executions. If n8n were ever acquired and repriced, self-hosted users could continue running their existing version indefinitely. That's what open source buys you: a floor beneath your feet that no acquirer can remove.

The third defense is modular architecture. Don't build one 40-step workflow when four 10-step workflows connected through webhooks will do the same job. Modular workflows are easier to migrate piecewise. They're easier to test. And they reduce the blast radius when any single platform changes its terms.

The fourth defense is documentation discipline. Every workflow should have a plain-language description of what it does, what it connects, and why it exists - stored outside the platform itself. When migration day comes, the teams that documented their logic will rebuild in weeks. The teams that didn't will spend months reverse-engineering their own processes. We see this pattern every time a platform forces a migration, and the gap between prepared and unprepared teams is measured in months of lost productivity.

The long game favors the portable

We're in the early stages of a consolidation cycle that will probably reshape the automation market over the next five years. The $7.7 billion iPaaS market grew 30% in 2023 alone. The five largest vendors (Salesforce, Oracle, Informatica, SAP, and Boomi) already control nearly 58% of it. The remaining independent platforms will face increasing pressure to sell, merge, or go private.

Not every acquisition destroys customer value. Some bring resources, stability, and faster development. But the historical record is clear: when a financial buyer acquires an infrastructure tool with high switching costs, prices go up. The median outcome isn't innovation. It's extraction.

The businesses that will weather this consolidation are the ones building on portable formats, open-source foundations, and modular architectures today. Before the acquisition announcements. Before the pricing restructures. Before the export features quietly disappear from the product roadmap.

Our bet is on portability. The automation platforms that win the next decade won't be the ones with the most features or the lowest introductory price. They'll be the ones whose users can leave, and choose not to.

The question isn't whether your automation platform will be acquired. The question is whether you'll have options when it happens.

Build workflows you can move.

Data verification: Acquisition dates, pricing changes, and valuation figures verified via TechCrunch, Network World, Make Help Center, Salesforce investor relations, and PitchBook as of March 2026. VMware price increase percentages sourced from CISPE member reports and individual customer disclosures.

Crux helps businesses find the right automation platform for their specific problem. We don't sell automation tools. We help you pick the right one.