Tableau Server · Tableau Cloud
Your calculated fields are worth more than your Tableau licence.
A Tableau alternative only pays off if your calculated fields and LOD expressions come along. Unwind Data extracts every workbook, data source, calculated field and LOD expression, documents it and translates it into an open semantic layer, so you renew or switch based on facts. Rebuild in Power BI, Omni or another tool without working the logic out again. A Logic Scan takes 5 working days and costs €4,950.
Starts with a free 30-minute intake call.
What we extract
What we take out of Tableau
Every object that carries logic is read, linked to what depends on it, and checked for use.
Workbooks and dashboards
Every sheet and dashboard, with usage and owner.
Published data sources
Shared data sources and which workbooks depend on them.
Calculated fields
The calculations behind your numbers, including duplicate and conflicting versions.
LOD expressions
FIXED, INCLUDE and EXCLUDE calculations, translated into clear definitions.
Parameters and filters
Choices and filters that decide what a dashboard shows.
Extracts and Prep flows
Preparation in Tableau Prep and extracts, and where the data comes from.
What you get
AI-native migration: more than new dashboards
Your logic leaves the old platform as something you own, can read and can query.
The result is a semantic layer your BI tools and AI agents share. Choosing one? Read dbt Semantic Layer vs Cube and the Open Semantic Interchange guide. How we expose it to AI: MCP-driven data consulting.
Curious what's in your environment? The Logic Scan shows you in 5 working days.
Book a Logic Scan for TableauOptional: Rebuild
Where can your Tableau logic go?
There is no single best destination. It depends on where your definitions should live next. This is what is left of your logic at each one.
Tableau Cloud or Tableau Next
You stay with Tableau. Workbooks move to Tableau Cloud as they are; Tableau Next adds Tableau Semantics, a shared semantic layer on Salesforce Data 360.
the dashboards are fine and the problem is hosting, or you already run on Salesforce.
Power BI
Calculated fields become DAX measures, LOD expressions become CALCULATE patterns. The logic is rewritten, not translated.
your organisation already runs on Microsoft.
OmniCalculated fields move into one shared model instead of living in every workbook.
you want self-service dashboards on one set of definitions.
SigmaA spreadsheet on your warehouse, without extracts. Models are built mostly in the interface, not in code.
your analysts build their own workbooks. Keep your definitions in dbt, so they don't get locked into one tool again.
dbt Semantic LayerCalculated fields and LOD logic become metrics in your dbt project, which every connected tool reads.
your team works in dbt, or you want to keep Tableau for now and make the logic portable.
Claude or ChatGPT
Claude Dashboards and the Data agent in ChatGPT write a query per chart on your warehouse. They only use your definitions when they can read them from a semantic layer; otherwise each chart works out its own number.
people want answers and quick dashboards in the assistant they already use. Both are new (Claude Dashboards is in beta), so keep a governed tool for reports many people rely on.
Tableau Cloud or Tableau Next
What is left of your logic: You stay with Tableau. Workbooks move to Tableau Cloud as they are; Tableau Next adds Tableau Semantics, a shared semantic layer on Salesforce Data 360.
Fits when: the dashboards are fine and the problem is hosting, or you already run on Salesforce.
Power BI
What is left of your logic: Calculated fields become DAX measures, LOD expressions become CALCULATE patterns. The logic is rewritten, not translated.
Fits when: your organisation already runs on Microsoft.

Omni
What is left of your logic: Calculated fields move into one shared model instead of living in every workbook.
Fits when: you want self-service dashboards on one set of definitions.

Sigma
What is left of your logic: A spreadsheet on your warehouse, without extracts. Models are built mostly in the interface, not in code.
Fits when: your analysts build their own workbooks. Keep your definitions in dbt, so they don't get locked into one tool again.

dbt Semantic Layer
What is left of your logic: Calculated fields and LOD logic become metrics in your dbt project, which every connected tool reads.
Fits when: your team works in dbt, or you want to keep Tableau for now and make the logic portable.
Claude or ChatGPT
What is left of your logic: Claude Dashboards and the Data agent in ChatGPT write a query per chart on your warehouse. They only use your definitions when they can read them from a semantic layer; otherwise each chart works out its own number.
Fits when: people want answers and quick dashboards in the assistant they already use. Both are new (Claude Dashboards is in beta), so keep a governed tool for reports many people rely on.
Whichever you choose, we first capture your definitions in Apache Ossie, an open standard. You pick the destination on facts, and your BI tools and AI agents keep using the same numbers.

Who does the work
One specialist for Tableau
Jnana Deepak Bhavani, 9 years of experience with Tableau, SQL and data migration. One fixed point of contact who signs off on the reconciliation.
Proof
What it looks like
metrics:
- name: net_revenue
expression: SUM(amount_excl_vat)
filters:
- is_intercompany = false
- is_credit_note = false
owner: finance
source: Sales.twbxCase
ExampleRetailer, 450 employees
126 objects (band M) · Logic Scan in 5 working days, Logic Extract in 4 weeks
- 212 calculated fields captured, 37 of them duplicates
- LOD expressions translated into semantic layer definitions
- Rebuilt in Power BI from documented definitions
Start here
Logic Scan for Tableau: €4,950
Inventory, complexity score, risk map and a fixed quote. 5 working days, credited when you commission the next step within 60 days.
Book a Logic ScanStarts with a free 30-minute intake call.
What does a full migration cost? Read how BI migration costs add up.
Frequently asked questions
Other sources
- SQL Server, SSRS, SSISSQL Server 2016 out of support since 14 July 2026.
- QlikView and Qlik SenseTake your load scripts with you, not just your dashboards.
- SAP BusinessObjectsBO 4.3 and Crystal Reports 2020 are running out.
- MicroStrategyOn-premises support ends on 31 December 2026.
- Power BIMake your DAX readable outside Microsoft.
- LookerLookML is already code. Now free your logic from Looker.
- Excel and AccessThe report that lives in one person's spreadsheet.