How to migrate a community-uploaded dataset to another Fabric workspace

[Harzer]

I have a dataset that was uploaded to the community section of a Fabric workspace. Due to organizational changes, I need to move this dataset to a new workspace while maintaining its structure and connections. I have already set up the necessary tables and pipelines in the new workspace, but I'm unsure of the best way to transfer the dataset. Is there a recommended approach for migrating community-uploaded datasets between Fabric workspaces?

[v-sgandrathi]

Hi @Harzer,

Thanks for reaching out to the Microsoft Fabric Community forum.

Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone. Mark it as Accept Answer and give us Kudos if you found it helpful.

Thank you for your understanding!

[v-sgandrathi]

Hi @Harzer,

I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.

If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.

Thank you for being a part of the Microsoft Fabric Community.

[v-sgandrathi]

Hi @Harzer,

I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.

If our response has addressed your query, please Accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.

Thank you.

[nilendraFabric · Accepted solution]

Hello @Harzer 

I am bit confused regarding community section of a Fabric workspace.

could you please explain this further.

To move datasets use deployment pipelines:

- Select dataset + dependent items (reports/dataflows) in source workspace
- Click *Deploy All* to clone metadata to target workspace
- Preserves relationships between items through TMDL definitions 

Note: Data itself isn’t copied - schedule refresh post-deployment

Preserves lineage and relationships between objects

Requires manual data refresh post-deployment