Key takeaways
- Start with usage. Tableau Server and Tableau Cloud both record who views what, and that list decides how many workbooks you rebuild.
- Calculated fields, published data sources and extracts hold the business logic, so map them to warehouse definitions before rebuilding any dashboard.
- Tableau to Power BI is the most searched path, and Sigma, Looker and Omni are also sensible destinations depending on who builds the reports.
- Row-level security in Tableau usually lives in user filters or data source filters, and it has to be rebuilt and tested in the new tool.
- Moving from Tableau Server to Tableau Cloud is a different job with its own official tooling.
- 01Tableau workbooks
Plus data sources and extracts
- 02Inventory
Views, owners and calculated fields
- 03Warehouse semantic layer
One definition per metric
- 04Destination BI tool
Power BI, Looker, Sigma or another tool
- 05Parallel run and cutover
Totals and access compared
How do we inventory a Tableau estate?
Tableau’s admin views and the repository on Tableau Server show views per workbook and when each was last opened. Pull that first. Large estates usually turn out to have far more workbooks than people actively use, and every workbook you retire is one you do not have to rebuild or test.
For each workbook that survives, record its published data sources, any extracts and their refresh schedules, and the calculated fields it relies on. Copy the formulas out, because they are the metric definitions in practice.
- Workbooks and views, with view counts and last-viewed dates.
- Published and embedded data sources, and the tables behind them.
- Extracts, refresh schedules and incremental refresh settings.
- Calculated fields, level-of-detail expressions and parameters.
- User filters, data source filters and site permissions.
- Subscriptions and alerts people rely on.
What is the migration plan?
Run the plan per wave, grouped by team or subject area.
- Pull usage, assign owners and agree which workbooks to rebuild, merge or retire.
- Map each calculated field that matters to one metric definition and build it in a semantic layer on the warehouse.
- Rebuild the surviving dashboards in the destination tool on that layer, replacing extracts with live queries where the warehouse can take the load.
- Run Tableau and the new tool in parallel, comparing totals by period and segment and testing access with real users.
- Cut over when the owner signs off, then retire the workbooks, data sources and licences.
Why rebuild the metrics in the warehouse?
Tableau calculations are tied to the workbook or data source they live in. If you rebuild them as DAX inside Power BI, or as table calculations in another tool, you have a second copy of the same logic in a different language, and the next tool change starts from scratch. A warehouse semantic layer keeps one definition that Power BI, Sigma, Looker and AI agents can all read.
Is Power BI the only destination?
No. Power BI is a common choice for Microsoft shops, and Microsoft publishes a staged migration series for moving from another BI tool. Sigma is built around a connected spreadsheet that queries the warehouse live. Looker models data in LookML. Omni pairs a semantic model with SQL and spreadsheet interfaces. Choose by who builds the reports and test one representative dashboard in each candidate.
What about moving to Tableau Cloud?
Moving from Tableau Server to Tableau Cloud keeps the tool and changes the hosting. Tableau’s Migration SDK lets you build an application that moves users, groups, data sources and workbooks from Server to Cloud. The inventory step still applies, because a cloud move is a good time to retire workbooks nobody opens.
Tableau migration checklist
Use these as the exit checks for each wave.
- View counts pulled and every workbook has an owner and a decision.
- Calculated fields copied out and mapped to warehouse definitions.
- Extracts replaced or scheduled in the new tool.
- Totals match by period and segment for a full reporting cycle.
- User filters and row-level rules rebuilt and tested with real users.
- Subscriptions and alerts recreated or retired.
- Workbooks and licences have a switch-off date.
Where does Rig fit?
Rig is an AI-native data and systems integrator. A Tableau-focused partner or a Microsoft partner can staff a programme, and an in-house team can follow the official tools. Platforms like Rig handle mapping, parallel runs and cutover, and leave a governed semantic layer on the warehouse you already run.
Rig Migrate scopes the work and agrees a fixed delivery price, Rig Map holds the metric definitions afterwards, and Gateway controls which people and agents can query them. The Tableau migration page describes the service, and the Tableau vs Power BI comparison helps with the destination choice.
Tools and approaches
- Tableau Migration SDK
- A framework for building your own application to move users, groups, data sources and workbooks from Tableau Server to Tableau Cloud.
- Microsoft Power BI migration guidance
- Microsoft’s staged series for migrating from another BI platform to Power BI, starting with a prioritised inventory.
- Sigma
- A BI and apps platform with a connected spreadsheet that queries the warehouse directly.
- Omni
- An analytics platform with a shared semantic model, SQL and spreadsheet interfaces.
Common questions
How do you migrate off Tableau?
Pull usage, keep the workbooks people open, map their calculated fields to metric definitions in a warehouse semantic layer, rebuild the dashboards in the destination tool on that layer, run both in parallel, then cut over wave by wave.
Is Tableau to Power BI the only sensible path?
No. Power BI suits many Microsoft shops, and Sigma, Looker and Omni are reasonable destinations too. Some teams stay on Tableau and move to Tableau Cloud. Test a representative dashboard before you choose.
What happens to extracts and row-level security?
Extracts are replaced by live queries or scheduled refreshes in the new tool. Row-level rules in user filters or data source filters have to be rebuilt in the destination, or better in the warehouse, and tested with real users.
What happens to Tableau metrics and data sources in a move?
Copy the calculated fields out of the published data sources and workbooks, define each metric once in a warehouse semantic layer, and point the new dashboards at those definitions.
Who usually runs a Tableau migration?
An in-house team can do this with the vendor’s own tools, a systems integrator can staff the programme, or an AI-native data and systems integrator like Rig can run the mapping and cutover.
Sources
Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.