ArcGIS development

Web AppBuilder to Experience Builder migration

Esri is retiring Web AppBuilder. In ArcGIS Online, existing apps can no longer be updated from Q4 2026 and stop working in Q2 2027. We inventory your apps, rebuild them in Experience Builder, rewrite custom widgets on the ArcGIS Maps SDK for JavaScript 4.x, and update every link that points at the old apps.

The deadline at a glance

Esri has published a phased retirement for Web AppBuilder in ArcGIS Online. ArcGIS Enterprise follows a different path, tied to the version you run.

PlatformWhat changesWhen
ArcGIS OnlineNew Web AppBuilder apps can no longer be createdQ1 2026
ArcGIS OnlineExisting apps can no longer be updatedQ4 2026
ArcGIS OnlineExisting apps are retired and stop workingQ2 2027
ArcGIS Enterprise11.5 is the last release that includes Web AppBuilderUpgrading beyond 11.5 means migrating first

Source: Esri, ArcGIS Web AppBuilder retirement.

What carries over, and what has to be rebuilt

Your web maps, layers and pop-ups are separate items in ArcGIS, so Experience Builder uses them as they are. The app itself does not convert.

Part of the appWhat happens in a migration
Web maps, layers, pop-upsReused directly in Experience Builder
Standard widgetsMost have an Experience Builder equivalent, but some do not; we check each one against Esri's widget matrix
Custom widgets and themesCannot be converted. Esri states that direct conversion is not possible, so they are rewritten on the ArcGIS Maps SDK for JavaScript 4.x
Layout and brandingRebuilt in Experience Builder's page and layout system, usually with a cleaner mobile view
App links, embeds and bookmarksThe app URL changes, so every link and embed that points at the old app is updated

Custom widgets are where most of the effort goes. Web AppBuilder runs on the ArcGIS API for JavaScript 3.x, which Esri is also retiring, while Experience Builder uses version 4.x. The logic of a widget carries over; the code does not.

How we migrate your apps

  1. Inventory. We list every Web AppBuilder app in your organisation with its widgets, custom code, data sources, users and where it is linked or embedded.
  2. Decide per app. Some apps are no longer used and can be retired. Some fit an Instant App or a Dashboard. The rest are rebuilt in Experience Builder.
  3. Map the widgets. Each standard widget is matched to its Experience Builder equivalent, and gaps are flagged before any build starts.
  4. Rewrite custom widgets. We rebuild them in the Experience Builder developer edition with React and the ArcGIS Maps SDK 4.x, keeping the behaviour your users rely on.
  5. Test with your users. The new app runs beside the old one so your team can compare workflows, not just screens.
  6. Cut over. We share the new app, update links and embeds, and retire the old app on a date you choose.

The code for custom widgets goes into a repository you own, with notes on building and deploying it.

Who this is for

  • ArcGIS Online organisations with Web AppBuilder apps still in use, especially public-facing ones.
  • ArcGIS Enterprise teams that want to upgrade beyond 11.5, or that need to plan for it.
  • Teams with custom widgets written by staff or contractors who have since moved on.
  • GIS managers who need a clear inventory and plan to put in front of budget holders.

Web AppBuilder is not the only Esri app being retired. Our guide to migrating from ArcGIS Workforce and AppStudio covers the others.

Frequently asked questions

Can Web AppBuilder apps be converted to Experience Builder automatically?

Not fully. Experience Builder offers templates that help recreate a Web AppBuilder layout, and your web maps carry over unchanged. Custom widgets and themes cannot be converted directly and must be rewritten.

We use ArcGIS Enterprise. Do we have to migrate now?

Web AppBuilder is included up to ArcGIS Enterprise 11.5, so existing apps keep working while you stay on that version or earlier. You will need to migrate before upgrading beyond 11.5, so it is best planned together with your upgrade.

How long does a migration take?

It depends on the number of apps and, above all, the number of custom widgets. Apps built only from standard widgets move quickly. After the inventory we give you an estimate per app.

Do you need access to our ArcGIS organisation?

Yes, through named accounts that your administrators create with only the permissions the work needs. We follow your change and deployment procedures, and access is removed when the work ends.

Are you an Esri partner?

No. Jugrafiya is not an Esri partner. Our engineers build with ArcGIS on client projects, and you keep licensing ArcGIS directly from Esri or your local distributor.

What happens to our data during the migration?

Nothing changes in your data. Experience Builder reads the same web maps and layers, so the migration touches the apps, not the content behind them.

Running Web AppBuilder apps today?

Send us a list of your apps, or just the links. We will reply with a migration plan, the custom work involved and a suggested order.

How we work: engagement models, ownership and handover