Domo is being acquired by Progress Software. Map your exit now.

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 structured to close within Progress' fiscal year ending 30 November 2026, subject to regulatory clearance and customary conditions, and is backed by a voting agreement from key Domo shareholders. Domo the listed entity is expected to change its name and ticker after the deal closes. The operating business, the platform, the customer contracts, and the people move to Progress.

If your team runs on Domo, none of that changes what your dashboards show tomorrow morning. What it changes is who sets the pricing, the roadmap, and the support model for the platform your business logic is locked inside. That is worth thinking about now rather than at your next renewal.

What an acquisition by Progress usually means

Progress is open about how it grows. Its stated approach, which it calls its Total Growth Strategy, is to acquire mature software businesses with strong recurring revenue and high customer retention, then run them efficiently. The pattern is visible across Telerik, Ipswitch, Chef, Kemp, MarkLogic, and ShareFile. These are not turnaround stories or aggressive reinvention plays. They are established products bought for their sticky revenue and operated for durable cash flow.

That is a perfectly rational model, and for a stable back-office tool it can even be reassuring. But for customers of an acquired platform it tends to mean the same few things over time: steady maintenance rather than aggressive net-new innovation, tighter discipline on discounting, and firmer terms when the renewal comes around. The product keeps running. The leverage in the relationship shifts toward the new owner.

Why this raises the stakes for locked-in logic

Here is the part specific to Domo. Your Magic ETL dataflows, the joins, filters, aggregations, and formula tiles that took years to build, still live only inside Domo's proprietary format. You can see them in the visual builder. You cannot export them as SQL, check them into version control, or run them anywhere else. That was already the source of the lock-in. An ownership change does not loosen it. It simply hands the switching cost that kept you in place to a new owner who paid 400 million dollars specifically for that retention.

The uncomfortable question a data leader should be able to answer is not whether Domo will keep working. It probably will. The question is: if the new owner's pricing or direction does not suit us at renewal, could we leave, quickly and safely? For most Domo estates, the honest answer today is no.

The window is the integration period

Acquisitions like this follow a predictable arc: sign, close, integrate, repackage, renew. The best time to understand your exit options is during that window, before your next renewal lands under new ownership and new packaging, not after. Knowing what it would take to leave is what gives you a real position at the table, whether you choose to migrate or to stay on better terms.

Preparing an exit is not ripping and replacing

Preparing an exit does not mean tearing Domo out next quarter. It means knowing precisely what leaving would involve, before you need to. Concretely, that is a free lock-in assessment that gives you four things:

• A full inventory of your estate: every dataflow, dataset, connector, and scheduled job, not a guess
• A complexity classification that separates the standard data preparation from the genuinely bespoke logic, and flags the dead and duplicate work worth retiring rather than migrating
• A fixed-price, fixed-timeline plan to convert what matters into SQL, dbt, and Airflow running on infrastructure you already own
• Proof of equivalence: a parity harness that checks row-level and aggregate output against the Domo original before anything is cut over

Even if you never migrate, that report is leverage at your next renewal. If you do migrate, it is the plan for getting your team's work back onto infrastructure it controls, on a timeline you set. Either way, the point is the same: your workflows are your intellectual property, and the moment the platform they live in changes hands is exactly the moment to make sure they do not depend on a single vendor's balance sheet.