how to move a semantic model to another Fabric workspace

[Jeanxyz]

I have created a Fabric workspace with pipeline and semantic data models. Due to permission issues, I have to move the items to a new workspace (the deployment pipeline failed to copy some items).  I have recreated all the pipeline in the new workspace with the same tables and data warehouse, how can I copy the semantic model to the new workspace? I'm think about semantic link, but not sure how to enable it. 

[v-ssriganesh · Accepted solution]

Hi @Jeanxyz,

Thanks for the update! That makes sense if Git integration could introduce the same ownership issues, then it's best to avoid it.

Since you’re not using Git, the PBIX method remains the best way to move your custom Semantic Model to the new Fabric workspace. Just to recap:

• Download the PBIX file from Power BI Service, update the data source in Power BI Desktop to match the new workspace, and then publish it to the target Fabric workspace.

Another option is to use Deployment Pipelines (if available) to move assets between workspaces.

Note: Deployment Pipelines can only move Semantic Models that originate from a .PBIX file and are not PUSH datasets. If your Semantic Model meets these criteria, you can try using Deployment Pipelines for a structured migration.

For your reference: Overview of Fabric Deployment Pipelines.

I trust this information proves useful. If it does, kindly Accept it as a solution and give it a 'Kudos' to help others locate it easily.
Thank you.

[v-ssriganesh]

Hi @Jeanxyz,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-ssriganesh]

Hi @Jeanxyz,
Thank you for reaching out to the Microsoft fabric community forum.

Currently, there is no direct way to move a Semantic Model between Fabric workspaces. The best approach is to move a semantic Model to another Fabric workspace, download the .pbix file from Power BI Service and open it in Power BI Desktop. Update the data source settings to match the new workspace and then publish it to the target Fabric workspace.

For your reference: Solved: Moving semantic model and Reports to a new workspa... - Microsoft Fabric Community

If this information is helpful, please Accept it as a solution and give a "kudos" to assist other community members in resolving similar issues more efficiently.

Thank you.

[AndyDDC]

Hi @Jeanxyz is the semantic model a "custom" semantic model you creating in the workspace from the warehouse?

[Jeanxyz]

@AndyDDC, yes, it's a 'custom' semantic model.

[AndyDDC]

In this scenario, I would connect your original workspace to Git.  Then create a new workspace, connect that to the same repo as the original workspace and "update".  This will restore the items from Git into the new workspace including the custom semantic model.

This doc shows how to connect a workspace to git Get started with Git integration - Microsoft Fabric | Microsoft Learn

[Jeanxyz]

Thanks for the answer. I will keep this in mind. But I don't want to connect the original workspace to git because there are owner issues with the first workspace. If I use git, I will introduce the same problem to the new workspace. 

[v-ssriganesh · Accepted solution]

Hi @Jeanxyz,

Thanks for the update! That makes sense if Git integration could introduce the same ownership issues, then it's best to avoid it.

Since you’re not using Git, the PBIX method remains the best way to move your custom Semantic Model to the new Fabric workspace. Just to recap:

• Download the PBIX file from Power BI Service, update the data source in Power BI Desktop to match the new workspace, and then publish it to the target Fabric workspace.

Another option is to use Deployment Pipelines (if available) to move assets between workspaces.

Note: Deployment Pipelines can only move Semantic Models that originate from a .PBIX file and are not PUSH datasets. If your Semantic Model meets these criteria, you can try using Deployment Pipelines for a structured migration.

For your reference: Overview of Fabric Deployment Pipelines.

I trust this information proves useful. If it does, kindly Accept it as a solution and give it a 'Kudos' to help others locate it easily.
Thank you.

[Jeanxyz · Accepted solution]

Thanks for reply, in my case the pbix file is pointing at the semantic model in the original workspace, so uploaidng pbix file doesn't change the semantic model. I have recreated the semantic model in new workspace and point the pbix file to the new model. That solves the problem. 

[Jeanxyz]

As a hind sight, I'm wondering if we could link the first workspace to Azure Git and then open the Power BI semantic link folder in Visual Studio Desktop, then change the source of semantic model to data warehouses in the new workspace and sync the updated semantic model folder to the new workspace. That requires some knowledge about json coding and Visual Studio Desktop, but will save some time vs rebuild a large sementic model in the new workspace.