Replicate Experiences between portals

[BrianLeroux]

For eXb Dev edition, does anyone have a good way to make a copy of an experience from one portal to another. I have tried a download and import but that does not work between 2 different portals. My issue is that I have 3 environments including a development, testing and production. creating all these experiences 3 different times is such a huge waste of time so hoping there is a better way. I am not sure how ESRI overlooks these multi environment organization scenarios.

[JeffreyThompson2]

https://developers.arcgis.com/python/latest/guide/experience-builder-workflows/#working-with-local-e...

The Python API has a module specifically designed for migrating Experience Builder between Portals. Let me know how well it works. I haven't tried it myself.

[BrianLeroux]

Looking into this now.

The experience I built is not on portal per se. It was just created in ExB dev edition while authenticated to our dev portal. It is a local experience at this point but is tied to the dev portal now and trying to download and import when ExB is logged into my Test portal just gives and error that it can only import into the dev.

[Laura]

Using developer edition might be the easiest way for you. Otherwise I know AGO Assistant can clone but I've never done it across Portals. 

https://support.esri.com/en-us/knowledge-base/how-to-transfer-content-from-one-arcgis-online-organiz...

Steps to migrate: https://community.esri.com/t5/arcgis-enterprise-documents/migrate-content-for-arcgis-enterprise-arcg...

[BrianLeroux]

I am using ExB dev edition. I should have stated that.

[BrianLeroux]

Adding info for clarity.

I am working with local projects in ExB. I am creating the initial local experience while connected to our DEV portal. I then need to duplicate that experience local but need it to be for my TEST portal so I can appropriately map to the correct data sources. i do not mind doing that manually. I am really hoping to get all the design elements correct as there are a lot of little setting that take a while to duplicate.

[BrianLeroux · Accepted solution]

I found some success going a very manual route to start. Here is what worked for me.

1. Log into ExB dev for your first portal environment.
2. Download the experience from first portal environment.
3. Extract the zip file
4. navigate within the extracted folders to AppName/cdn/3 and find the config.json file.
5. Edit config.json. towards the bottom you will find attributes. One being portalURL that will need to be updated to the new portal environment URL. Also in the dataSources section you will need to update any portalURL  and the itemIDs to match the items in your new portal environment. 
6. Save that config.json. 
7. Copy that config.json file and overwrite a second config.json file that is at AppName/cdn/3/resources.
8. Re-zip the entire app folder.
9. Log into ExB dev for your second portal environment.
10. Run an import and select the new zip file you created.

This brought the app into my second environment and all functionality works including any images and a custom widgets I had. This was a very simple experience so there could be issues with more complex experiences but tough to say without more testing.

[BrianLeroux]

This seems to work pretty well. The only issue I have is sometime the import hangs and fails. After trying a few attempts it usually goes through.

[DanJiang]

ArcGIS Assistant could be an option to try. https://guide.assistant.esri-ps.com/docs/

[BrianLeroux]

Unfortunately, not. That only works with Portal or AGOL whereas I am working with local projects in ExB Dev.