Why?
Without the need for third party paid tools, you may want to migrate the configuration of your Power Apps Portal from either a backup or another environment. Only the configuration because content has its own migration path 🚥.
What?
A post on how to use the Configuration Migration tool within the XRM Tool to move a Power Apps Portal Configuration from one environment to another.
How?
So you have a fully configured Source Portal and a blanco Destination Portal in two different Power Platform Environments.
1) If not already done before you need to install the XRM tools of which the ConfigurationMigration is the one we will be using. A web page with a pretty good instruction is that of Microsoft using PowerShell to install the packages: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/download-tools-nuget.
2) If you have run the script, you will find the different tools in a Tools folder probably in your root User folder:
You can open the ConfigurationMigration folder and double click on the DataMigrationUtility.exe file to open the application.
3) The first important step is to have the xml-schema of all the entities being used by the Source Power Apps Portal. One way to do this, is to select the Create schema option in the DataMigrationUtility and select all the entities, relationships and definitions being used by your source Portal 🤯. The easier way is to visit this Microsoft web page: https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/migrate-portal-configuration and get the default schema for the Customer Portal (blank portal) 🤓.
TIP: add additional solution configuration in the same schema from your Source Portal to get all configuration data in one single schema making the export and import as less work as possible 💡.
4) Now you have the schema you need to get all the data you want in the destination Portal, you can use the Export data option of the DataMigrationUtility. Just select the Schema file of Step 3, determine a location to save the export en let the magic begin 🧙♂️.
5) After a successul export you will have a .zip file that you can import by selecting the Import data option of the DataMigrationUtility after connecting to the Destination Portal. Please note that if your portal has any relation to another solution (like a web page with an Entity list showing a custom Entity), you need to install that solution on your environment first or if your solution is built on Portal Entities install that solution last.
Before this step my new portal with custom installed solutions still looked like:
After this step (and a few minutes wating):
So now we have moved over the Power Apps Portal configuration from one environment to another in a way that is reusable multiple times.
Easy right! 🤩
