Power BI tenant to tenant migration after a merger or split
Power BI tenant to tenant migration moves reports, semantic models and workspaces from one Microsoft tenant to another, usually after a merger, a sale or a rebrand. Microsoft offers no single button for this, so every item needs an export, a republish and a fresh set of connections. One of our consultants plans the order, rebuilds what cannot travel and checks each report in its new home.
- Full content inventory
- Access rebuilt by group
- Links and refresh retested
Last updated
What does a Power BI tenant to tenant migration involve?
A tenant is the boundary around a company's Microsoft accounts and content. Everything in Power BI belongs to one tenant: workspaces, models, reports, apps and the people allowed to open them. When a company changes shape, that boundary has to change too.
The platform has no built-in transfer between tenants. So each report file comes down from the old side and goes up on the new one. Then someone reconnects it to its data, because stored credentials never travel.
Some items need more care. Dashboards, apps and subscriptions have no file to download, so we rebuild them by hand. Also, a few models cannot come down as files at all, for example those changed through external tools. In that case we recover them by another route. For example, a Power BI project portfolio dashboard with years of history needs that care before the move.
Power BI items that need attention when tenants change
Most surprises in a tenant move come from one of these six areas.
User identities
People get new accounts in the target tenant. Every role, security rule and share therefore needs mapping to the new names.
Row-level security members
The roles travel inside the model, but their members do not. We assign groups again and test each role.
Gateways and credentials
A gateway registers to one tenant. So we install a new one and enter source credentials with your IT team.
Links and bookmarks
Every report gets a new address. Saved links, embedded pages and shared favorites then need an update or a redirect note.
Dataflows and pipelines
These export in their own formats. We move the definitions and then confirm that each refresh still lands correctly.
Capacity and licenses
The target tenant needs the right capacity and licenses before content arrives. We check this early to avoid a stall.
Why do tenant moves go wrong without a plan?
The first trap is an incomplete list. Administrators know the official workspaces, but personal workspaces often hold reports that managers use every day. If nobody checks, those reports vanish on cutover day.
The second trap is timing. Identity, email and file storage usually move in the same program, and reporting sits at the end of the queue. As a result, accounts change before reports are ready, and access breaks for a while.
A clear sequence avoids both. We take an inventory through the admin tools first, agree the order with the wider project team, and keep the old tenant readable until the new one has passed its tests.
When a Power BI tenant to tenant migration comes up
These business events most often trigger a move between tenants.
- Two companies merge into one tenant
- A business unit is sold or spun off
- A rebrand brings a new domain
- Several regional tenants consolidate
- A parent company absorbs a subsidiary
- A test tenant becomes the live one
How our Power BI tenant to tenant migration runs
Four stages keep both tenants usable until the final switch.
Inventory both sides
First we list workspaces, models, reports, apps and owners in the source, and we check what the target already holds.
Prepare the target
Then we set up workspaces, security groups, capacity and a gateway, so that content has somewhere safe to land.
Move and reconnect
Content moves in waves. After each wave we reconnect sources, run a refresh and compare totals with the source tenant.
Cut over and support
Finally, users receive new links and a short guide. We stay close during the first days, since questions cluster there.
Questions about moving Power BI reports between tenants
Is there a Microsoft tool to move Power BI between tenants?
Not a complete one. Microsoft provides admin interfaces that help list and export content, and we use them for the inventory. However, no feature moves a whole tenant's reporting in one step. So the work combines scripts for the repeatable parts with careful manual effort for dashboards, apps, subscriptions and access.
Will Power BI report links keep working after a tenant move?
No. Each report receives a new address in the target tenant, so old links stop working. We therefore prepare a mapping of old to new addresses. Then your team can update intranet pages, embedded reports and saved bookmarks. We also suggest a short notice to users before the switch, which prevents most support calls.
Can both tenants run side by side during the move?
Yes, and they should. We keep the source tenant readable while content moves, so nobody loses a report halfway. Each group switches once its reports pass the comparison. After that the source content becomes read-only for a while and then retires on a date you choose.
What happens to historical data held only in a model?
That case needs care. Some models keep history that the source system no longer holds, for example through incremental refresh. A republish would lose it. So we find those models early and plan a way to preserve the history, such as a staging database, before anything else moves.
Who does the work?
Our consultants do the work remotely, alongside the administrators of both tenants. Power BI Agency is a division of Sataware Technologies and is independent of Microsoft. A free 30-minute assessment comes first. After that a written quote fixes the scope, and weekly demos show which workspaces have moved and passed their tests.
Related pages
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.