# How to Migrate Tableau Dashboards to Power BI: A Six-Step Process

> The six-step process for migrating Tableau dashboards to Power BI: inventory, score, sequence, convert, validate, cut over. What automates and what does not.

- Canonical: https://getantares.io/migrate-tableau-dashboards-to-power-bi/
- Published: 2026-02-18
- Updated: 2026-08-06

---

Migrating Tableau dashboards to Power BI runs in six steps: inventory and prune the estate, score what remains for complexity, sequence the work, convert, validate numbers and interactions, then cut over with user enablement. Automation compresses step four and part of step five. The other four steps stay with your team no matter which tool you buy, and skipping the first one is the most common way to overspend.

Microsoft frames its own guidance the same way, with [pre-migration steps followed by five stages](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-overview): gather requirements and prioritize, plan for deployment, conduct a proof of concept, create and validate content, then deploy, support and monitor. What follows maps that shape onto a dashboard estate specifically.

## Step 1: Inventory the estate and prune it

Start by counting what you actually have and, more importantly, what anyone actually opens. Tableau Server and Tableau Cloud both ship [administrative views](https://help.tableau.com/current/server/en-us/adminview.htm) covering traffic to views and workbooks, stale content and actions by user; Tableau Cloud exposes [the equivalent set](https://help.tableau.com/current/online/en-us/adminview.htm) for a site. Cross those with the [Metadata API](https://help.tableau.com/current/api/metadata_api/en-us/index.html), which indexes workbooks, data sources and lineage, and you have both usage and structure.

The typical outcome is uncomfortable and useful: a meaningful share of published dashboards are duplicates, abandoned drafts or one-off analyses that nobody has opened in a year. Every one of those you decline to migrate is effort and license cost you never spend. Typical mistake: treating the workbook count as the project size. The unit that matters is the dashboard, because that is what a user opens and what a converter produces.

## Step 2: Score what remains for complexity

Two dashboards with the same number of charts can differ by an order of magnitude in effort. What separates them is feature mix: [LOD expressions](/tableau-lod-expressions-to-dax/), [table calculations](/tableau-table-calculations-to-dax/), [sets and set actions](/tableau-sets-to-dax-measures/), [custom SQL](/tableau-custom-sql-to-power-bi/), blends and extensions. Score each dashboard on those, not on chart count, and you get an estimate that survives contact with the work.

Typical mistake: estimating from a sample of the dashboards the team likes. The expensive ones are usually the old finance and operations dashboards nobody volunteers to demo.

## Step 3: Sequence the work

Order the queue so the team learns before it commits. Simple, low-risk dashboards first, to shake out the target workspace structure, naming and refresh setup. High-visibility dashboards second, once the pattern is proven, because those are what buy sponsor confidence. The complex remainder last, when everybody knows which parts of Power BI they are working with.

Set up the target before conversion starts, not after: [workspaces](https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-create-the-new-workspaces) for the content, and [deployment pipelines](https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/intro-to-deployment-pipelines) if you want development, test and production stages rather than publishing straight into production.

## Step 4: Convert

One Tableau dashboard becomes one Power BI report page. Keep the vocabulary straight, because in Microsoft's terms a [Power BI dashboard](https://learn.microsoft.com/en-us/power-bi/create-reports/service-dashboards) is a single page of pinned tiles that cannot be filtered, while a [report](https://learn.microsoft.com/en-us/power-bi/explore-reports/end-user-reports) holds one or more pages and carries the filtering and drilling. Very tall Tableau dashboards sometimes read better split across two report pages, since the Power BI canvas has fixed [display settings](https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-report-display-settings) rather than a long scroll.

Typical mistake: converting and redesigning in the same pass. Like-for-like conversion is verifiable against the original; a redesign is not, and mixing them makes every discrepancy a debate. If a dashboard genuinely needs rethinking, schedule that as separate work after cutover.

## Step 5: Validate numbers, then behavior

Validation is two passes. The numeric pass reconciles headline measures on each report page against the Tableau original, once unfiltered and once with slicers applied, because context-dependent calculations agree at the total and diverge under filtering. The behavioral pass exercises interactions: a click that filtered three charts in Tableau should still filter three, and tooltips should still carry their detail.

Typical mistake: validating with the migration team only. The person who wrote the original dashboard finds problems in minutes that a reviewer will not find in a day.

## Step 6: Cut over and enable users

Run both platforms in parallel for a defined window, publish the new location, and set a date after which the Tableau version is read-only. Plan enablement alongside the cutover: Microsoft's own migration guidance puts training, support and a communication plan among the practices that separate successful migrations, and the [Fabric adoption roadmap](https://learn.microsoft.com/en-us/power-bi/guidance/fabric-adoption-roadmap) covers the governance side. Then [monitor usage](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-implementation-planning-auditing-monitoring-overview) in the new tenant, which also tells you which migrated content was worth migrating.

| Step | Manual path | With a migration tool |
| --- | --- | --- |
| Inventory and prune | Admin views exported and reconciled by hand | Automated inventory with usage and complexity together |
| Score complexity | Workbooks opened and read one by one | Feature usage counted across the estate |
| Sequence | Team judgment | Team judgment, informed by the score |
| Convert | Rebuild each report page in Desktop | Generated report page plus flagged items to review |
| Validate | Manual reconciliation | Manual reconciliation, narrowed to flagged areas first |
| Cut over and enable | Team owns it | Team owns it |

## What Antares does

Antares is a BI migration tool covering steps one, two and four, and narrowing step five. The Analyzer connects to the source environment, reads metadata only, and returns the inventory and complexity scoring that steps one and two need; it is deterministic and free, so pruning happens before any spend. The Converter produces the Power BI report page and deploys it, at a flat $200 per source dashboard, with no per-user licensing and no time limits. LLM usage is billed by your own provider, typically under $20 per dashboard, with private endpoints supported.

Conversion is like-for-like by design, not a redesign, which is what keeps step five verifiable. Where a mapping is ambiguous it is flagged rather than guessed, so review starts with the items that need judgment. [Run the free Analyzer](https://try.getantares.io) to produce the step one inventory for your own site.

Related reading: the [Tableau to Power BI migration guide](/tableau-to-power-bi-migration/), [what converts and what breaks](/tableau-to-power-bi-automated-migration/), and [consultant versus tool](/tableau-migration-consultant-vs-tool/). Primary source: Microsoft's [deployment planning stage](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-planning).

## Related resources

- [Tableau to Power BI Migration Guide](/tableau-to-power-bi-migration/)
- [Automated Migration: What Converts](/tableau-to-power-bi-automated-migration/)
- [What a Conversion Tool Converts](/tableau-to-power-bi-conversion-tool/)
- [Consultant vs Migration Tool](/tableau-migration-consultant-vs-tool/)

## FAQ

### What are the steps to migrate Tableau dashboards to Power BI?

Inventory and prune the estate, score the remaining dashboards for complexity, sequence the queue simple first, convert, validate numbers and then interactions, and cut over with user enablement. Microsoft's own guidance follows the same shape: pre-migration steps, then five stages ending in deploy, support and monitor.

### Does one Tableau dashboard become one Power BI dashboard?

No, it becomes a Power BI report page. In Microsoft's vocabulary a Power BI dashboard is a single page of tiles pinned from reports and cannot be filtered. A very tall Tableau dashboard sometimes reads better split across two report pages, because the Power BI canvas is a fixed size rather than a long scroll.

### Which dashboards should be migrated first?

Simple, low-risk ones, to settle workspace structure, naming and refresh before anything visible is at stake. High-visibility dashboards second, once the pattern is proven. Complex dashboards last. Anything nobody has opened in a year is a candidate for retirement rather than migration.

### Should dashboards be redesigned during migration?

Not in the same pass. Like-for-like conversion can be verified against the original, a redesign cannot, and mixing them turns every discrepancy into a debate about intent. Schedule redesign as separate work after cutover, when users are already on the new platform.