Tableau to Fabric Migration With LOD Expressions Rebuilt as DAX, Not Just Dashboards Redrawn
Moving from Tableau is not a redraw. Your workbooks hold business logic in calculated fields, LOD expressions, table calculations and extracts. Our Tableau to Fabric migration inventories that estate, rebuilds the logic as DAX on governed semantic models, moves reporting to Power BI on Microsoft Fabric, and proves the numbers match before you switch Tableau off.
Tableau to Fabric Migration: Rebuilding Logic, Not Redrawing Dashboards
A Tableau estate is more than its dashboards. Behind them sit calculated fields, LOD expressions, table calculations, parameters, sets, extracts and Tableau Prep flows. A Tableau to Fabric migration has to carry that logic across, not just recreate the charts.
Power BI works differently from Tableau. It is built around a semantic model, so we consolidate the many workbook-level extracts into governed star-schema models, then rebuild reports on top. Microsoft's own migration guidance recommends focusing on the business questions a report answers rather than copying every visual exactly.
We decide per workbook. Content people use is rebuilt, near-duplicate workbooks are merged into one report, and workbooks nobody opens are retired. Where a workload should stay on Tableau for now, we say so, and plan the rest around your renewal date.
Six Core Components of Every Tableau to Fabric Migration
From inventory to parity sign-off: everything needed to move Tableau reporting to Power BI on Microsoft Fabric.
We list every workbook, data source, extract, Prep flow, schedule and permission, then check usage and owners. Each item is marked retire, consolidate or rebuild, with a complexity rating, before any build starts.
We replace workbook-by-workbook extracts with shared semantic models on a star schema, and choose Import, DirectQuery or Direct Lake per subject area based on data size, freshness and where the data already lives.
We translate FIXED, INCLUDE and EXCLUDE expressions, table calculations, parameters and sets into DAX measures, then test results at the original grain. Some logic moves upstream into Fabric transformations instead.
Extract refreshes and Tableau Prep flows are re-hosted where they fit best: Dataflows Gen2 for light shaping, pipelines for orchestration, notebooks or SQL for heavier transformation, landed in OneLake.
We rebuild priority workbooks as Power BI reports and apps, mapping Tableau actions and filters to slicers, cross-filtering, drill-through and bookmarks, and deciding report versus dashboard per view as Microsoft's guidance advises.
We map Tableau projects, groups and user filters to workspaces, apps, roles and row-level security, then run a parity framework with report owner sign-off before cutover and set up usage monitoring afterwards.
LOD Expressions to DAX: How We Translate Tableau Calculations
A Tableau LOD expression fixes the level of detail inside the calculation. A DAX measure responds to the filter context of the report. So the translation is about controlling filter context, and every pattern is tested against the Tableau result. Illustrative patterns only: the right DAX depends on your model.
{ FIXED [Customer] : MIN([Order Date]) }CALCULATE ( MIN ( Sales[Order Date] ), REMOVEFILTERS (), VALUES ( Customer[Customer] ) ){ INCLUDE [Customer] : SUM([Sales]) }AVERAGEX ( VALUES ( Customer[Customer] ), [Total Sales] ){ EXCLUDE [Region] : SUM([Sales]) }CALCULATE ( [Total Sales], REMOVEFILTERS ( Geography[Region] ) )SUM([Sales]) / TOTAL(SUM([Sales])) and RANK()DIVIDE ( [Total Sales], CALCULATE ( [Total Sales], REMOVEFILTERS ( Product ) ) ) and RANKX ( ALLSELECTED ( Product[Product] ), [Total Sales] )RUNNING_SUM(SUM([Sales])) and WINDOW_AVG()Visual calculations such as RUNNINGSUM, or DAX window functions, or a date-table measureParameters, sets, groups and binsWhat-if or field parameters, calculated columns or tables, and measure-based flagsNot every Tableau calculation has a one-line equivalent. Where a calculation is really data preparation, such as a row-level flag computed at extract time, we move it into Fabric so every report reuses it.
Tableau to Fabric Migration: Four Phases to Cutover
A structured plan so your Tableau reporting moves without disruption. Tableau stays live while Power BI is built and validated, so users switch only when their reports are signed off.
We inventory your Tableau Server or Cloud site, check usage and owners, and agree what to retire, consolidate or rebuild, with a complexity rating that flags LOD-heavy and table-calculation-heavy content.
Output: inventory and decisionsWe build the first governed semantic model, translate the hardest calculations and rebuild a pilot set of workbooks. The pilot sets DAX, naming and design standards and proves parity before the main build.
Output: signed-off pilot and standardsWe migrate in waves ordered by business priority and shared data. Each wave is checked against the Tableau original, and the report owner signs off every report before it moves on.
Output: migrated reports with sign-offWe run Tableau and Power BI side by side, cut over by audience, retire Tableau content when you are ready and hand over documentation, runbooks and training so your team can run the platform.
Output: retired Tableau content and handoverWhat the Timeline Depends On
We do not quote a duration before we have seen your estate. Length is driven by the number of workbooks still in scope after triage, the share that is LOD-heavy or table-calculation-heavy, the number of data sources and Prep flows, and how long you want to run in parallel. We fix the plan in the proposal after discovery and work back from your Tableau renewal date where there is one.
Triage complete; destination model design and wave plan approved.
First semantic model live; pilot reports match Tableau; standards agreed.
Each wave validated and signed off by report owners.
Users moved by audience; Tableau content retired, ideally ahead of your renewal date.
How We Price a Tableau Migration
You see real effort on your own data before committing to the full programme. Price is driven by workbook count, calculation complexity, data source and Prep flow count, security requirements and parallel-run length.
We inventory your Tableau estate and give you a triage, a complexity profile and a recommended scope, at no cost.
No commitmentA priced pilot that builds one semantic model and rebuilds a representative set of workbooks, so the approach and effort are proven on your data.
Fixed scope and feeRemaining waves are quoted by complexity tier once the pilot gives real numbers, as fixed fee per wave or on a time and materials basis, whichever suits you.
Your choice of modelWhy Choose Us for Tableau to Fabric Migration
Six reasons teams trust us to move Tableau reporting to Power BI without losing the numbers their business relies on.
Translating Tableau calculations is where migrations stall. We map each pattern to DAX, test it at the original grain and move upstream anything that is really data preparation.
Hundreds of workbooks usually mean hundreds of private extracts. We consolidate them into shared semantic models first, so each business metric has one definition.
Long-lived Tableau sites carry workbooks nobody opens. We find them first, so you rebuild and test only what the business uses.
We do not switch reporting until totals, LOD results and filtered views match the Tableau original and the report owner signs off.
The same team designs the OneLake data layer, the semantic models and the reports, so definitions stay consistent from source to chart.
You receive architecture notes, runbooks and a team walkthrough, and we can train your Tableau authors in Power BI and DAX, so your team runs the platform without us.
The starting point: a Tableau site that has grown for years. Many workbooks, each with its own extract, and several different calculations of the same revenue figure. Finance and sales cannot reconcile their numbers, and a Tableau renewal is approaching.
What we do: triage the site, retire what nobody opens, build one governed semantic model for the shared subject area, translate the LOD-heavy calculations to DAX measures and rebuild the priority workbooks as Power BI reports. Each report is checked against the Tableau original and signed off by its owner.
What the client team gets: one definition per metric, fewer reports to maintain, documented DAX, and authors trained to extend the model. Tableau is retired in stages once parallel running confirms the numbers hold.
Other services and guides our clients use alongside Tableau to Fabric migration.
Common Questions About Tableau to Fabric Migration
Still deciding? These are the questions teams ask most before they plan their move off Tableau.
Book a Free Call →Start Your Tableau to Fabric Migration Plan
Book a free assessment. We will inventory your Tableau workbooks, flag the LOD-heavy content and recommend what to rebuild, consolidate or retire, at no cost.