How to Export or Connect Tableau to Power BI (There Is No Export Button)

There is no export button and no direct way to export Tableau to Power BI: Tableau Desktop has no Export to Power BI command, and the Power Query connector list that Power BI uses has no Tableau entry, so Power BI cannot open a workbook, a published data source or an extract. What people mean by "export Tableau to Power BI" is one of five different jobs, and each has a route that works. The right route depends on the job.

What "export or connect Tableau to Power BI" usually means

Why there is no export button

Tableau's own export documentation is entirely about data: CSV from the data source page, crosstabs to Excel, view data to Access or CSV. Nothing in it produces a Power BI artifact, because the two formats describe different things (the detail is on workbook to PBIX conversion), and as of September 2026 the only BI vendor with an in‑product importer for another vendor's workbook files is Databricks, whose Genie Code importer reads .twb, .twbx, .tds, .tdsx and .pbit files and lands the result in Databricks AI/BI, not in Power BI.

The connect phrasing fails for the same reason. Power BI connects to databases, files, services and other Power BI semantic models; a Tableau published data source is none of those, and Tableau exposes it to Tableau clients and its own APIs, not over a database protocol.

Route 1: get the data out of Tableau

If the source system behind the workbook still exists, point Power BI at it directly and you inherit a refreshable query. Every route below produces a snapshot that nobody can refresh, so treat it as a bridge for sources that have gone away.

Two caveats apply to every view‑level export. Tableau warns that an export may exclude some table calculations and level of detail expressions, because those are computed in the view, and fields on the Filters shelf are left out unless they also sit on Detail. The CSV carries the data; the dashboard's logic gets rebuilt as DAX, which is covered under LOD expressions and table calculations. Extract mechanics, including the fact that a packaged .tdsx carries a copy of the extract, are on Hyper files to Power BI; how a published data source becomes a shared semantic model is on data sources to semantic models.

Route 2: move the dashboard itself

Because no file conversion exists, moving a dashboard means regenerating a report page and a model from what the workbook describes. A rebuild reads the Tableau dashboard as a specification and authors the Power BI version by hand, which is also the moment most teams redesign. A conversion tool generates the model and report from the workbook definition and leaves review to people. Either way the same items decide the effort: LOD expressions, table calculations, dashboard actions, data blending and custom SQL, none of which map one to one. The migration guide walks the whole list, and automated migration is specific about what converts cleanly and what does not.

Can Tableau connect to a Power BI semantic model?

Yes, with a warning attached. Power BI semantic models on Premium, Premium Per User or Fabric capacity expose an XMLA endpoint, read‑only by default, and Microsoft lists third‑party visualization tools among the clients that can query it. Tableau's Microsoft Analysis Services connector speaks that protocol, so Tableau Desktop on Windows can open a Power BI model as a cube.

Tableau's Fabric connector page documents the steps and then says, in as many words, that the connector is not recommended for production situations and not supported by Tableau, citing schema resolution issues and functionality gaps between Tableau and the semantic model engine. Its recommended Fabric route is the Azure SQL Database connector against a warehouse or lakehouse SQL endpoint, which reaches tables, not the model. Use the XMLA route only while both platforms are live, and plan for it to be gone by cutover.

How to run Tableau and Power BI side by side

Migrations of any size run both platforms in parallel for a period, and "connect" often means making that period bearable. A Power BI report can be placed inside a Tableau dashboard through a Web Page object holding Power BI's secure embed URL; viewers sign in to Power BI inside the frame and, unless both the report and its semantic model sit on Premium or F64‑plus capacity, each needs a Pro or Premium Per User license. A shared warehouse layer keeps both tools reading the same tables, leaving only the calculations to reconcile. And the Tableau Metadata API answers, per workbook, which databases and tables it touches, which is the inventory that decides what moves in which order. One rule keeps the parallel period short: once a dashboard is converted and validated, changes go to the Power BI version only, or the validation has to be repeated.

What Antares does here

Antares is a BI migration tool for Route 2. The Analyzer connects to Tableau Server or Tableau Cloud, reads metadata only, never business data, and returns the inventory: every workbook, what each data source points at, whether it is live or extract‑backed, and which dashboards carry the constructs that do not map one to one. It is free and fully deterministic. The Converter takes a source dashboard and produces a Power BI report page with its semantic model, deployed into a Fabric workspace, at a flat $200€200 per source dashboard, with LLM costs on top, typically under $20€20 per dashboard. It converts dashboards, not databases: live sources are reconnected on the Power BI side, which is Route 1. Run the free Analyzer to see which route each of your dashboards needs.

Related reading: workbook to PBIX conversion, Hyper files to Power BI and data sources to semantic models. Primary sources: Microsoft on data sources in Power BI Desktop and the XMLA endpoint; Tableau on exporting data, saved data sources, the REST API, the VizQL Data Service and the Hyper API.