Skip to main content
The fastest way off Power BI / Fabric / Tableau isn’t a rewrite — it’s giving Ana what the original dashboard is made of and rebuilding it on governed data. You keep the old tool running and prove parity side-by-side.

​
Two ways to bring the dashboard in

Source file (.pbit / .twb)

Export the template/workbook and upload it. Best when you have the file and want the model, measures, and layout in one shot.

Live BI connector

Power BI or Tableau is connected as a data source in your workspace. Ana reads the published datasets, measures, and metadata directly — no export needed. Best when the file is locked down, or you want the rebuild to track a report that keeps changing.
What each path exposes — A Power BI template (.pbit) carries the data model, DAX measures, and report layout — Ana reads all three (this replaced the old zip/xlsx/unpack hack). A Tableau workbook (.twb) is XML: datasource fields, calculated fields, and worksheet/dashboard layout. A connected Power BI / Tableau source exposes the published datasets, measures, and field metadata through the connector. Any of them gives Ana the logic to reconstruct the dashboard.
Add screenshots — this is what nails the look & feel — Whichever path you use, attach 2–3 screenshots of the original dashboard (the full view, plus any key tiles). The file or connector gives Ana the logic; the screenshots give her the look — layout, color, card styling, chart types. Rebuilds come out far closer to the original when Ana can see it, not just read its model. This is the single highest-leverage thing you can hand her.
  • Give Ana the source + screenshots. Path A: upload the .pbit / .twb. Path B: point her at the connected Power BI / Tableau source. Either way, attach 2–3 screenshots of the original and ask her to read the model, measures, and layout before building anything.
  • Map measures → governed metrics. Bind each visual to an ontology metric instead of re-implementing DAX/Tableau calcs ad hoc — that’s what makes the number deterministic and auditable. Any measure with no clean mapping gets flagged, not guessed.
  • Build a static-first snapshot for the visuals actually shown (Module 6 is the how + why).
  • Replicate the layout — tiles, filters, trend — against the snapshot.
  • Reconcile figure-for-figure to the source dashboard before you trust it.
Prompt
Prompt
You’ll see: a measure-by-measure mapping (source measure → ontology metric), a layout proposal that mirrors the original’s look from your screenshots, and a flagged list of anything that needs a definition before it can be rebuilt faithfully.
Prompt
You’ll see: the rebuilt app with its numbers lined up against the source — matching figures where the logic is faithful, and an explicit note on any intentional difference.
Keep the old tool running — Don’t cut over on faith. Run the data app alongside the Power BI / Tableau original until the numbers reconcile and the team trusts it. For estate-wide migration (inventory, semantic-layer translation, cutover, adoption), the Migrate from Your BI Tool workshop is the bigger playbook — this module is the single-dashboard hands-on.
Visual-level DAX with no governed equivalent, report-only calculated columns, custom visuals/plugins, and pixel-exact formatting. Rebuild the logic as governed metrics and the intent of the layout — not every cosmetic detail. Flag anything you can’t map rather than approximating a number.

​
✅ Checkpoint

  • You gave Ana the source (file or connected) and screenshots of the original
  • The app reproduces the source dashboard’s headline numbers to the dollar
  • Every source measure maps to a governed metric (or the unmapped ones are flagged)
  • The app runs alongside the original for parity testing