Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
is it possible to move an existing dataflow to another workspace?
Thanks!
Hey!
There's quite a few methods depending on the context that you wish to use them for. For example, deployment pipelines do in fact move your Dataflow from one workspace to another:
A different approach is to use the Fabric REST API. You can retrieve your Dataflow definition using the endpoint below:
Items - Get Dataflow Definition - REST API (Dataflow) | Microsoft Learn
And using the respones from it create a new one in the workspace of your choice using the endpoint below:
Items - Create Dataflow - REST API (Dataflow) | Microsoft Learn
Hope this helps!
Thanks! I will test this way 😊
Hi @cw88
Thanks for using Fabric Community.
There is no direct way to move a Dataflow gen2 from one workspace to another. But you can create the same Dataflow gen2 in another workspace easily. You can follow these steps:
1) Select the export template option in the Dataflow Gen2 toolbar.
2) Save the JSON file to your local machine or a cloud storage location.
3) Create a new Dataflow Gen2 in another workspace and select the Import from Power Query template. Upload the JSON file downloaded in the previous step.
4) Update the dataflow gen2 settings and connections in the target workspace. You may need to change the data sources, destinations, and other settings of the dataflow gen2 to match the target workspace environment. You can do this by editing the dataflow gen2 in the dataflow editor window, and then selecting Publish to save the changes.
Hope this helps. Please let us know if you have any further questions. Glad to help.
Hi @cw88
The internal team has confirmed that they have plans to enable a "Save As" functionality for dataflows that would allow duplicating an existing dataflow as another dataflow (including saving it to another workspace). After the new dataflow is saved, you could remove the old dataflow if no longer needed. This is not available yet, but is on plan. Currently we do not have any ETA.
Please try the above suggested workaround method and do let us know if you have any further queries. Glad to help.
I've tried the above method and it doesn't work at all. The template import method can't interpret the json file. Is there any update on built in support you mented above?
This is the exact issue I'm running into. Did you ever find an way around it?
Hi @cw88
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let us know if you have any further queries.
Hi @cw88
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let us know if you have any further queries.