TL;DR: Automation platforms hold a business's operational logic, and switching costs are brutal — there's no tool to move workflows between Zapier, Make, and n8n. When a platform triples its price, teams are stuck rebuilding from scratch. A migration tool that exports and translates workflows is a clear opportunity.
The evidence
Workflow Automation surfaced as a distinct high-scoring cluster (8 posts scored 10+/15, intensity 7.4/10), concentrated on Discourse with corroboration from BlueSky and Medium.
The sharpest complaint is about lock-in. Users describe an automation platform tripling its cost overnight for the same workflows with no added value — and discovering there's no way out. There's no existing tool to move workflows between platforms, so switching means rebuilding every automation from scratch. The data explicitly calls manual migration time-consuming and error-prone.
The adjacent complaints round out the category: self-hosted n8n users struggling with reliable webhook delivery, and the security overhead of patching a self-managed deployment. But the migration gap is the one with no current answer.
Why this exists now
No-code automation went mainstream, and businesses moved real, revenue-critical logic onto these platforms. That logic is now an asset locked inside a proprietary format. Pricing power follows lock-in: once a platform knows you can't easily leave, the renewal conversation changes.
Self-hosting (n8n and similar) became the pressure-release valve — but only for teams that can absorb the migration cost. Everyone else is stuck. The gap between "I want to leave" and "I can leave" is the product.
The wedge
Don't build a new automation platform. Build the off-ramp.
- A converter that reads a workflow export from one platform and emits an equivalent on another — starting with the most common Zapier → n8n path.
- A coverage report that's honest about what mapped cleanly and what needs manual attention, so migrations are predictable.
- A managed option for the long tail that wants to self-host but can't run the migration themselves.
Land on "move off your automation platform in an afternoon, not a month," then expand into ongoing sync and backup.
Risks and honest caveats
- Moving target: platforms change their formats and node sets; the converter needs maintenance.
- Imperfect mappings: not every node has a 1:1 equivalent. Set expectations with a coverage report rather than promising magic.
- Platform pushback: incumbents have no incentive to keep exports clean — build defensively against format churn.
How to validate this further
Read the lock-in threads in the Pain Point Browser, pressure-test demand with how to validate a startup idea, and check the exact search terms in the Idea Validator. Related: an escape hatch for no-code platform code and switching payment processors without rebuilding.