"Exporting a Solution: Step by Step"

The solution export is the entry ticket to almost everything: delivery to another environment or analysis of someone else's solution. The path is short. But at three points, a choice decides what ends up in the ZIP file.

The path in the maker portal

Sign in at make.powerapps.com and pick the right environment at the top right. This is by far the most common mistake: the export runs in the default environment instead of the one you mean.

Then click Solutions on the left, select the solution you want and choose Export in the command bar. The platform offers to publish pending customizations. Always do that. Anything unpublished is missing from the export, and no warning appears.

Next comes the version number. Increase it, even if it is only an interim state. And note in one sentence what this version contains. Three weeks later, that sentence is the difference between a targeted rollback and guessing.

The one choice that really matters

Finally, the platform asks: managed or unmanaged. In short, unmanaged is the editable development state. Managed is the sealed delivery for test and production. The detailed comparison is in Managed vs. Unmanaged.

For analysis or documentation, the unmanaged export is the better one. It contains the structure completely and without the restrictions of a sealed solution. A managed export can be analyzed too. But statements about naming consistency and about telling your own components from standard ones are then only partly reliable.

What you hold afterwards

A ZIP file. Inside are the "solution.xml" (manifest, version, publisher, dependencies) and the "customizations.xml" (the actual configuration). Depending on the content, further folders for web resources, flows, plug-in assemblies or canvas apps are added.

Four pitfalls

Large solutions take time. With several thousand components, the export can take minutes and look like a freeze in the browser. Wait instead of clicking again.

Segmented solutions export only what is in them. If a field was never added to the solution, it is missing from the export, although it exists in the environment.

Environment variables can carry current values. On import, these overwrite the configuration of the target environment, without an error message. Before delivery, check whether the export contains a value next to the definition.

The export is not a backup of your data. It contains only the configuration and customizations, and no records. There are other ways to handle data.

And if it needs to be faster

If you export regularly, do not do it by hand. The Power Platform CLI handles export and unpacking on the command line. In a pipeline, you can automate both, including a check.

Microsoft itself provides detailed step-by-step screenshots in the documentation on exporting solutions.