Magic ETL is a proprietary format. Your logic does not have to stay in it.
Domo is a capable platform, and this is not an argument that it is a bad one. The argument is narrower and harder to dismiss: the transformation logic your team built inside Magic ETL is your intellectual property, and right now it exists only in a format one vendor controls.
That is the moat. Not the dashboards, which anyone can rebuild in a weekend. The dataflows underneath them, which took years, and which you cannot export as SQL, check into version control, or run anywhere else.
What the lock-in actually is
Magic ETL has no meaningful export
You can see the tiles and arrows in the visual builder. You cannot get the transformation out as SQL, diff two versions of a dataflow, or run it outside Domo. The logic is visible and inextricable at the same time.
No version control, no code review
Changes to a dataflow are not commits. There is no branch, no pull request, and no reliable history of who changed which join and why. Institutional knowledge lives in the heads of whoever built it.
Consumption pricing on your own data
Credits are metered against usage of a platform that holds the logic you wrote. The more central Domo becomes to daily reporting, the more the meter runs and the more the switching cost grows.
The estate grows quietly
Because a dataflow is quick to build in a visual tool, estates sprawl. Most teams we assess are surprised by their own dataflow count, and by how much of it is feeding reports nobody opens.
Where Domo stands right now
Progress Software agreed to acquire the platform business
On 22 July 2026, Progress Software announced an agreement to acquire substantially all of Domo's assets, its AI and data platform business, for approximately 400 million dollars in cash. The transaction is set to close within Progress' fiscal year ending 30 November 2026, subject to regulatory clearance and customary conditions.
Progress buys for retention, then runs for cash
Progress is open about its model. Its stated Total Growth Strategy is to acquire mature software businesses with strong recurring revenue and high retention, then operate them efficiently. The pattern runs through Telerik, Ipswitch, Chef, Kemp, MarkLogic, and ShareFile. That usually means steady maintenance over aggressive net-new innovation, tighter discipline on discounting, and firmer terms at renewal.
The switching cost is what was bought
An ownership change does not loosen the lock-in. It hands the switching cost that kept you in place to a new owner who paid for exactly that retention. Your dashboards will look the same next Monday. The leverage in the relationship will not.
The integration window is the window
Acquisitions follow a predictable arc: sign, close, integrate, repackage, renew. The time to understand your exit options is during that window, before the next renewal arrives under new ownership and new packaging.
What a typical estate is made of
Numbers from the estates we have assessed. Yours will differ, which is exactly why the assessment counts rather than estimates.
Standard preparation
Joins, filters, aggregations, and standard formula tools that transpile cleanly into SQL and dbt models.
Dead or duplicate
Dataflows feeding reports that no longer exist, and copies made during old projects. Retired rather than migrated.
Genuinely complex
Dense bespoke logic that deserves careful, verified conversion rather than a rewrite from scratch.
What converts into what
The mapping, component by component. Every row is verified against the original by the parity harness before it reaches production.
Deterministic transpiling. This is the structural majority of a typical estate and it converts predictably.
AI-assisted conversion with an engineer reviewing every output, then checked by the parity harness.
Sources are re-pointed at your warehouse. The BI layer keeps reading from tables, except now you own them.
Existing schedule, ordering, and retry behaviour carried over, with real lineage this time.
The easy part. Once the tables are yours, the visualisation layer is a commodity decision again.
Signs it is worth assessing now
- Your Magic ETL dataflow count is a number nobody in the building can state confidently
- A renewal lands in the next twelve months, under new ownership
- The engineer who built the core dataflows has left, or is about to
- Credit consumption is growing faster than the value anyone can point at
Any one of those is reason enough to run the free lock-in assessment. It is read-only, it takes two weeks, and the report is yours whether or not you ever migrate.
Other platforms
Find out what leaving Domo would actually cost.
The lock-in assessment is free, takes two weeks, and needs read access. You keep the report whether or not you migrate.