Forum Discussion
Tableau to Power BI Migration
- 1 year ago
This isn't a "migration" in the traditional sense. Power BI and Tableau are fundamentally different platforms, so you're not just converting files — you're rebuilding reports from scratch. It's critical to set expectations with stakeholders and end users: some reports may not look or behave exactly the same due to feature differences.
Best practices:
-
Discovery & Mapping: Start by mapping existing Tableau data models and identifying report usage. Eliminate unused or redundant reports to reduce scope.
-
Centralized Data Models: Create reusable semantic models in Power BI to avoid duplicating logic across reports.
-
Phased Rollout: Migrate in stages. Validate and perform QA on each batch before moving to the next.
-
Access Management: Once reports are validated in Power BI, restrict access to the equivalent Tableau versions to avoid confusion and dual usage.
-
Documentation & Training: Provide clear documentation and user training to ease the transition and ensure adoption.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
-
- 1 year ago
Hello powerbiexpert22
Assessment & Planning
Inventory existing Tableau reports: List all dashboards, data sources, users, and usage frequency.
Classify reports:
Critical vs. Non-critical
Frequently used vs. rarely used
Identify complexity:
Custom calculations, filters, parameters, blended data, etc.
Set Up the Power BI Environment
Workspaces and Access Control
Data Gateway for on-prem data
Power BI Premium (if large-scale or advanced needs)
Governance: naming standards, documentation, role-based access
Data Source Mapping
Map Tableau’s data sources to Power BI equivalents:
Same SQL DBs? Cloud sources?
Extracts vs. Live/DirectQuery
Optimize queries early — Power BI handles data differently than Tableau.
Rebuild Visuals & Reports in Power BI
Start with critical, high-use reports
Recreate:
Data models
Calculated fields (DAX equivalent of Tableau calculations)
Visuals (match layout as needed)
Filters, bookmarks, interactivity
Consider using tools like:
Tabular Editor (for model management)
DAX Studio (for performance tuning)
Testing & Validation
Cross-check report outputs between Tableau and Power BI
Validate metrics, filters, and interactivity
Engage business users for feedback
Deployment & Rollout
Publish to correct Power BI workspaces
Set up refresh schedules
Migrate users, share access
Provide training for end users
Retire Tableau Gradually
Run Tableau and Power BI in parallel for a while
Monitor user adoption
Retire Tableau reports in phases
Thanks,
Pankaj Namekar | LinkedInIf this solution helps, please accept it and give a kudos (Like), it would be greatly appreciated.
In Power BI, a strict 1:1 mapping from Tableau (workbook or TDS) is generally not recommended.
Instead, we follow a rationalization and consolidation approach—analyzing multiple TDS sources, removing overlaps, and grouping them into domain-driven semantic models. Power BI is fundamentally model-centric, not report-centric.
This approach helps with:
- Performance → optimized models (star schema, fewer cross-source joins)
- Scalability → reusable semantic models across reports
- Governance → standardized KPIs and reduced duplication
Migration is not just lift-and-shift—it’s an opportunity to rationalize fragmented data sources and consolidate them into governed data products.
Thank you for the information noorbashak
Regarding the migrator, given there are 1000 workbooks spread across 70 Datasources (embedded, hyper, live), with each workbook can be based on more than one published datasource (tds), how does the accelerator handle this situation?
1. Is it like 1000 workbooks will be 1000 reports and sematic model in Power BI ?
2. Or how is the multiple tds situtaion handled in Power BI when utility is used