Platform migration guide
Planning a Tableau to Power BI migration
A Tableau workbook contains more than charts. Its data sources, calculations, parameters, filters, and dashboard interactions contribute to how users interpret a result. A Power BI migration should begin with that behavior and a target semantic model, then work toward a reviewed report. CoDash’s documented path supports a single workbook, including a variant with a Tableau Server connection.
Inspect the workbook and its dependencies
List data sources, worksheets, dashboards, calculated fields, parameters, and actions. Identify shared calculations and the reporting questions each dashboard answers. Check whether required source data and extracts will remain available in the target environment.
Select reference views that exercise the workbook’s important logic. Save the filter state and expected results along with the data snapshot. This becomes the basis for comparing the target report after conversion.
Review calculation meaning before translation
Tableau and Power BI express calculation context differently. Level-of-detail expressions and table calculations deserve particular attention because the intended grouping and the displayed result can depend on the view. Document the expected behavior using examples instead of assuming a calculation has a direct text replacement.
Review parameter-driven branches, date logic, aggregations, null handling, and filter behavior with the report owner. A translated expression that parses successfully can still produce a result that differs from the business expectation. Keep unresolved cases visible in the migration backlog.
Review the target semantic model and report
CoDash’s Tableau to Power BI path produces a parsed workbook inventory, converted semantic model and report structures, and translated calculations with validation. Review tables, relationships, measure placement, and data types in the target workspace before investing in the report’s presentation.
Continue development in the Power BI workspace to refine DAX, Power Query, report pages, and visuals. Treat interaction differences as design decisions to review with users. The goal is an accepted target experience with clear business meaning, rather than an assumption that every source interaction transfers unchanged.
Validate, package, and plan publishing
Compare detail values and totals with the baseline. Exercise important filters and parameter choices, then record exceptions and owner acceptance. Review data access, refresh requirements, and publishing permissions in the intended environment.
The documented path includes PBIP/PBIT output and a publish-ready workspace. Package review and successful publishing are useful milestones, but neither replaces business acceptance. Start with the representative workbook, use the findings to estimate the next wave, and preserve source access according to the agreed cutover plan.
- Workbook inventory and target data access are complete.
- Calculation behavior is checked against reference results.
- Target model and report interactions are reviewed.
- Exceptions, publishing responsibilities, and acceptance are recorded.