# Tableau Dashboard Complexity Analysis: A Scoring Rubric for Migration Effort

> Score Tableau dashboard complexity before migrating: the five dimensions that drive effort, a simple, moderate and complex rubric, and how to use the bands.

- Canonical: https://getantares.io/tableau-dashboard-complexity-analysis/
- Published: 2026-02-18
- Updated: 2026-08-11

---

Migration effort per Tableau dashboard is set by what the workbook calculates and where it reads from, not by how many charts sit on the canvas. Five dimensions account for most of the spread: calculation logic, data sources, interactivity, visualization types, and size and layout. Score those five across an estate and a dashboard count becomes an effort estimate you can defend.

Scores are worth producing only if something depends on them. Here they drive three decisions: which dashboards move in which wave, how many hours to budget per band, and which content is worth retiring instead of converting. Duration ranges built on those hours live on [how long a migration takes](/how-long-does-tableau-to-power-bi-migration-take/).

## What drives migration effort in a Tableau dashboard

Each dimension moves effort for its own reason, so they are scored separately rather than averaged into a single number too early.

| Dimension | Why it drives effort | Where to look next |
| --- | --- | --- |
| Calculation logic | [LOD expressions](https://help.tableau.com/current/pro/desktop/en-us/calculations_calculatedfields_lod.htm) and [table calculations](https://help.tableau.com/current/pro/desktop/en-us/functions_functions_tablecalculation.htm) restate into DAX under different evaluation rules, so each one is reviewed rather than transcribed | [LOD to DAX](/tableau-lod-expressions-to-dax/), [table calculations to DAX](/tableau-table-calculations-to-dax/) |
| Data sources | Blends, extracts and [custom SQL](https://help.tableau.com/current/pro/desktop/en-us/customsql.htm) have to become a model with explicit relationships before any report page can be validated against anything | [blending to relationships](/tableau-blending-to-power-bi-relationships/), [custom SQL](/tableau-custom-sql-to-power-bi/) |
| Interactivity | Sets, set actions and chained dashboard actions have no single Power BI object behind them, so they are rebuilt from cross-filtering, drillthrough and bookmarks | [sets to DAX](/tableau-sets-to-dax-measures/), [actions to drillthrough](/tableau-actions-to-power-bi-drillthrough/) |
| Visualization types | Bar, line and scatter charts map across directly; dual-axis combinations, custom shapes, dense cross-tabs and bespoke maps take design time per view | [workbook to PBIX conversion](/tableau-workbook-to-pbix-conversion/) |
| Size and layout | Sheets per [dashboard](https://help.tableau.com/current/pro/desktop/en-us/dashboards_create.htm), floating containers and device-specific layouts multiply assembly work even when nothing is calculated | Assembly, theming and layout standards |

## The simple, moderate and complex rubric

Three bands are enough. A finer scale invites argument over whether something is a six or a seven without changing what anybody does next.

| Band | Criteria | What it means for the approach |
| --- | --- | --- |
| Simple | No LOD expressions or table calculations, one governed source or one extract, filters and standard chart types, a handful of sheets | Convert first, then reconcile the numbers. The right content for the earliest wave and for calibrating hours per dashboard |
| Moderate | A few LOD expressions or table calculations, two or three sources that become relationships, parameters, filter and highlight actions | Convert, then review every flagged calculation against the original before the report page reaches its owner |
| Complex | Nested LOD logic over blended sources, custom SQL, sets and set actions, dense dual-axis views, bespoke layouts, row-level filters | Plan design work before converting. Parts of these are rebuilds, and they belong in a later wave with named specialists |

Two habits keep the bands stable. Score the highest dimension instead of the average, because one set action wired through six sheets outweighs forty plain calculated fields. And score the workbook together with the source underneath it, since a tidy page sitting on a database the target tenant cannot reach is not a simple migration.

## How to use the scores

Sequencing is where a rubric pays off soonest. Moving simple dashboards early gives the team a working semantic model, a report theme, a validation routine and a measured hours-per-dashboard figure that everything harder then borrows. Opening with the most visible and most complex content buys the slowest possible first delivery and no baseline to defend the schedule with.

Pruning benefits nearly as much. Cross the scores against 90-day view counts from Tableau's [administrative views](https://help.tableau.com/current/server/en-us/adminview.htm) and one quadrant answers itself: a complex dashboard nobody has opened in a quarter is work you can subtract outright, provided its owner signs the retirement. The [migration checklist](/tableau-migration-checklist/) carries that as a task with an exit criterion attached.

Estimates take their shape from the bands too. Multiply band by band rather than applying one blended average to the whole estate, then recalibrate once a representative dashboard has actually been converted. Microsoft's [proof of concept](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-proof-of-concept) stage exists for that measurement, and it is what turns assumed hours into observed ones. The same bands feed [the budget lines](/tableau-migration-cost-estimation/), since conversion labor is the only line that moves with complexity.

## Where complexity scoring goes wrong

Counting objects is the usual failure. Visual count, sheet count and calculated-field count are easy to extract and correlate weakly with effort, because they treat a dual-axis chart and a set action as comparable line items. What correlates is whether a feature has a direct Power BI counterpart, and how many of the features that lack one are wired into the dashboard's interactions.

Scoring only the top layer is the other. A workbook rated simple on its calculations can still hold a live connection nobody in the target tenant can open, or an extract that was quietly performing the data preparation. That work does not evaporate, it moves to the data engineer, and it belongs inside the score. Which dashboards carry which of those problems is a separate exercise, kept as a [risk register](/tableau-migration-risk-assessment/) rather than folded into the band.

## What Antares does with complexity scoring

This rubric is the job the Antares Analyzer performs. It costs nothing to run, behaves deterministically and reads workbook metadata only, so it crosses an estate without touching data and returns the inventory, a per-workbook feature breakdown and a complexity score for every dashboard instead of a spreadsheet somebody has to populate by hand. Genuinely ambiguous mappings are flagged rather than guessed, which stops a score from hiding the work it was meant to expose.

Antares is a BI migration tool, and its Converter builds on the same analysis: each source Tableau dashboard becomes a Power BI report page for $200 flat, with no per-user licensing and no time limit. Your own provider carries the LLM usage, typically under $20 a dashboard, and private endpoints can be used. Because the method stays deterministic-first with guardrailed, validated AI steps producing like-to-like pages, the complex band still carries review time. [Run the free Analyzer](https://try.getantares.io) to score your own estate before you commit to a sequence.

Related reading: [the Tableau to Power BI migration guide](/tableau-to-power-bi-migration/), [the migration risk register](/tableau-migration-risk-assessment/), [enterprise migration strategy](/enterprise-tableau-migration-strategy/) and [the Analyzer](/analyzer/). Primary sources: Tableau on [set actions](https://help.tableau.com/current/pro/desktop/en-us/actions_sets.htm) and [blending data sources](https://help.tableau.com/current/pro/desktop/en-us/multiple_connections.htm), plus Microsoft on [star schema design](https://learn.microsoft.com/en-us/power-bi/guidance/star-schema), [data reduction for import models](https://learn.microsoft.com/en-us/power-bi/guidance/import-modeling-data-reduction) and [gathering requirements](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-requirements).

## Related resources

- [Migration Risk Register](/tableau-migration-risk-assessment/)
- [Enterprise Migration Strategy](/enterprise-tableau-migration-strategy/)
- [How Long a Migration Takes](/how-long-does-tableau-to-power-bi-migration-take/)
- [Tableau to Power BI Migration Guide](/tableau-to-power-bi-migration/)

## FAQ

### How do you measure Tableau dashboard complexity for a migration?

Score five dimensions separately: calculation logic, data sources, interactivity, visualization types, and size and layout. Take the highest dimension rather than the average, because one set action wired through several sheets costs more than dozens of plain calculated fields sitting next to each other.

### What makes a Tableau dashboard hard to convert to Power BI?

Nested LOD expressions over blended sources, table calculations with unusual addressing, custom SQL, and sets with set actions. Those features either change meaning when restated in DAX or have no Power BI object at all, so they need review or a rebuild rather than a translation.

### Does the number of visuals predict migration effort?

Weakly. Visual, sheet and calculated-field counts are easy to extract and treat a dual-axis chart and a set action as equivalent line items. What predicts effort is whether each feature has a direct Power BI counterpart, and whether the source underneath the workbook is reachable and modeled.

### What do complexity scores change in a migration plan?

Three things: wave order, with simple content first to establish the model, theme and validation routine; hours budgeted per band instead of one blended average across the estate; and retirement decisions, since a complex dashboard with no recent viewers is better retired than converted.