Forum Discussion
Migrating All Workspaces, Datasets, and Apps Between Power BI Tenants
Hi. Yes we had. We have used SimplePBI python unofficial library for the PowerBi Rest API to make it easier. There are things to consider before doing it. You can only migrate datasets and its original report. Dashboards and apps can't be migrated. I'm not sure about dataflow because we didn't have those, but it might be possible to export the json and load it again.
It's very important to get a deep dive knowledge about the content to migrate, how much content, sizes, users shared, features (incremental refresh datasets can't be downloaded), etc. There are content that breaks rules and others that make it more difficult. For example: a critical details is that exporting and importing might be a total pain if the data model size is higher than 1gb. We did it manually for those because they weren't that much and it was way more coding and complexity for migrating that.
Consider that after migrating everything, you need to schedule refresh all over again. That means editing credentials or configuring gateway sources manually. Entering credentials it must be done manually. You can schedule refresh at the same manual process or later with API probably.
I hope that helps,
Hi ibarrau ,
Thank you for sharing your valuable insights on migrating reports and datasets using the SimplePBI Python library and the Power BI REST API. Your detailed explanation is really helpful.I noticed that the migration of workspace-level reports was not specifically mentioned in your response. Given that my migration scenario involves multiple workspaces with numerous reports in each, I'm particularly interested in understanding how to handle this aspect.
Have you had any experience with, or could you offer any advice on, migrating entire workspaces (including all contained reports, datasets, and other configurations) from one Power BI tenant to another? Any insights or suggestions on this would be greatly appreciated, especially regarding the automation of such processes.
Sorry I forgot to mention about workspaces. The thing about "migration" is that it's not actually a migration as the definition. It's more creating the most closed structure in another tenant. Thinking that way means that you will be creating scripts to make sure your new structure is similar to the old one.
The script will probably start getting the workspaces and its datasets/reports with a token. You can loop them. Then running a new token auth for the new structure and creating the workspace. You can go workspace by workspace read old, create new. Then content, export old and import new (considering the limitations like I said before).
The creation of the workspace can be as deep as you want. The process could include things like asign a capacity or check the users in the old to add users in the new one with the same permission for the workspace.
Another thing to consider is apps. Sadly, if you are distributing the content with just apps, you can't migrate that configuration.
I hope that helps
Hi, is it possible to share the script please
