Reporting and KPIs

How to Migrate From Tableau to Power BI

How to migrate from Tableau to Power BI without breaking your dashboards. A plain, step-by-step plan for a Head of Data, plus what to rebuild.

Austin Levine

·

Updated

How to migrate from Tableau to Power BI comes down to four steps: take stock of what you still use, rebuild the data model properly in Power BI, recreate the reports that matter, then run both tools side by side until the numbers match. The mistake most teams make is trying to convert dashboards one for one. Power BI works differently under the hood, so a clean rebuild of the model is faster and safer than a copy.

You picked Tableau years ago, and now the rest of the company runs on Microsoft, so someone has asked how to migrate from Tableau to Power BI without losing every dashboard your team built. That's a fair question and a stressful one. You have dozens of workbooks, a few people who know where the numbers come from, and a licence renewal coming up. Nobody wants to spend six months on a move that leaves the business with two reporting tools and no clear answer to which one is right.

Thousands of teams have done this move, so it's well understood. Most guides still make it sound simpler than it really is. Tableau and Power BI look similar on the surface and think about data very differently underneath. If you treat the move as a straight copy, you get reports that render but return the wrong totals. This guide walks through how to do it properly, in plain terms, without the sales gloss.

Key takeaways

  • Migrating comes down to four steps: take stock, rebuild the model, recreate reports, then run both side by side.

  • Do not convert dashboards one for one, since Power BI works differently under the hood.

  • Without a priority list, teams stall halfway and pay for both licences.

  • Auto-convert tools help with a first draft but cannot rebuild a proper data model.

What does it really take to migrate from Tableau to Power BI?

Three things move when you switch tools, and they aren't equally hard.

The first is the data connections. Tableau connects to your databases, extracts, and files. Power BI does the same, and this part is usually straightforward. You point Power BI at the same sources.

The second is the data model, which is the set of tables, relationships, and calculations behind your charts. This is the real work. Tableau uses its own calculation language and its own way of joining data. Power BI uses a language called DAX and a star-schema model, and the two don't translate line for line. A Tableau calculated field often has to be rethought as a DAX measure, not simply pasted across.

The third is the reports and dashboards themselves, the visuals people open every day. These are the easiest to recreate once the model is right, and the most tempting to start with, which is exactly the trap.

Most teams start with the visuals because that's what everyone can see. Then they discover the numbers don't tie out, because the model underneath was never rebuilt. Start with the model. The visuals come quickly after.

How do you plan a migration without stalling halfway?

The most common way this goes wrong isn't technical. A team starts converting workbooks with no priority list, runs out of time or budget, and ends up with half the reports in Power BI and half still in Tableau. Now both licences are being paid for, nobody trusts either version, and the finance team keeps using the old one anyway. The migration stalls half finished and both tools run at once, which is the worst of every outcome.

You avoid that with a short planning pass before anyone touches Power BI.

  1. Inventory what exists. List every Tableau workbook and dashboard. Note who opens each one and how often. Tableau's own usage stats tell you this.

  2. Cut hard. Most Tableau deployments have a long tail of reports nobody opens. You don't migrate those. You retire them. Moving dead reports is pure waste.

  3. Rank what's left. Order the survivors by how much the business relies on them. The month-end pack and the sales pipeline report come first. The one chart someone made in 2021 comes last, if at all.

  4. Pick a first slice. Choose one important, self-contained report to migrate first. You learn the real effort on something that matters, not on a toy.

This step alone often cuts the work in half, because most teams are carrying far more reports than anyone uses.

How to migrate from Tableau to Power BI step by step

Once the plan is set, the build follows a repeatable order. Do it in this sequence and the numbers stay correct.

  • Connect the data. Point Power BI at the same sources Tableau used. Confirm you can see the same raw tables.

  • Rebuild the model as a star schema. Lay out fact tables and dimension tables cleanly, with clear relationships. This is where trusted numbers come from. Don't skip it to save time.

  • Rewrite the calculations as DAX measures. Take each Tableau calculated field that matters and rebuild it as a measure. Write the definition down as you go, so there's one agreed version of revenue, margin, and every other number.

  • Recreate the reports. Now build the visuals. With a clean model, this is the fast part.

  • Add row-level security. So a regional manager sees only their region, the way your Tableau permissions did.

  • Validate against Tableau. Put the old report and the new report next to each other and check that every total matches. Skipping this step is how wrong numbers reach the business.

That validation step is the one people rush, and it's the one that decides whether the business trusts the new tool. If a total is off by even a little, find out why before you switch anyone over.

Should you convert dashboards or rebuild them?

There are tools that promise to convert Tableau workbooks into Power BI automatically. They can help with a first draft and save some clicking, but they won't save you from the real work, because they can't rebuild a proper data model or decide what your one agreed definition of margin should be. A converted dashboard usually needs almost as much cleanup as a fresh build, and it hides problems inside logic you didn't write.

For anything important, rebuild it. The rebuild forces you to decide what each number means, which is the whole point of the exercise. Reserve auto-conversion for low-stakes reports where a rough copy is good enough.

Part of the reason teams take this on at all is cost. Power BI Pro lists at $14 per user each month, against Tableau Creator at $75, according to vendor list prices in 2025. Across a large deployment that gap is real money, and it's often what gets a migration approved. Just don't let the saving tempt you into a rushed copy, because a Power BI report nobody trusts costs far more than the licence you saved.

What changes for your team in Tableau vs Power BI?

Here's how the two tools compare on the points that matter during a move.

Point

Tableau

Power BI

Calculation language

Tableau calculations

DAX measures

Data model shape

Flexible joins, less enforced

Star schema, clearer structure

Licence list price

Creator around $75/user/month

Pro around $14/user/month

Fits Microsoft stack

Separate platform

Native with Excel, Teams, Fabric

Learning curve for the team

Known to your current users

New syntax, familiar Office feel

The table shows why the move is worth doing and where the real effort sits. The cost and the Microsoft fit pull you toward Power BI. The different calculation language is exactly why you can't just copy your work across.

How CaseWhen can help

If you're working out how to migrate from Tableau to Power BI, the hard part is rebuilding the data model so the new reports return the same trusted numbers your team already relies on. The visuals are the quick part. That's the work we do. We inventory what you have, rebuild the semantic model to one agreed number, and validate every total against your existing Tableau reports before anyone switches over.

Start with our free Power BI Governance and Cost Scorecard. It's a five-minute assessment that scores where your reporting stands today and flags the top risks before a migration starts. If you have a Tableau renewal or a deadline in front of you, book a migration scoping call with us and we'll map the real effort on your actual reports.

FAQ

How long does a Tableau to Power BI migration take? It depends far more on how many reports you keep than on the tool. A focused migration of the reports that matter can take a few weeks. A full move of a large, uncleaned Tableau estate can run several months, which is exactly why cutting dead reports first is so important.

Can you automatically convert Tableau dashboards to Power BI? Partly. Some tools generate a first draft, but they can't rebuild a proper data model or decide what each number means. For important reports, a clean rebuild is faster and safer than fixing an automatic conversion.

Will the numbers match after we migrate from Tableau to Power BI? Only if you validate them. Put the old and new versions side by side and check every total before switching users over. Differences almost always trace back to the data model or a calculation that was copied instead of rebuilt.

Do we have to run Tableau and Power BI at the same time? For a short window, yes, and that's healthy. Running both while you validate lets you prove the new numbers before you retire the old tool. The risk is leaving both running for months with no plan to finish, so set an end date.

Read next

  • Tableau vs Power BI: Which One Fits Your Team

  • Power BI Governance: How to Get to One Trusted Number

Is your Power BI set up the right way?

1

Book 45 minutes and tell us what you want looked at.

2

We walk through your reports and setup with you, live.

3

Within two working days, you get our plan in writing.

Is your Power BI set up the right way?

1

Book 45 minutes and tell us what you want looked at.

2

We walk through your reports and setup with you, live.

3

Within two working days, you get our plan in writing.

Is your Power BI set up the right way?

1

Book 45 minutes and tell us what you want looked at.

2

We walk through your reports and setup with you, live.

3

Within two working days, you get our plan in writing.

CaseWhen is a Berlin BI consultancy that builds reporting that leaders can trust, on the Microsoft stack: Power BI, Fabric and Azure.

Berlin, Germany

© CaseWhen Consulting GmbH

English

CaseWhen is a Berlin BI consultancy that builds reporting that leaders can trust, on the Microsoft stack: Power BI, Fabric and Azure.

Berlin, Germany

© CaseWhen Consulting GmbH

English

CaseWhen is a Berlin BI consultancy that builds reporting that leaders can trust, on the Microsoft stack: Power BI, Fabric and Azure.

Berlin, Germany

© CaseWhen Consulting GmbH

English