#PowerPlatformTip 193: 'Export a Power Automate Flow When the Export Option Is Missing'

TL;DR: For a non-solution cloud flow whose Export > Package (.zip) button is missing, replacing /details with /export is an undocumented UI workaround. For a solution-aware flow, export the solution.

A cloud flow that’s part of a solution is exported with its solution; standalone Export > Package (.zip) is for non-solution flows. Remove from this solution moves the flow to the Default Solution; it doesn’t make the flow a non-solution flow. For solution-aware flows, export the solution. The /export URL pattern below is an undocumented UI workaround for a non-solution flow whose Export button is missing.

💡 Challenge

You need a standalone flow package (.zip) to move a single cloud flow to another environment, but:

🔸 While the flow is inside a solution, there’s no Export > Package (.zip) option, that’s by design (solution flows export via the solution).

🔸 For a non-solution flow, the Export button may still be missing from its details page.

✅ Solution

For a non-solution flow whose Export button is missing, the /export URL pattern may open the package export page directly. For a solution-aware flow, export its solution instead; removing it from a solution only moves it to the Default Solution.

🔧 How It’s Done

1. Confirm the flow isn’t solution-aware.

🔸 If the flow is in a solution, export that solution. Remove from this solution moves it to the Default Solution; it doesn’t convert it to a non-solution flow. Don’t choose Delete from this environment unless deletion is intended.

2. Open the flow under My flows.

🔸 Go to My flows > Cloud flows and select the flow you just detached to open its details page.

3. Force the export page via the URL.

🔸 Look at the browser address bar. The URL ends in /details.

🔸 Replace /details with /export and press Enter, for example:

https://make.powerautomate.com/environments/<env>/flows/<flowId>/details
→ https://make.powerautomate.com/environments/<env>/flows/<flowId>/export

🔸 This opens the package export page directly, even when the button was hidden.

4. Configure the package and download.

🔸 Adjust the package name if needed.

🔸 Set the import behavior per resource, Create as new or Update.

🔸 Select Export. When the package is ready, save the .zip locally (use Download if it doesn’t start automatically).

The .zip can now be imported into any other environment via My Flows > Import > Import Package (Legacy).

🎉 Result

You get a standalone flow package (.zip) even when the Export button never appeared, no need to rebuild the flow or route it through a solution export just to move one flow.

🌟 Key Advantages

🔸 Unblocks the export: reaches the package export page when the UI button is missing.

🔸 Keeps the flow intact: Remove from this solution detaches without deleting.

🔸 No premium needed: standard package export/import for a single cloud flow.

⚠️ Good to Know

Replacing /details with /export is a practical UI workaround, not an officially documented feature. The documented paths are Export > Package (.zip) for a non-solution flow and exporting the solution for solution-aware flows. For proper ALM across environments, Microsoft recommends Dataverse solutions over single-flow packages. Note that non-solution package export/import requires third-party cookies enabled, and only the flow owner or co-owner can export.

🎥 Video Tutorial

Based on the tip “Export Power Automate When Export option is not available” by Malay Vasavada.

🛠️ FAQ

1. Why is there no Export > Package (.zip) for a flow in a solution?

Standalone package export is meant for non-solution flows. Solution-aware flows are exported by exporting the whole solution (as managed or unmanaged), so the single-flow Export > Package (.zip) option isn’t offered.

2. The button is still missing after removing the flow from the solution, what now?

Open the flow’s details page and change /details to /export in the URL to open the export page directly.

3. Will ‘Remove from this solution’ delete my flow?

No. Remove from this solution only detaches the flow from the solution. Delete from this environment is the destructive option, don’t pick that one.

4. Can I import the exported package anywhere?

Yes. Use My Flows > Import > Import Package (Legacy) and choose Create as New or Update. For repeatable, multi-flow moves, prefer Dataverse solutions.

🔗 Related Tips

• #PowerPlatformTip 48: Sharing of Flows & Power Apps, all the reliable ways to move flows and apps between people and environments.
• #PowerPlatformTip 8: Automate Backups & Restores for Flows, Apps & Solutions, schedule solution exports so you always have a .zip to restore from.
• #PowerPlatformTip 20: Change Flow-Owner, make a flow solution-aware to change its owner in place.