Tableau migrations have a specific challenge that the technology cannot solve: the power users. The people who have invested most in Tableau are the ones whose buy-in the migration most depends on. Lose them and the project does not recover.
This playbook covers the three-phase approach Hopton uses for Tableau to Power BI migrations - audit, rebuild, switch-off - how LOD expressions translate, the differences that surprise teams most often, and how to carry power users rather than lose them to the transition.
How you handle the power users is how the migration goes.
What Tableau migrations get wrong
The most common mistake is treating the migration as a feature-for-feature rebuild. Tableau and Power BI have genuinely different data models and calculation languages. The migrations that succeed use the transition to improve on what existed rather than simply replicate it.
Three phases from audit to switch-off
A well-run migration moves through a usage audit that identifies what to migrate and what to retire, a parallel running period that maintains business continuity, and a switch-off that is planned rather than forced.
What the playbook covers
- The three-phase migration approach from audit through parallel running to switch-off
- How Tableau LOD expressions and calculated fields translate to DAX and Power BI
- The specific differences between Tableau and Power BI that surprise teams most often
- How to identify power users early and keep them invested in the outcome
- How to use the migration as an opportunity to improve on the existing report estate
Who this is for
BI leads, data teams, and IT managers responsible for migrating a Tableau estate to Power BI, particularly those managing technically sophisticated Tableau implementations with invested power users.