Overview of exporting and importing canvas apps
In this article, you'll learn about the different options available to export and import canvas apps in the form of singular app file, app package, and considerations from the application lifecycle management (ALM) perspective. To effectively manage ALM, it's recommended to use solutions. Canvas apps packages don’t support ALM and should only be used for basic import and export capabilities when Dataverse isn’t accessible.
You can export and import canvas apps using one of the following options:
- Export and import canvas apps as app packages
- Export and import canvas apps as part of solutions
- Export and import a canvas app as a single app file
Important
- Canvas app packages can't be used with Dataverse solution packages because of the package incompatibility.
- Canvas apps that have Dataverse dependencies, such as flows, connection references, etc. are not supported for canvas app packages. For ALM capabilities in Microsoft Power Platform environments, use Microsoft Dataverse and solutions instead of the canvas app package export and import. More information: ALM overview
- An App Insights instrumentation key may be present in imported canvas apps. Inspect the instrumentation key after importing an app to ensure it corresponds to the desired App Insights resource.
Export and import canvas apps as app packages
You can export and import canvas apps by using packages. This feature allows you to export an app from one environment and import it to another.
Resources included in canvas apps packages
An app can consume different resources. For example, most apps use connections. Other apps might use Power Automate, have custom connectors, or connect by using gateways to on-premises resources. Some apps might also use Dataverse customizations
The following table explains different resource types, supportability, and import options.
Resource type | Supported | Import options |
---|---|---|
App | Yes, for canvas apps | There are two options to import an app into an environment:
|
Power Automate | Yes | There are two options to import a flow into an environment:
Note: All resources that the flow depends on will also be included in the app package that's exported and will need to be configured when the package is imported. You can also export and import flows by using solutions. More information: Power Automate solutions |
Custom connectors | No | Exporting a custom connector isn't supported. You need to re-create the custom connector on the target environment. |
Connections | No | Exporting a connection isn't supported. You need to re-create connections on the target environment. |
Dataverse customizations | No | Exporting Dataverse customizations as a part of a canvas app package isn't supported. You need to use Dataverse solutions instead. More information: Dataverse solutions |
Gateways | No | You can't export or import gateways. You need to re-create gateways on the target environment. |
Permissions
Only the Owner or Co-owner of an app can export a canvas app package. To import an app, the Environment Maker permission is required on the destination environment.