What this means for your store
Tableau Next brings semantic models, Pulse metrics, and org-wide visual standards on the Salesforce platform. CRM Analytics stays tied to Salesforce object sync, RLS predicates, and SAQL apps your sales ops team already runs. Tableau Next fits executive KPIs spanning finance GL and Snowflake orders. CRMA still wins when regional pipeline lives entirely in Opportunity datasets refreshed from CRM.
Scenario on a real storefront
A US B2B ecommerce platform adds Tableau Next for CEO revenue Pulse metrics while keeping regional pipeline in an existing CRMA app:
# Coexistence pattern
CRM Analytics (keep):
- Opportunity / Account grain with RLS
- Rep dashboards on Lightning Account pages
- SAQL: stage velocity, forecast category splits
Tableau Next (add):
- Semantic model: Finance GL + Salesforce + Snowflake orders
- Pulse: Net revenue, churn risk, marketing CAC
- Executive home on Salesforce landing page
# Do not rebuild every CRMA lens in Tableau on day one
# Map SKUs: CRMA Platform vs Tableau Cloud / Tableau Next
What to do next
- Switching mid-quarter without metric parity kills trust - run side-by-side pipeline totals before changing stand-up dashboards.
- Tableau Next semantic models may not replicate CRMA RLS one-to-one; revalidate partner portal access.
- Greenfield teams: ask your AE which bundle covers needed embedding and sync before buying overlapping licences.
Bottom line
CRMA for Salesforce-native sales datasets and embedded rep views; Tableau Next for cross-cloud executive analytics. Most B2B orgs run both for a while - reconcile KPIs first.