The cost of staying locked in, while the vendor sorts itself out
Domo's going-concern questions and Alteryx's private-equity ownership are two different situations with the same lesson: your workflows are your IP, and they should not depend on someone else's balance sheet.
We are not in the business of predicting what happens to any specific vendor. We are in the business of making sure it does not matter to your team either way. Two situations in the market right now make that point better than we could argue it in the abstract.
Domo
As of mid-2026, Domo has disclosed a forbearance agreement with its lender that raised going-concern questions, its board has been running a strategic review since February, and the company has confirmed advanced negotiations on a potential transaction. The stock has lost roughly 70% of its value this year. None of that means Domo disappears tomorrow. It does mean the platform's ownership, pricing, roadmap, and support model are being decided in a negotiation that current customers are not part of.
Alteryx
Alteryx's situation is the other end of the same risk. Since its $4.4B take-private by Clearlake Capital and Insight Partners, customers report stiffer renewal proposals, reduced discount flexibility on smaller deployments, 3-7% annual escalation clauses, and pressure to move to new packaging and cloud migration on the vendor's timeline. Server licensing alone lists at roughly $58,500 a year for four worker threads, before a single Designer seat is counted.
The actual question worth asking
Whatever the outcome for either vendor, the useful question for a data leader is the same one: if we needed to leave, could we? For most estates built on either platform, the honest answer today is not quickly. Dashboards can be rebuilt in a weekend. The dataflows and workflows underneath them, the joins, filters, aggregations, and formula logic that took years to build, exist only inside a proprietary format that the vendor controls.
In our experience running these migrations, 60 to 80% of a typical estate is standard data preparation that translates cleanly into SQL, dbt models, and Airflow DAGs running on infrastructure the customer already pays for. Another 15 to 30% is usually dead or duplicate work that should be retired rather than migrated. The remainder is genuinely complex logic that deserves careful, verified conversion rather than a rewrite from scratch.
Knowing precisely which is which, before you commit to anything, is the entire point of running a free assessment. Whether or not you ever migrate, that report is leverage at your next renewal. If you do migrate, it is the fixed-price, fixed-timeline plan for getting your team's work back onto infrastructure it controls.