Concept card

Tableau Next — Salesforce-built agentic platform alongside classic Tableau

As of 2026-10-09

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Tableau Next?

Tableau Next is a separate analytics platform built by Salesforce on its own platform (Hyperforce, Einstein, Data Cloud) alongside classic Tableau, which Salesforce acquired in 2019 for $15.7B — and the field has not yet priced what moving workloads to it will cost.

What it is

Tableau Next is Salesforce's agentic analytics platform, built natively on the Salesforce platform (integrated with Data 360 and Agentforce) to combine the best of CRM Analytics, the Tableau products Salesforce acquired (which its documentation now calls "Tableau by Tableau": Desktop, Cloud, Server, Prep) and AI. It is positioned as part of a unified, interoperable portfolio rather than as a replacement: Tableau Cloud, Server and Desktop reach Tableau Next's semantic models through a Tableau Semantics connector.

Why it matters to an SAP consultant

It is the clearest recent example of a pattern worth recognising: a vendor building a parallel, AI-native platform around an acquisition it still sells. The consequence for a client is never only features — a client that chooses to move workloads faces migration effort, changed licensing and a different integration surface, with the vendor setting the commercial terms and the pace of the roadmap.

That pattern is the actual lesson, and it applies to SAP's own consolidation as much as to Salesforce's. A consultant who can name it is more useful than one who can compare two BI tools.

How to position it

When a client raises Tableau Next, the productive question is not which product is better but what adopting the new platform costs the customer: which extensions survive, what happens to existing workbooks, and whether the governance model changes. Those questions are answerable and they move the conversation to total cost.

Why it matters

SAP-anchored customers running Tableau face a decision on whether and when to adopt Tableau Next alongside classic Tableau, not a distant one.
Salesforce publishes no end-of-sale date for classic Tableau, so the decision is about timing and cost, not a cut-off — confirm support dates in writing.
The lack of a priced migration cost is itself the finding — treat any vendor estimate as a conservative anchor, not a quote.

Key points

Tableau Next is a separate analytics platform built by Salesforce on Salesforce infrastructure (Hyperforce, Einstein, Data Cloud), positioned inside an interoperable portfolio alongside classic Tableau (Cloud, Server, Desktop).
It is the clearest recent example of a vendor building a parallel, AI-native platform around an acquisition it still sells — the pattern matters more than the product.
For a client that chooses to move workloads, the consequence is migration effort, changed licensing and a different integration surface, with the vendor setting commercial terms and roadmap pace.
The same pattern applies to SAP's own consolidation; a consultant who can name it is more useful than one who only compares features.
Salesforce states the AI-grounding motive itself: Tableau Next integrates natively with Agentforce via Data 360 (Salesforce Data Cloud, renamed 14 October 2025) so the agent reasons over Tableau's semantic layer with no integration hop.
General availability is staged: Tableau Next reached GA for ISVs in April 2026; a separate GA date for direct enterprise customers should be checked before quoting a client a firm timeline.
The precise SAP parallel: SAP Business AI Platform (unveiled Sapphire 2026, 2026-05-12/13) unifies BTP + Business Data Cloud + Business AI so Joule grounds reasoning in one SAP Knowledge Graph — the same 'AI agent wants to own the semantic layer' logic Salesforce states for Tableau Next.
No primary source published by September 2026 prices a classic-Tableau-to-Tableau-Next migration; a consultant who scopes and estimates that cost first captures the engagement rather than reacting to a vendor timeline.

Terms used on this page

Reusable IP: An artifact, checklist, or model that can be reused across clients without copying client-specific data.
Hyperforce: Salesforce's own cloud infrastructure layer (built on public-cloud regions) that Tableau Next runs on natively, replacing Tableau's prior separate hosting stack.
Agentforce: Salesforce's agentic AI platform; Tableau Next ships native Agentforce skills (Data Pro, Concierge, Inspector) so the agent can act on Tableau's semantic layer directly.
Data 360: Salesforce's data platform, renamed from Data Cloud on 14 October 2025; Tableau Next's zero-copy data integration runs through it.
Zero-copy integration: A pattern where an analytics or AI layer queries data in place rather than duplicating it — the specific mechanism both Tableau Next (via Data 360) and SAP (Joule via SAP Knowledge Graph over Datasphere/S/4HANA) claim to use.
Re-platforming: Rebuilding an acquired or legacy product natively on the acquirer's own infrastructure and data model, rather than maintaining it as a separately-integrated product — the general pattern this card is named for.
Platform-native application: An application built to run directly inside a vendor's own cloud platform (its identity, data model, and compute layer) rather than connecting to that platform via an external integration.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →