topic Re: Can't import 1.18 Experiences into 1.19 developer edition in ArcGIS Experience Builder Questions

Can't import 1.18 Experiences into 1.19 developer edition

ericsamson_tract — Thu, 13 Nov 2025 21:34:57 GMT

Hey everyone,

I am attempting to migrate to the new 1.19 version of EB developer edition.

When I attempt to import a previous experience builder project (zip file) that I had in 1.18, I get the following error message:

"Failed to import the experience. This experience can only be imported by users of portal: {portal url}"

This is strange because I am currently logged into that portal url in the new 1.19, and it's using the correct client id.

I double checked and I can import this zipfile into 1.18 with no issues.

I tried manually copying the project into the server/apps folder, but it did not show up within the EB dashboard. I also tried creating a new template within the dashboard, then copying my old project into that, and it then disappeared from the EB dashboard

Not getting any helpful console logs except for:
site-components.js:635 Uncaught (in promise) TypeError: Cannot set properties of null (setting 'value')
at site-components.

Tracing that down didn't help much

Anyone else experiencing this? Any ideas?

Re: Can't import 1.18 Experiences into 1.19 developer edition

shodge_fsu — Fri, 14 Nov 2025 20:56:09 GMT

I am getting the same error and am working on a solution. My guess is one of the custom widgets I am using is not compatible with the new code. I think my strategy wll be to make a copy of my app and then start deleting custom apps one at a time and see if that is the problem.

Re: Can't import 1.18 Experiences into 1.19 developer edition

shodge_fsu — Mon, 17 Nov 2025 16:03:28 GMT

I just tried creating a 1.18 app with just a map, export it and then tried to import it into 1.19. It failed too. I highly suspect that you will have to upgrade to react verion 19 (as this page says....) before things will import. Just a guess though. I am not in a position to upgrade for awhile so I cannot do any further analysis.

You cannot (easily) have both versions 18 and 19 running on the same machine.

Re: Can't import 1.18 Experiences into 1.19 developer edition

ericsamson_tract — Fri, 21 Nov 2025 17:24:53 GMT

Maybe I am confused, wouldn't the new version 1.19 come bundled with the new version of react? Also, if you tried to import a blank map from 1.18, wouldn't that imply that there is something more than just the custom widgets affecting this? I feel like this is potentially a bug in the new developer edition not being able to import previously created applications, but so far I have only heard of troubles from the two of us.

Re: Can't import 1.18 Experiences into 1.19 developer edition

KeyHunter — Fri, 19 Dec 2025 19:19:27 GMT

Any news on this? I am getting the same issue and unable to load a 1.18 into 1.19 with an error code of "this experience can only be imported by users of portal://myportal address

I did a search in visual studio for portalurl and checked and they all point to portal://myportaladdress.

I thought the same thing with custom widgets or updated dependencies. I set up three different EB 1.8 dev folders. One for out of the box widgets, one for custom widgets and one for internal portal applications as a new development structure to try and track down inconsistencies.

Still giving the same error no custom widget and portal://myportal address painstakingly searched through the config.json.

Anyone with new clues?

Re: Can't import 1.18 Experiences into 1.19 developer edition

gkatsamb — Thu, 29 Jan 2026 20:38:29 GMT

Same thing is happening to me; I even tried the npm ci on server and client before, eventually contacted ESRI support, after a few weeks we both gave up and hoping V 1.20 wont have this issue. I did find out with ESRI that portal address is changing first letter to a capital lol

Re: Can't import 1.18 Experiences into 1.19 developer edition

gkatsamb — Fri, 27 Mar 2026 14:55:18 GMT

So ESRI support could not figure this out, we did find out that for some reason portal address in one app was being "Proper Cased" but not in the other. We determined that we would bypass 1.19 and see what happens in 1.20. Well same thing is happening so i reopened support case.

Re: Can't import 1.18 Experiences into 1.19 developer edition

gkatsamb — Thu, 02 Apr 2026 14:17:28 GMT

ESRI-Support (always a joy to work with them) found a solution.

Part 1: Experience Builder v1.20:
Create a blank experience builder app. Locate the app directory on your server>> arcgisexperiencebuilderv1.20/server/public/apps/1 (The number 1 will vary depending on your app ID).
Part 2: Experience Builder v1.18:
Navigate to the app you want to migrate via the server directory, not the downloaded app >> arcgisexperiencebuilderv1.18/server/public/apps/0. (The number 0 will vary depending on your app ID).
Copy the resources folder and config.json file.
Part 3: Migration:
Navigate to the blank app created in v1.20 >> arcgisexperiencebuilderv1.20/server/public/apps/1
At this location, replace the resources folder and config.json file from Part 2 i.e, app from v1.18. Launch Experience Builder v1.20 and check if the migration was successful.