Concept card

Tableau Next — Salesforce-platform-native rebuild

As of 2026-07-23

Edited by Cédric-Olivier Mâry, 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 — Salesforce-platform-native rebuild?

Tableau Next relocates Tableau onto the Salesforce platform (Hyperforce, Einstein, Data Cloud) six years after Salesforce's $15.7B 2019 acquisition — and the field has not yet priced what migrating to it will cost.

What it is

Tableau Next is Salesforce's rebuild of Tableau as a platform-native application on the Salesforce infrastructure, rather than an acquired product maintained alongside it.

Why it matters to an SAP consultant

It is the clearest recent example of a pattern worth recognising: a vendor re-platforming an acquisition onto its own stack. The consequence for a client is never only features — it is migration effort, changed licensing, and a different integration surface, all arriving on the vendor's schedule rather than the customer's.

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 a re-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 an active 2026-2027 migration decision, not a distant one.
Postponing the decision past 2027 risks a forced cut-over with limited tooling support.
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 — Salesforce-platform-native rebuild is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.
For non-AI use cases, still define quality, adoption, and operating ownership.
Leave a reusable operating asset: memo, checklist, control table, and exception log.
A premium answer is short, trade-off explicit, and defensible in a steering committee.

Terms used on this page

Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.
Reusable IP: An artifact, checklist, or model that can be reused across clients without copying client-specific data.

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.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

SAP Analytics Cloud vs Tableau: Coexist or Migrate