Tableau Online to Power BI Migration: What Cloud-to-Cloud Really Saves
September 2, 2026
Tableau Online is now Tableau Cloud, as Tableau's release notes state. Moving from it to Power BI drops the infrastructure work entirely: no servers, no upgrades, no gateway for cloud-hosted sources. It changes nothing about three things: rebuilding every connection and its authorization, living inside refresh limits on both platforms, and paying two subscriptions until the last report is accepted.
Worth saying plainly, because cloud-to-cloud gets sold as the easy case and then surprises people at the same points. The content conversion is identical either way and lives on the migration guide. What follows is only what differs from leaving Tableau Server.
What actually gets easier in a cloud-to-cloud migration
| Area | Cloud-to-cloud effect | Why |
|---|---|---|
| Server infrastructure and upgrades | Gone | Neither platform is yours to run, so there is no decommissioning project and no final upgrade |
| Gateway for cloud-hosted sources | Not needed | Power BI reaches a cloud warehouse directly, as Tableau Cloud did |
| Capacity and sizing work | Reduced to a licensing decision | You pick per-user licenses or a capacity instead of sizing hardware |
| Dashboard conversion | Unchanged | Workbook logic is the same logic whatever hosted it |
| Row-level security | Unchanged | User filters become RLS roles and are rebuilt by hand; the detail is on the access-heavy version of this migration |
| Validation and sign-off | Unchanged | Numbers are proved against a source of truth wherever either platform runs |
| Enablement and adoption | Unchanged | Users learn a different tool, not a different hosting model |
How Tableau Cloud content maps to Power BI
Object mapping mostly matches the server case. Connections are where the cloud case has its own character, because a Tableau Cloud site holds authorizations rather than a network route, and authorizations do not transfer.
| Tableau Cloud | Power BI | Notes |
|---|---|---|
| Site | Tenant, separated by workspaces | Several Tableau Cloud sites usually consolidate into workspaces and capacities |
| Project | Workspace | Flat containers, so nested projects are flattened |
| Published data source | Shared semantic model | Several reports connect to one model, as several workbooks connected to one published source |
| Extract on a refresh schedule | Import model with scheduled refresh | No file moves; both platforms cap how often it runs, and the caps are shaped differently |
| OAuth connection to a cloud source | A cloud connection authorized in Power BI | Tokens do not migrate; every Snowflake, Salesforce or BigQuery connection is authorized again, ideally by an account that still exists next year |
| Tableau Bridge | On-premises data gateway | If Bridge is running anywhere, you do need a gateway, with the same design conversation as on the server page |
| Subscriptions | Report subscriptions | Recreated per report and per owner |
| Web authoring | Editing in the service, or Power BI Desktop | Authors who never installed Tableau Desktop will meet a desktop application for the first time |
On the caps: Tableau documents Tableau Cloud extract capacity as up to 8 backgrounder hours per Creator license per site, with an individual refresh limited to 120 minutes, as of August 2026. Power BI counts runs instead of hours: up to 8 scheduled refreshes per day on Pro, up to 48 with Premium Per User or a capacity, also as of August 2026. A team used to trading long refreshes against each other has to re-plan around a count of runs, which usually means incremental refresh for the largest models.
How to get content out of Tableau Cloud
There is no file system to copy from, the practical difference in week one. Workbooks come out through the web interface one at a time, or through the REST API, which is how anyone with more than a few dozen workbooks should do it. Site administrator access and a personal access token are the prerequisites, so raise that request early; it is a small task that has blocked large projects for a week.
One caution while exporting. A downloaded packaged workbook can carry an embedded extract, and Tableau documents the contents of a .twbx file as stored in plain text, readable by anyone who opens it. Where data is regulated, that download is a data movement event and belongs inside the controlled environment; the healthcare version of this migration works through where else that matters.
How long you pay for both platforms
This is the cost only cloud-to-cloud migrations feel sharply, because the Tableau contract keeps running whether or not anyone opens a viz. Through the parallel period you hold Tableau seats you cannot yet drop and Power BI licenses you already provisioned, so the overlap costs about the sum of both per month. Power BI's side is public at $14.00 per user per month for Pro and $24.00 for Premium Per User, billed yearly, as of August 2026. Tableau's side is whatever your contract says.
Which makes the length of the overlap the variable worth managing, and it is set by conversion throughput and owner availability, not by hosting. On the assumptions behind our own calculator, a hundred dashboards at 80 hours each and $85 an hour is $680,000 of manual conversion, against roughly $88,000 with a conversion tool once about 10% review time is added. The number to take from that is not the gap but the calendar behind it: the same team finishes months earlier, and every month saved is a month of two subscriptions nobody pays. Budget lines are on migration cost estimation, the arithmetic on the migration cost calculator.
What Antares does in a cloud-to-cloud move
Antares is a BI migration tool. The free Analyzer connects to your Tableau Cloud site through the same APIs you would otherwise script by hand and returns the inventory: workbooks and their usage, published data sources and where they repeat, the calculations and features that will need attention, and a complexity read per dashboard. It is deterministic, metadata-only, and alters nothing in the source site.
The Converter converts each source Tableau dashboard into a Power BI report page and deploys it, at a flat $200 per dashboard with no per-user licensing and no time limit; LLM costs sit with your own provider, typically under $20 per dashboard, private endpoints supported. It runs deterministic-first with guardrailed, validated AI steps, and flags what it cannot map confidently rather than guessing. Conversion is like-to-like, not a redesign, and connections are reauthorized by you on the Power BI side, because credentials are yours and stay yours. Run the free Analyzer to see the estate before the two-subscription clock starts.
Related reading: Tableau Server to Power BI, Tableau to Microsoft Fabric, the migration risk register and the Converter. Primary sources: Tableau on Tableau Cloud release notes and site capacity, plus Microsoft on scheduled refresh.
← Back to the Tableau to Power BI Migration guide
Related Migration Resources
Frequently asked questions
Is Tableau Online the same thing as Tableau Cloud?
Yes. Tableau Online was renamed Tableau Cloud, and Tableau's release notes state it directly, although the help URLs still carry the old name. Older internal runbooks, contracts and inventories will use both terms for one platform, which is worth checking when migration scope is written against an existing document.
Do we still need a gateway after moving from Tableau Cloud to Power BI?
Only if you were running Tableau Bridge. Bridge exists to reach private-network data from Tableau Cloud, and its Power BI counterpart is the on-premises data gateway. If every source is cloud-hosted and Bridge is installed nowhere, Power BI connects directly and no gateway is required.
Do data source credentials transfer from Tableau Cloud to Power BI?
No. OAuth authorizations belong to the Tableau site and cannot be exported. Every cloud connection is authorized again on the Power BI side, so build that list early and decide which account owns each connection. Service accounts that outlive individual employees save a second round of this work later.
How do we export dashboards out of Tableau Cloud in bulk?
Through the REST API, using site administrator access and a personal access token; the web interface downloads one workbook at a time. Note that a downloaded packaged workbook can contain an embedded extract, and Tableau documents that file's contents as plain text, so bulk downloads of regulated data count as a data movement event.