How to Export a Semantic Model that is not attached to a Report

[sassy0112]

Hi,

I'm need to migrate a semantic model from our development workspace to our production workspace. The issue is this semantic model isn't attached to a report, so I do not have a report that I can download with the model and then publish to production. I can't figure out how I do this without manually copying all the calculations from one to the other. 

The flow looks like this:

LH Gold-->semantic model with calculations-->report semantic model-->report

I need to migrate "semantic model with calculations".

Any help would be greatly appreciated!

[GilbertQ · Accepted solution]

Hi @sassy0112 

Here is another option where you can copy the semantic model from one space to another workspace using a notebook and semantic link labs. Code Examples · microsoft/semantic-link-labs Wiki

[v-karpurapud · Accepted solution]

Hello @sassy0112 

Welcome to the Microsoft Fabric Community Forum.

To migrate a semantic model that is not attached to a report from one workspace to another, you can use one of the following three supported approaches, as suggested by @tharunkumarRTK and @GilbertQ , depending on your setup and requirements.

First, Deployment Pipelines offer the most straightforward method if both your source and target workspaces are backed by Premium or Microsoft Fabric capacity. This allows you to move semantic models, even those not associated with a report, through a structured Dev-Test-Prod workflow without manual intervention.

Second, Tabular Editor provides more control and flexibility. It allows you to connect directly to a semantic model, export it as a .bim file, and then deploy that model into another workspace. This method is particularly useful when you need to manage model definitions in version control or outside of the Power BI/Fabric interface, and it works even without a Premium workspace.

Third, the semantic-link-labs project is an experimental and advanced option from Microsoft, which uses notebooks and APIs to programmatically manipulate and migrate semantic models. While powerful, this method requires a higher level of familiarity with the Tabular Object Model, scripting (Python or PowerShell), and Fabric notebooks. 

Ultimately, the right approach depends on the complexity of your dataset and your organizational setup. For most standard use cases, deployment pipelines or Tabular Editor will provide the best balance of simplicity and control.

If this response resolves your query, please mark it as the Accepted Solution to assist other community members. A Kudos is also appreciated if you found the response helpful.

Thank you for being part of Microsoft Fabric Community Forum.

Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.

[GilbertQ · Accepted solution]

Hi @sassy0112 

Here is another option where you can copy the semantic model from one space to another workspace using a notebook and semantic link labs. Code Examples · microsoft/semantic-link-labs Wiki

[tharunkumarRTK]

@sassy0112 

You can deploy it from one workspace to other workspace using deployment pipelines. Or with some external tools like tabular editor 

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipel...

https://docs.tabulareditor.com/index.html?tabs=TE3

I am assuming your semantic model is in a Premium or fabric capacity backed workspace. 

Connect on LinkedIn

Did I answer your question? Mark my post as a solution!
If I helped you, click on the Thumbs Up to give Kudos. Proud to be a Super User!