migrate contents from one tenant to another

[powerbiexpert22]

how to migrate below contents from one tenant to another tenant. i am assumming that i no need to recreate mobile compatible reports post migration, are there any features which i need to recreate post migration?

workspaces

semantic models

reports

dashboards

apps

data flows

alerts and subscription

[v-nmadadi-msft]

Hi @powerbiexpert22 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @powerbiexpert22 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[Poojara_D12 · Accepted solution]

Hi @powerbiexpert22 

When migrating Power BI content from one tenant to another, the migration process usually involves exporting and re-publishing reports, semantic models (datasets), dataflows, apps, dashboards, and workspace structures using either manual export/import or supported deployment tools like Power BI APIs, Power Platform pipelines, or third-party migration tools (e.g., Martian, PowerBI Sentinel). While core items like reports, semantic models, and dataflows can be moved, some tenant-specific features do not automatically transfer. Mobile-optimized report layouts generally remain intact within the PBIX and do not need to be recreated, so your assumption is correct. However, certain tenant-bound configurations—including dashboard tiles, personal bookmarks, subscriptions, alerts, RLS assignments (though definitions move, role-to-user mapping must be re-configured), gateway connections, security groups, app audiences, and user permissions—will need to be manually re-set in the target tenant. Additionally, semantic model refresh credentials, data gateway mappings, scheduled refreshes, and API connections must be reconfigured. Items tied to tenant identity, such as email notifications, subscriptions, and Power BI-embedded scenarios, also require re-creation. Planning a structured migration approach, validating data sources, and performing pre-migration inventory checks are essential to ensure that functionality like row-level security, refresh pipelines, and app user access behaves correctly in the new environment.