How to export Portal settings and import to another env?

[Audreyma]

Hi everyone,

Good day!

I created a portal in sandbox env.  Now all configurations are finished, so I want to export the portal setting and import to another test env.

I found the below manual and tried once.

Migrate portal configuration - Power Apps | Microsoft Docs

Schema is created and exported normally.  However, when import to the test env, the below error happened and import failed.

Having checked in the test env, only 1 entity was uploaded and some fields are missing.

Anybody faced similar issues?

[OliverRodrigues]

Hi, have you provisioned the portal in your TEST environment? Also is it the same Portal type/template?

If yes, did you take a look at the logs from Config Migration? 

[Fubar]

• Are you trying to just do 2 entities? (only 2 are showing in your screen shot what are they?, the full portal export should have a lot more)
• Just the Site Settings? (would be 1 entity?)
• or are you trying to move the whole Portal? then make sure you export from your soruce instance using the correct schema file provided by Microsoft (download from the link you provided) for the type of Portal you have in your source, and make sure you have the same type of Portal in your target that you are importing into (note: you must have installed a portal into your target before import)

[Audreyma]

Hi @Fubar 

I want to copy the whole portal setting into the test env, including entity,web page and access setting.

However, when creating schema, I need to select a solution first.  In the solution, it seems that only entity can be selected.

Thus my schema only contains entity setting.

Yesterday I forgot to create the same type portal in my test env.  I created it today and tried the import again, but failed with same error.

Do you know how to create a full portal export?

[Fubar]

You do not need to select a solution file - you would do this if you were going to create a Schema file from scratch (but Microsoft provides you with one),

You start from here:

After you login, your next step is to load the Schema File that Microsoft provide and give a file name for the data that will be exported, then hit Export at the bottom of the form

That gives you all the Portal, now you use the Config Migration Tool again and select the Import Data option, login to your target environment, select your data file (what you exported), then import.

[Audreyma]

Hi @Fubar ,

Thank you for your reply.

Since I created the current portal in sandbox env from blank, so I download the schema file marked in red.

Both export and import were completed successfully.

However, checking the new portal in my test env, I found the following issues.

1. Entities were not copied from sandbox env.

2. Customer portal exists, but its address is not the new one in test env but the one in sandbox env. 

3. Corresponding web pages of sandbox env also exist, but were linked to the sandbox Customer portal.

After import finished, are there any manual settings required?

[Fubar]

1. What do you mean by Entities were not copied? (if you created a custom entity etc you need to package that stuff in Your own Solution File and move it)

2. Please show some screen shots etc so we know what you are talking about for this item

3. Web pages in an environment link to the Portal that is in that environment, they do not point to some other environment (unless you hard coded urls in JavaScript etc).

[Audreyma]

Hi @Fubar ,

Sorry for causing the misunderstanding.

Backgroud:  I have 2 envs in powerapps, Env1 and Env2.  Env1 is sandbox env, Env2 is a free environment for individual use, created through Power Apps Community Plan.

I created a customer portal in Env1 through "Portal from blank".  Tables(its old name is Entity) and webpages are configured.

Purpose:  I want to copy the entire portal setting to Env2. 

Action:  Based on your explanation, I created a blank portal in Env2 first.  Then using the below schema file to export data from Env1 and import to Env2. Import and export finished normally.

Issue:  After import, in Env2 I can't find the same tables (entities) configured in Env1.  I originally thought that the import should also include Table setting.

So you mean that to copy Table setting,  I need to create a solution in Env1 and added the related tables in the solution, then import the solution into Env2, right?

Actually, I also tried it, but solution import failed with the below error.

Error:  "There are no dependencies. Before installing this solution, please install the following solution "Active", "MicrosoftPartnerPipeline (9.2.2009.3)", "FieldService (8.8.0.88)", "msdynce_MarketingPatch (9.0.1904.1019)", "MicrosoftDynamics_Marketing (1.35.1026.0)", "ProjectService (3.10.0.31)", "RelationshipAnalytics (9.0.1.0965)" ".

I don't know if it's because Env2 is a free env created through Power Apps Community Plan, some functions are not complete.

[Fubar]

Its because you have dependencies to those other Solutions in what you are attempting to move.  Your initial environment looks like it had all of the Apps installed (addons like Field Service etc), and your new environment doesn't.

You can try creating a new Solution file and only include absolutely what is necessary - only what you changed - (but if this will work really depends on what changes you made and where), or try removing the other Apps, or  add the other apps into your 2nd environment.

[Akshay_M92]

Hi,

It looks like the error occurred due to missing customizations (to be more specific "Missing Fields on Entities") in target environment compare to source environment from where you exported the schema.

The Configuration Migration tool uses schema to export and import configuration data. The tool does not migrate entities or entity schema. Migration may fail with missing elements such as entities and fields when configuration data has mismatch with selected schema.

During export, ensure the source environment contains portal entities as specified in Configuration Migration tool schema file. You can still alter the schema files to add, remove, and modify entities, attributes, and so on to migrate subset of configuration data.

During import, ensure the destination environment contains the same portal type already installed with any additional customizations such as entities, fields, forms or views imported separately as solutions.

You can refer the below link for more information.  
https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/migrate-portal-configuration