Tableau Server to Power BI Migration: Moving the Platform, Not Just the Content
September 2, 2026
Retiring Tableau Server moves three separate things into Power BI: content, access, and schedules. Only the first one is a conversion problem. Permissions get rebuilt against a different model, and every on-premises source the server used to reach from inside your network now needs an on-premises data gateway before a single refresh runs.
The report layer gets the attention because it is what people see. The platform layer is where dates slip. This page covers that layer: what each server object becomes, what has no counterpart, and which decisions belong before the first workbook is touched. Workbook mechanics are on the migration guide.
What moves from Tableau Server and what does not
Power BI Service is tenant-wide SaaS, so objects you administered on your own hardware become settings inside someone else's. Most of the mapping is workable. The rows that cost time are the ones rebuilt by hand.
| Tableau Server | Power BI equivalent | What to watch |
|---|---|---|
| Site | The tenant, separated by workspaces and capacities | A multi-site server collapses into one tenant; isolation comes from workspaces |
| Project, including nested projects | Workspace | Workspaces do not nest, so the tree is flattened and filing is separated from permissions |
| Permissions and server groups | Workspace roles plus app audiences | Four roles replace granular capability grants; Entra groups replace server groups |
| User filters | RLS roles with DAX filters | Rebuilt, not translated; entitlement logic has to reach the semantic model |
| Extract refresh schedules | Semantic model refresh | On-premises sources need the gateway, and daily refresh counts are capped by license |
| Subscriptions and data alerts | Report subscriptions and alerts | Recreated per report and per owner; nobody inherits somebody else's list |
| Promotion between projects | Deployment pipelines | Real development, test and production stages, with rules that repoint sources per stage |
| Administrative views | Usage metrics | Different measures, no history carried over; capture your usage baseline before decommissioning |
| Certified data sources | Endorsement: Promoted or Certified | Certification rights are granted separately, so decide who holds them before publishing starts |
The shorter list is more often forgotten. None of it converts.
| Does not move | Why |
|---|---|
| Server topology and configuration: nodes, processes, TSM settings, SSL and proxy setup | You no longer run the platform, so the settings have no destination |
| Custom administrative views built on the server repository | There is no repository database to query |
| tabcmd and REST API automation | A different API surface entirely; rewriting is a workstream, not an afternoon |
| Schedules as reusable server objects | Refresh timing is configured per semantic model, not attached to a shared schedule |
| Historical view counts and usage statistics | Export what the prune decision needs while the server is still up |
How on-premises data sources reach Power BI
This is the specific problem of leaving a server, and the one genuinely new component in the target architecture. Tableau Server sat inside your network and connected to databases directly. Power BI Service does not, so anything unreachable from the public cloud goes through a gateway in standard mode: a service installed on a machine inside the network, making outbound connections only, holding data source credentials centrally.
Three decisions follow: where it runs, since the host needs network access to every source and memory for concurrent refreshes; whether it is clustered, because one gateway is a single point of failure for every scheduled refresh in the tenant; and who administers it, since gateway and workspace administration are separate jobs in most organizations. Cloud-hosted sources need none of this.
What happens to schedules and subscriptions
On your own server, refresh frequency was a hardware question. In Power BI it is a licensing one. Microsoft documents a maximum of 8 scheduled refreshes per day for a semantic model on Power BI Pro, and up to 48 per day with Premium Per User or a Premium or Fabric capacity, as of August 2026.
So sort the Tableau schedules by frequency before choosing a license; the hourly extracts decide the answer. Where a full reload will not fit the window, incremental refresh is a design choice to plan for, not a fix to discover late. Subscriptions and alerts are recreated by hand, so give owners a deadline and a list.
How to size the licensing change
Tableau Server charged for named users on infrastructure you also paid to run, patch and upgrade. Power BI charges per user or per capacity, and the hosting line disappears apart from the gateway host. Microsoft's public list prices are $14.00 per user per month for Power BI Pro and $24.00 for Premium Per User, billed yearly, as of August 2026. Capacity is priced separately, and free-licensed users can only open shared content on a Fabric F64 or larger capacity, which is what makes a large read-only population affordable.
The sizing question is therefore not how many Tableau seats you had, but how many people author, how many only read, and whether the reader count justifies capacity over seats. Build it with the other budget lines on migration cost estimation, and re-read the pricing page the day you write the business case.
If your Tableau is Tableau Cloud, not Server
Then most of this page does not apply: no server configuration to abandon, no administrative views to rebuild, no gateway at all when sources are cloud-hosted. Identical are the content conversion, the security rework, the validation effort, and the two-subscription overlap. That version is on Tableau Cloud to Power BI.
What Antares does when the server goes away
Antares is a BI migration tool, and it addresses the content column of the three, not the platform column. The free Analyzer inventories what Tableau Server holds: which workbooks are still opened, which sources repeat, where user filters and blends live, and how complex each dashboard is to convert. It is deterministic, reads metadata only, never business data, runs inside your own environment, and changes nothing in the source.
The Converter turns each source Tableau dashboard into a Power BI report page for a flat $200, with no per-user licensing and no time limit; LLM costs go to your own provider at typically under $20 per dashboard, private endpoints supported. It runs deterministic-first with guardrailed, validated AI steps, and flags mappings it cannot resolve confidently instead of guessing. Conversion is like-to-like rather than pixel-perfect, and it is not a data migration tool: gateways, warehouses and network paths remain your work. Run the free Analyzer to get the content inventory before you plan the platform cutover.
Related reading: enterprise scale, data sources to semantic models and the Analyzer. Primary sources: Microsoft on the on-premises data gateway and scheduled refresh, plus Tableau on projects.
← Back to the Tableau to Power BI Migration guide
Related Migration Resources
Frequently asked questions
Can Tableau Server permissions be migrated to Power BI automatically?
No. Tableau grants capabilities on projects, workbooks and data sources; Power BI grants four workspace roles plus app audiences, with row-level security handled separately in the semantic model. The structures do not correspond, so permissions are redesigned rather than copied. Export the current permission set as a requirements document, then map groups to Microsoft Entra groups before the first workspace exists.
Do we need an on-premises data gateway if our data is already in the cloud?
No. Power BI connects to cloud-hosted sources directly, and a gateway in standard mode is only needed for sources unreachable from the public cloud. In practice most Tableau Server estates keep a few on-premises databases or file shares, so plan a gateway host anyway and decide early whether it is clustered.
How many times a day can a Power BI semantic model refresh?
Microsoft documents up to 8 scheduled refreshes per day on a Power BI Pro license, and up to 48 per day with Premium Per User or a Premium or Fabric capacity, as of August 2026. Sort your Tableau schedules by frequency before choosing a license, and plan incremental refresh for models that will not reload fully inside the window.
What happens to our tabcmd scripts and Tableau REST API automation?
They stop working, because the target platform exposes a different API surface. Treat the automation inventory as its own workstream: list what each script does, decide what is still needed, and rebuild against Power BI APIs. Publishing and promotion scripts often disappear entirely once deployment pipelines take over that job.