Skip to content

Domo is no longer an independent company. On September 22, 2026, Progress Software completed its $400 million acquisition of substantially all of Domo’s business, including the platform, the team, the customer contracts, and the Domo brand. The product isn’t being shut down, and Progress has said it will keep serving Domo customers. But ownership, roadmap, and pricing decisions now sit with a new parent company, and that has a lot of Domo customers asking whether they should stay, wait, or start planning a move.

This post covers what happened, what is and isn’t known about Domo’s future, how to decide whether to migrate, and the alternatives worth evaluating. We build Basedash, so we have an obvious interest here. We’ll be upfront about where Domo is still a reasonable choice and where other tools fit better.

What happened to Domo?

Here’s the timeline:

  • July 22, 2026: Domo announced a definitive agreement to sell substantially all of its assets and employees to Progress Software for $400 million in cash. The deal was structured as an asset purchase: Progress takes the operating business, technology platform, customer contracts, intellectual property, and foreign subsidiaries, and assumes certain liabilities.
  • September 22, 2026: Progress announced that the acquisition had closed, about two months earlier than the November 30 target Progress had given. Domo’s platform is becoming part of the Progress Data Platform portfolio.

A few details matter for customers:

  • The Domo brand moved to Progress. Domo, Inc., the former public company, keeps its cash and roughly $900 million in net operating loss carryforwards, and continues as a separate listed holding company under a new name and ticker. It no longer runs the product.
  • Domo brings about 2,400 customers. In its investor materials, Progress said roughly 86% of Domo’s annual recurring revenue comes from consumption-based pricing.
  • Progress is a serial acquirer. The Burlington, Massachusetts company has built its portfolio largely through acquisitions, including Ipswitch, Chef, Kemp, MarkLogic, ShareFile, and Nuclia. Domo is the latest addition to what Progress calls its “Total Growth Strategy.”

Is Domo shutting down?

No. When the deal was announced, Domo said that Progress “expects to continue serving Domo customers and supporting the Domo technology platform.” In its post announcing the close, Progress described Domo as strengthening its data platform and AI strategy. Your dashboards, DataSets, and scheduled reports keep working, and your contract carries over to Progress.

This is a different situation from the analytics tools that actually shut down, like Chartio, DataGPT, or the hosted version of Redash. Nothing is forcing you off Domo on a deadline. The question is whether the platform you renew in a year or two will look like the one you bought.

Why Domo customers are uncertain

Acquisitions don’t automatically make a product worse. Some acquired products get more investment than they had before. But several parts of this deal leave open questions for customers:

  • There’s no published roadmap yet. Progress has described Domo in terms of its own AI infrastructure strategy (“context and control” for AI), not in terms of Domo’s BI and dashboarding roadmap. Detailed product plans haven’t been announced. Progress said it would share more about the deal’s financial impact on its September 30 earnings call.
  • Progress expects cost synergies. Its investor presentation said cost synergies should be fully realized by the end of its 2027 fiscal year. In software acquisitions, cost synergies usually come from consolidating teams, infrastructure, and overlapping functions, and customers often feel that consolidation in support and in the pace of product development.
  • Pricing and packaging could change. Domo’s consumption pricing was already its most common complaint, with some G2 reviewers describing renewal increases of more than 1,000%. New owners often repackage acquired products or bundle them into existing suites. That isn’t necessarily bad, but it makes a multi-year budget harder to forecast.
  • The longer you wait, the more lock-in you have. Domo stores your data, your Magic ETL dataflows, your Beast Mode calculations, and your permission rules inside its cloud. Every new dataflow you build there is another thing to migrate later.

None of this means you need to leave Domo tomorrow. It does mean your next renewal is the right time to find out what the alternatives would cost you in money and effort.

Should you migrate off Domo now or wait?

The answer depends mostly on your contract date and how deeply you’ve built on Domo-specific features.

Stay on Domo for now if:

  • Your contract has more than a year left and pricing is locked.
  • Your team relies heavily on App Studio apps, Domo.AI agents, or other features without a clear equivalent elsewhere.
  • You don’t have the capacity to run a migration project in the next two quarters.

Start evaluating alternatives if:

  • Your renewal is within the next 6 to 12 months.
  • You’ve already had a painful renewal conversation, or your consumption costs keep climbing.
  • Most of your usage is dashboards, reports, and alerts, which are the easiest parts of Domo to replace.

Plan a migration if:

  • Your renewal is within the next few months and Progress can’t give you written commitments on pricing, support, and roadmap.
  • You were already frustrated with Domo’s pricing or performance before the acquisition.
  • You want your data and business logic in a platform you can leave without rebuilding everything.

For most teams in the middle group, a short parallel pilot is the lowest-risk option. Rebuild your three or four most important Domo pages in an alternative, compare the numbers and the cost, and decide with real data before the renewal deadline.

What to look for in a Domo replacement

Domo’s pitch was that one vendor handled everything: connectors, storage, ETL, BI, alerts, and embedding. Most Domo alternatives only replace the dashboard layer, and that affects how much work a migration takes. Judge replacements on these criteria:

  • How much of the stack it replaces. If an alternative only covers BI, leaving Domo also means buying an ingestion tool like Fivetran, a warehouse like Snowflake or BigQuery, and a modeling layer like dbt. That’s four contracts instead of one.
  • Connector coverage. List the sources your Domo instance actually syncs and check that each one is supported.
  • A real semantic and modeling layer. Your Magic ETL dataflows and Beast Mode calculations encode years of business logic. The replacement needs somewhere governed to put it.
  • Governance parity. Domo’s personalized data permissions (PDP) restrict rows per user. The replacement needs row-level security, SSO, audit logs, and certified content.
  • AI that works on your real data. Natural-language analytics is standard now, but accuracy on messy, real schemas varies widely between tools.
  • Embedding, if you used Domo Everywhere. Customer-facing dashboards need per-tenant data isolation and white-labeling.
  • Predictable pricing and an exit path. After an acquisition, pricing you can forecast is worth more than it used to be. So is keeping your data somewhere you can query directly.

The best Domo alternatives in 2026

1. Basedash: the closest full-stack replacement

Basedash is the closest match to Domo’s scope, because it covers the whole data stack, not just the dashboards on top of it. That means you can replace Domo with one platform instead of assembling four vendors.

Here’s how it maps to what Domo did for you:

  • Storage. Basedash Warehouse is a fully managed warehouse that’s provisioned automatically when you connect your first source, with backups, scaling, and maintenance handled for you. If you already run Snowflake, BigQuery, Redshift, Databricks, ClickHouse, or Postgres, you can connect it directly instead.
  • Ingestion. 750+ Fivetran-powered connectors cover sources like Salesforce, HubSpot, NetSuite, Stripe, Shopify, Google Ads, and Meta Ads, and sync them into your warehouse. You can also connect SQL databases directly.
  • Modeling and semantics. Basedash Models replace Magic ETL and Beast Mode. A model is reusable SQL plus documented dimensions, measures, and segments, with verification and full version history. You can describe the model you want in plain English and the AI builds it.
  • Governance. SSO (SAML and OIDC), SCIM, role-based access, row-level security, audit logs, and SOC 2 Type II, plus a self-hosted deployment option. The AI follows the same permissions as your users. See security for details.
  • BI and AI. Ask a question in plain English and Basedash writes the SQL against your governed models, picks a visualization, and shows the query behind every answer. In BI Bench, our public benchmark of AI data analysts, Basedash scored 92.1% accuracy, the highest of the tools tested.
  • Alerts, embedding, and AI clients. Automations replace Domo alerts and scheduled reports with delivery to Slack and email. Embedded analytics replaces Domo Everywhere. The Basedash MCP server gives Claude, ChatGPT, and Cursor governed access to the same data.

Pricing is published: the Startup plan is $1,000 per month plus AI usage for up to 25 users, with a 14-day free trial and no credit card required. The Enterprise plan adds custom seat counts, SSO, embedding, self-hosting, and dedicated support.

Where Domo still has an edge: App Studio for building custom data apps, native mobile apps, and a longer track record in large enterprises. If App Studio apps are central to how your company operates, plan how you’d replace them before you commit to any migration.

Best for: Domo customers who want to replace the entire platform in one move, and teams that want AI-native BI with pricing they can forecast. For a feature-by-feature breakdown, see Basedash vs Domo.

2. Power BI with Microsoft Fabric: best for Microsoft shops

Power BI on its own replaces only Domo’s dashboard layer, but combined with Microsoft Fabric (Data Factory for ingestion, OneLake for storage, and dataflows and notebooks for transformation) Microsoft offers something close to an all-in-one stack. Power BI Pro runs about $14 per user per month and Premium Per User about $24, with Fabric capacity priced separately.

The tradeoff is ecosystem commitment. Fabric works best when your company already runs on Azure, Microsoft 365, and Teams. DAX has a steep learning curve, and Copilot works best on well-built semantic models.

Best for: Microsoft-centric enterprises that are willing to standardize on Fabric. See Domo vs Power BI.

3. Tableau: best for visualization depth

Tableau remains the standard for sophisticated, presentation-grade visualizations, and Tableau Prep, Pulse, and Tableau Agent add data prep, proactive insights, and AI assistance. It’s owned by Salesforce, which gives it long-term backing and strong CRM integration.

Tableau doesn’t replace Domo’s ingestion or storage, so you’ll need a warehouse and ELT tool underneath. Costs grow quickly with Creator licenses at around $75 per user per month.

Best for: analyst-led teams where visualization craft matters more than an all-in-one platform. See Domo vs Tableau.

4. Sigma: best for spreadsheet-fluent teams with a warehouse

Sigma gives finance and operations teams a spreadsheet-style interface that runs live on Snowflake, BigQuery, Databricks, or Redshift. For Domo customers that used Cloud Amplifier to keep data in their own warehouse, Sigma can be a natural landing spot.

Sigma doesn’t include ingestion or storage, and pricing is sales-led. If you don’t already operate a warehouse, you’ll need to set one up first.

Best for: spreadsheet-heavy teams with a mature cloud warehouse. See Domo vs Sigma.

5. Looker: best for code-governed metrics on Google Cloud

Looker’s LookML semantic layer is still the reference point for governed, version-controlled metrics, and its Gemini integration and BigQuery alignment make it a natural fit for Google Cloud companies.

Moving Domo’s Magic ETL and Beast Mode logic into LookML takes real analytics engineering work, and Looker doesn’t handle ingestion. Pricing is custom and generally high.

Best for: Google Cloud teams with analytics engineers who want metrics defined in code. See Domo vs Looker.

6. ThoughtSpot: best for search-first enterprise analytics

ThoughtSpot’s search interface and Spotter AI agent give business users a conversational way to explore governed data, and it also owns Mode for analyst-led SQL work.

It expects a well-modeled warehouse to deliver good answers and doesn’t replace ingestion or storage. Pricing is enterprise-oriented.

Best for: large enterprises with data teams that want search-driven self-service. See Domo vs ThoughtSpot.

7. Metabase: best for tight budgets

Metabase’s open-source edition is free to self-host, and Metabase Cloud starts at $100 per month. For small teams that used Domo mainly for a handful of internal dashboards, it’s the cheapest practical landing spot.

It doesn’t include ingestion, storage, or enterprise-grade governance, and its AI features are basic compared with purpose-built tools.

Best for: small, cost-conscious teams comfortable operating their own stack. See Domo vs Metabase.

Domo alternatives compared

Tool Domo layers it replaces AI experience Pricing model Best for
Basedash Connectors, storage, modeling, governance, BI, alerts, embedding Primary interface, with SQL shown Published: $1,000/month + AI usage Full-stack Domo replacement
Power BI + Fabric Most of the stack, inside Microsoft Copilot Per user plus Fabric capacity Microsoft-centric enterprises
Tableau BI and light data prep Tableau Agent and Pulse ~$15–75/user/month Visualization-led teams
Sigma BI on your warehouse AI assistance Sales-led Spreadsheet-fluent teams
Looker BI and semantic layer Gemini Custom Google Cloud teams
ThoughtSpot BI and search Spotter Custom (enterprise) Large enterprises
Metabase BI Basic Free / Cloud from $100/month Small budgets

For a longer breakdown, see our guide to Domo alternatives.

How to migrate from Domo to Basedash

A Domo migration is mostly a mapping exercise. Here’s how each Domo concept translates:

Domo Basedash
Connectors and Workbench Fivetran-powered connectors and direct database connections
Domo-hosted DataSets Basedash Warehouse, or your own warehouse
Cloud Amplifier Direct connection to Snowflake, BigQuery, Databricks, or Redshift
Magic ETL and SQL dataflows Basedash Models (SQL transformations)
Beast Mode calculations Measures and segments in Basedash Models
Personalized data permissions (PDP) Row-level security
Cards and pages Charts and dashboards, created from prompts or SQL
Alerts and scheduled reports Automations delivered to Slack and email
Domo Everywhere Embedded analytics
Domo.AI and the Domo MCP Server AI data analyst and the Basedash MCP server

A typical migration follows these steps:

  1. Inventory what’s actually used. Use Domo’s activity log and the DomoStats connector to find the pages, cards, and DataSets people use regularly. Most Domo instances carry a long tail of abandoned content that doesn’t need to move.
  2. Connect your sources. Reconnect the same SaaS tools and databases in Basedash. If you used Cloud Amplifier, connect your warehouse directly, since the data is already there.
  3. Backfill data that only lives in Domo. Some DataSets can’t be rebuilt from the source, like uploaded spreadsheets or history your source system no longer keeps. Export them from Domo (as files or through Domo’s DataSet API) and load them into your warehouse.
  4. Rebuild business logic as Models. Recreate your important Magic ETL dataflows and Beast Mode calculations as Basedash Models. You can describe each one in plain English and review the SQL the AI generates.
  5. Recreate permissions. Translate PDP policies into row-level security rules and map Domo groups to roles, using SCIM if you provision users from your identity provider.
  6. Rebuild your key dashboards. Start with the pages from your inventory. Describing a page in plain English usually gets you most of the way there.
  7. Move alerts, reports, and embeds. Recreate scheduled reports and alerts as automations, and swap Domo Everywhere embeds for Basedash embedded dashboards.
  8. Run both in parallel and cut over. Compare key numbers between Domo and Basedash for a few weeks, fix discrepancies, and switch before your Domo renewal date.

You can start a free trial and connect your first sources in minutes to see how your own data looks before committing to a migration plan.

The takeaway

Domo isn’t going away, but it now belongs to a company whose plans for the product haven’t been published yet. For some customers, that’s a reason to wait and see. For many others, especially those already unhappy with Domo’s pricing or facing a renewal soon, it’s a good reason to find out what switching would take.

If you’re evaluating a move, look past the dashboard layer. Domo replaced a whole stack, and the easiest migration is to a platform that does the same. Basedash gives you a managed warehouse, 750+ connectors, a semantic modeling layer, enterprise governance, and AI-native BI in one product with pricing you can plan around.

FAQ

Who acquired Domo, and when did the deal close?

Progress Software, the Burlington, Massachusetts infrastructure and AI software company (Nasdaq: PRGS), acquired substantially all of Domo’s assets for $400 million in cash. The agreement was announced on July 22, 2026 and the deal closed on September 22, 2026. Progress acquired the Domo platform, employees, customer contracts, intellectual property, and brand, and is making Domo part of its Progress Data Platform portfolio alongside earlier acquisitions like MarkLogic and Nuclia.

Will Domo’s pricing change under Progress Software?

Progress hasn’t announced pricing or packaging changes yet, and existing contracts carry over. But Progress told investors that about 86% of Domo’s recurring revenue comes from consumption-based pricing, and it expects cost synergies from the deal by the end of its 2027 fiscal year, so packaging changes at renewal are possible. Before renewing, ask your account team for written commitments on price caps, support levels, and the product roadmap, and compare that against a quote from an alternative.

Should Domo customers migrate now or wait?

It depends on your renewal date and how much you rely on Domo-specific features. If your contract has more than a year left and you depend on App Studio or Domo.AI agents, waiting for Progress to publish its roadmap is reasonable. If your renewal is within six to twelve months, or you were already unhappy with pricing, start a parallel pilot now so you can make the decision with real data instead of under deadline pressure.

How do I migrate from Domo to Basedash?

Start by inventorying the Domo pages, cards, and DataSets your teams actually use. Then connect the same sources in Basedash through its Fivetran-powered connectors or direct database connections, export any data that only exists in Domo, and rebuild Magic ETL dataflows and Beast Mode calculations as Basedash Models. Recreate PDP policies as row-level security, rebuild your key dashboards from prompts, move alerts to automations, and run both platforms in parallel before cutting over.

What happens to Magic ETL dataflows and Beast Mode calculations when you leave Domo?

They don’t transfer automatically, because both are proprietary to Domo. Treat them as specifications: document what each important dataflow and calculation does, then rebuild it in your new platform’s modeling layer. In Basedash, dataflows become SQL-based Models, and Beast Mode formulas become reusable measures and segments. Most teams find that only a fraction of their dataflows are still in active use, which makes this step smaller than it first looks.

Is Domo still a public company?

Not in the way it used to be. Domo, Inc., the Delaware holding company that traded as DOMO on Nasdaq, sold its operating business to Progress Software. It keeps its cash and net operating loss carryforwards and remains a separate listed company under a new name and ticker, led by founder Josh James. The Domo product, brand, employees, and customer contracts now belong to Progress Software.

Written by

Max Musing avatar

Max Musing

Founder and CEO of Basedash

Max Musing is the founder and CEO of Basedash, an AI-native business intelligence platform designed to help teams explore analytics and build dashboards without writing SQL. His work focuses on applying large language models to structured data systems, improving query reliability, and building governed analytics workflows for production environments.

View full author profile →

Basedash lets you build charts, dashboards, and reports in seconds using all your data.