# Tableau Workbook to PBIX: What Converting a .twbx Actually Involves

> There is no file-level .twbx to .pbix converter. What each file actually contains, what maps to what, what converts mechanically, and what has to be rebuilt.

- Canonical: https://getantares.io/tableau-workbook-to-pbix-conversion/
- Published: 2026-02-18
- Updated: 2026-07-28

---

There is no file-level converter from `.twbx` to `.pbix`, and there cannot easily be one, because the two formats describe different things. A `.twbx` is a zip holding a `.twb` workbook definition in XML plus any extracts and images that workbook needs. A `.pbix` holds two artifacts of its own: a semantic model and a report definition. Converting a workbook therefore means rebuilding both halves, by hand or with a tool that reads Tableau's XML and generates Power BI artifacts. What follows is what is actually inside each file, what maps to what, and what does not survive the trip.

## What is inside each file

| Layer | Tableau | Power BI |
| --- | --- | --- |
| Container | `.twbx`, a zip with the workbook, local data and images | `.pbix`, a single file, or `.pbip`, a folder of text files |
| Definition | `.twb` XML, no published schema | TMDL for the model, PBIR JSON for the report, both with public schemas |
| Data | `.hyper` extract inside the package | Compressed model cache, or no data at all in DirectQuery |
| Editing outside the tool | Not a supported workflow | Supported for PBIR, not for the legacy `report.json` |

## What maps to what

| Tableau | Power BI | Notes |
| --- | --- | --- |
| Workbook | One report plus its semantic model | The report is the deliverable, the model is the prerequisite |
| Dashboard | Report page | The natural unit of conversion |
| Worksheet | Visual | A worksheet on no dashboard has no target of its own |
| Story | Bookmarks and navigation buttons | No direct equivalent |
| Data source | Model tables and relationships | Blends become real relationships |
| Calculated field | Measure or calculated column | The split is a modelling decision, not a translation |
| Parameter | What-if parameter or field parameter | Two different mechanisms in Power BI |
| Action | Drillthrough, cross-filtering or page navigation | Chosen per action |
| Layout containers | Absolute positions on a fixed canvas | Power BI has no flow container |
| Device layouts | Mobile layout, held per visual | Rebuilt, not carried over |

One line in that table constrains everything else. In Tableau, each worksheet binds to whichever data source it needs, so a single workbook can sit on several unrelated connections. A Power BI report has exactly one semantic model behind it. Several unrelated Tableau data sources therefore have to be merged into one model, which is real modelling work, or split across several reports, which changes what users see. Deciding that before conversion starts is cheaper than discovering it halfway through.

## Why the layout never comes across cleanly

Tableau dashboards are built from nested containers that resize with the window. A Power BI report page is a fixed canvas with every visual placed at an absolute position on it. The [canvas settings](https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-report-display-settings) default to a 16:9 page sized from a short list, 1280 x 720 upward, or to custom pixel dimensions, and the page is then scaled to fit the browser. So a dashboard designed to flow has to be re-pinned to a pixel grid, and the spacing decisions that looked automatic in Tableau become explicit coordinates in Power BI.

The other asymmetry is the chart unit itself. A Tableau worksheet is a query plus a mark specification, and one worksheet can carry several mark types on a dual axis. A Power BI visual is a chart type with fixed field wells. One worksheet is usually one visual, sometimes two, and occasionally a combination that has no equivalent and needs a design decision instead of a conversion.

## What converts mechanically and what gets rebuilt

| Element | What to expect |
| --- | --- |
| Bar, line, area, scatter and map charts | Convert mechanically |
| Row-level calculated fields | Mostly mechanical, into DAX or Power Query |
| LOD expressions and table calculations | Manual DAX, the largest single cost |
| Sets, groups and parameters | Rebuilt on Power BI's own mechanisms |
| Custom SQL data sources | Power Query or DirectQuery |
| Dashboard layout and formatting | Re-laid out on the fixed canvas |
| Worksheets on no dashboard | A scoping decision, not a conversion |

The rows near the bottom are where estimates go wrong. Charts are the visible work and the cheap part; [LOD expressions](/tableau-lod-expressions-to-dax/), [table calculations](/tableau-table-calculations-to-dax/) and [custom SQL](/tableau-custom-sql-to-power-bi/) are the invisible work and the expensive part.

## Inspect the .twbx before scoping the work

Rename the workbook to `.zip` and open it. The `.twb` inside is XML, so you can count dashboards against worksheets before committing to anything, and the two numbers are usually far apart. Only the dashboard count drives conversion work; a long tail of worksheets that appear on no dashboard is a decision about what to keep. The same archive shows whether data travels with the workbook as an [embedded extract](/convert-hyper-files-to-power-bi/) or whether the connection is live. Note that Tableau publishes no schema for the `.twb`, so anything reading it works against an undocumented format.

## PBIX or PBIP as the target

[Power BI projects](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-overview) save the report and the semantic model as folders of plain text rather than one binary file: TMDL for the model, and the [PBIR](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report) format for the report, where every page and visual is its own JSON file with a public schema. That matters for migration specifically, because generated output becomes reviewable in Git instead of arriving as an opaque file.

Two caveats. Projects are still in preview at the time of writing, and conversion between the two formats happens only through Save As in Power BI Desktop, not programmatically. The service also enforces limits on PBIR reports that are worth knowing before folding many dashboards into one: 1,000 pages per report, 1,000 visuals per page, and 300 MB across all report files.

## What Antares does with workbooks

The Converter takes a source dashboard and produces a Power BI report page, then deploys it. The unit is the dashboard an end user opens, so a workbook with several dashboards is several units of work rather than one. The pipeline is deterministic first, with AI steps confined to the places where the mapping is genuinely ambiguous, and anything it cannot resolve is flagged rather than guessed.

Before that, the Analyzer reads the workbooks themselves and separates the two counts above, so the scope is dashboards rather than files, and the manual items are named before anyone commits to a date. [Run the free Analyzer](https://try.getantares.io) on your own workbooks, or [see how conversion works](/converter/).

Related reading: [calculated fields to DAX](/tableau-calculated-fields-to-dax/) and [actions to drillthrough](/tableau-actions-to-power-bi-drillthrough/). Primary sources: Tableau's [file type reference](https://help.tableau.com/current/pro/desktop/en-us/environ_filesandfolders.htm) and [packaged workbook documentation](https://help.tableau.com/current/pro/desktop/en-us/save_savework_packagedworkbooks.htm), plus Microsoft's documentation of the [project semantic model folder](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-dataset).

## Related resources

- [Tableau to Power BI Migration Guide](/tableau-to-power-bi-migration/)
- [Calculated Fields to DAX](/tableau-calculated-fields-to-dax/)
- [Actions to Power BI Drillthrough](/tableau-actions-to-power-bi-drillthrough/)
- [Hyper Files to Power BI](/convert-hyper-files-to-power-bi/)

## FAQ

### Can you convert a .twbx file to .pbix directly?

No. No tool reads one format and writes the other as a file conversion, because a .twbx holds a Tableau workbook definition plus its packaged data, while a .pbix holds a semantic model and a report definition. Conversion means regenerating both, by hand or with a converter that reads Tableau's XML and emits Power BI artifacts.

### What is inside a .twbx file?

A zip archive: the .twb workbook definition in XML, plus the local data, extracts and images the workbook needs. Rename the file to .zip and open it. Tableau publishes no schema for the .twb itself, so any tool that reads it is working against an undocumented format.

### Does one Tableau worksheet become one Power BI visual?

Usually, but not always. Power BI visuals have fixed field wells, so a worksheet with several mark types or a dual axis can become two visuals or need a redesign. Worksheets that sit on no dashboard have no target at all and need a scoping decision before conversion starts.

### Should converted output be PBIX or PBIP?

PBIP when the output is generated or reviewed in Git, since it stores the report and the model as plain text files with published schemas. Power BI projects are still in preview, and conversion between PBIX and PBIP happens only through Save As in Power BI Desktop, not programmatically.