Migrating Experience Builder gives Error: This is an experience. Please switch to experiences tab and try again

[GeeteshSingh07]

Hi,

I am trying to migrate experience builder from one Portal organization to another. Workflow: Solved: Re: Replicate Experiences between portals - Esri Community

I have downloaded the experience from source portal. Made the changes (Changed Portal URL) to config.json file.

When uploading the zipped folder into target portal ExB, I am getting error "Error: This is an experience. Please switch to experiences tab and try again".

The version of both source & target exB is 1.15.

[JeffreyThompson2]

I tried @BrianLeroux's hack a few weeks ago and got the same error. I was not able to upload into Developer Edition on the new Portal, but I could deploy the application to a server.

[BrianLeroux]

Hopefully I can help here. In experience builder there might be a couple of things that might matter that I do not account for in my instructions. First I am in "Full Mode" and not in "Express Mode". There is a toggle in the top right corner to switch. 

Second I am on the Experiences tab and not on the Templates tab.

Other than that, makes sure you are updating both config.json files. Feel free to post screenshots or video of what you try and I will see if anything stands out to me. 

[GeeteshSingh07]

Thank you @JeffreyThompson2 & @BrianLeroux .
I have updated in both config files and importing through Experience tab.

I couldn't understand where full mode & express mode is. 

[BrianLeroux]

I just looked and express mode availability started on 1.16 and you are on 1.15 so that is not an issue at play. That said, my testing has been on 1.16 so there is a chance the procedure is not the same as on previous versions. @JeffreyThompson2 Were you on 1.16 when you tried or an earlier version?

@GeeteshSingh07 Are you able to 

[JeffreyThompson2]

I was using 1.14 at the time.

[GeeteshSingh07 · Accepted solution]

Thank you for all your help @BrianLeroux @JeffreyThompson2. I was able to resolve the issue with this workaround suggested by Esri:

1. Extract the zip folder of the Experience app.
2. Once you extracted the zip folder, navigate to <app_name>/cdn/<appId>
3. We will use the files in this directory later on.
1. Notes: <appId> is the integer corresponding to the apps you created in order.
4. Next, create a new Experience app in ArcGIS Experience Builder Developer Edition that is connected to another environment. 
5. Navigate to the app folder which is located at <install_folder>/server/public/apps/<appId>.
6. Find the appId for the Experience app that you just created. If it is a newly created application, it should be the folder with the highest id.
7. Copy the content in the app folder at <app_name>/cdn/<appId> to the app folder in ArcGIS Experience Builder Developer Edition, connected to the other portal environment, which is located at <install_folder>/server/public/apps/<appId>.
8. Open Experience Builder Developer Edition (connected to the other portal environment) at https://localhost:3001/.
9. Refresh the page. 
10. Click on the app created in step #3.
11. You should see the content from the zip folder of the Experience app being imported into Experience Builder Developer Edition connected to the other portal environment.

[BrianLeroux]

Hi @GeeteshSingh07  - Thanks for the update.  A couple of questions on this before I try this method. Do you have 2 instances if eXb dev running for different environments? I typically just use one and log in and out of different environments and only the apps for the current environment show after logging in.

After you ran this process, how much in the new experience was broken? I have to imagine anything related to data sources from the previous environment would be broken and need to all be links to new data sources. 

[GeeteshSingh07]

Hi @BrianLeroux , apologies for the delayed response.

The server and client are initiated once through VS Code. One ExB (ArcGIS Enterprise Organization A) is opened in Chrome and other ExB (ArcGIS Enterprise Organization B) is opened in Edge.

Yes, everything was broken. I need to manually set the datasources for every widget. I haven't done this yet, as I was only exploring different ways to migrate and not actually migrating.