Learn how to migrate resources from one environment to another. These environments can be within the same tenant or across different tenants.

The scenario

One common scenario where you may want to migrate resources is where you have Test or Dev environments and a Production environment. Developers and testers have wide access to the apps in their environments. But when it comes time to migrate a new app to production, that environment has rigorous control over permissions to update and change it.

Another scenario is one where each customer has their own environment and data. When a new customer is added, a new environment is created for them, and you would migrate apps into their environment.

What resources you can migrate

There are different procedures for migrating each kind of resource.

  1. Connections, custom connectors, and flows: you can't be migrate these resources; you must recreate them in the destination environment.
  2. Gateways: gateways are only supported in the default (and {tenant name} (from preview) ) environments, so migration is not supported.
  3. PowerApps: you save the app locally in the origin environment by using PowerApps Studio for Windows or PowerApps Studio for web, and then you open the app and recreate it in the destination environment.
  4. Common Data Service entity schema changes, new entities, new permission sets, new roles: this is not supported for GA but is coming very soon.

Connections, custom connectors, and flows

These resources can't be migrated. You must create each one you need in the destination environment.

Gateways

Gateways are only supported in the default and {tenant name} (from preview) environments, so migration is not supported. You must create any needed gateways in the destination environment.

Migrating an app

  1. In http://web.powerapps.com, click or tap Apps, select the ellipses for the app you want to migrate, and then choose to edit the app in either the PowerApps Studio for Windows or PowerApps Studio for web.

  2. When PowerApps Studio opens, click Save as in the left navigation bar, select This computer, and then click or tap Save. Note where the file was saved on your local machine.

  3. Change the environment to the destination environment.

    For PowerApps Studio for web, return to http://web.powerapps.com to switch your environment and then re-open PowerApps Studio for web in the browser:

    For PowerApps Studio for Windows, you can change your environment by opening your account information:

  4. Open PowerApps Studio, which will now be in the destination environment. Click or tap Open in the left nav bar, and then click or tap Browse.

  5. Select your file from where you saved it when in the original environment, and then click or tap Open.

  6. You may need to address any compilation issues in the app, in accessing resources that may have different names, such as data connections and sources. An easy way to resolve compilation issues with the app is to remove and re-add the data sources for the app in the destination environment. See Understand data sources.

  7. Test the app to verify whether all compilation issues have been resolved.

Common Data Service entity schema changes, new entities, new permission sets, new roles

We do not currently support a way of migrating entities, permission sets, and roles from one Common Data Service database to another in a separate environment; however, this functionality is coming very soon.