ArcGIS Enterprise 11.5, part of the ArcGIS 2025 Q2 releases, will be available soon. Not only will ArcGIS Enterprise 11.5 on Windows and Linux be a long-term support release, bringing lots of exciting new features, but it will be the last release of the 11.x generation.

Some of the exciting things to look forward to in ArcGIS Enterprise 12.0 and beyond are new server roles, additional extensibility options, improved observability capabilities, and more. However, in this blog post, we will focus on the various removals and retirements that may necessitate some extra thought and planning before you can move to ArcGIS Enterprise 12.x.

Because ArcGIS Enterprise 11.5 is the last version in the 11.x series, this means it will be the last version to include ArcGIS Web AppBuilder, ArcGIS Configurable Apps, and Map Viewer Classic.

Following ArcGIS Enterprise 11.5, ArcGIS Enterprise 12.0 will be released as a short-term support version for Windows and Linux. This release will no longer include those long-loved applications and will mark the beginning of the 12.x generation of the software.

We appreciate that having ample time to understand and plan for upcoming changes helps ensure success for your organization. In anticipation of these upcoming releases, this blog will cover the specific changes you can expect in ArcGIS Enterprise 12.0 and provide guidance on how to ensure a successful upgrade to the 12.x generation of ArcGIS Enterprise by planning now for ArcGIS Enterprise 11.5.

ArcGIS Enterprise 12.0 will bring plenty of exciting new features, in addition to the changes covered in this blog. Stay tuned for a blog on new features in ArcGIS Enterprise 12.0 coming alongside its release!

Quick Links

Why the move from 11.x to 12.x? | Other changes to expect with ArcGIS Enterprise 12.0 | Planning your migration path | Why consider ArcGIS Enterprise 11.5?

Why the move from 11.x to 12.x?

To understand the reason behind this change, we need to first recognize that ArcGIS Enterprise has recently included both the ArcGIS API for JavaScript 3.x and the ArcGIS Maps SDK for JavaScript 4.x. The JavaScript Maps SDKs are essential for powering the web applications within the ArcGIS Enterprise portal. You may have noticed the presence of both the JavaScript 3.x and 4.x versions, with older 3.x applications – such as ArcGIS Web AppBuilder, ArcGIS Configurable Apps, and Map Viewer Classic – offered alongside their modern 4.x successors – ArcGIS Experience Builder, ArcGIS Instant Apps, and Map Viewer.

We are transitioning to ArcGIS Enterprise 12.0 because ArcGIS Web AppBuilder, ArcGIS Configurable Apps, and Map Viewer Classic are being retired and will be removed from ArcGIS Enterprise. These changes build on the July 2024 retirement of ArcGIS API 3.x for JavaScript.

Other changes to expect with ArcGIS Enterprise 12.0

In addition to the removal of ArcGIS Web AppBuilder, ArcGIS Configurable Apps, and Map Viewer Classic with ArcGIS Enterprise 12.0, the ArcGIS Data Store tile cache data store and metadata editor classic are being retired as well. The ArcGIS Data Store tile cache data store has been superseded by the ArcGIS Data Store object store and the metadata editor classic is superseded by the metadata editor.

Planning your migration path

Before upgrading to ArcGIS Enterprise 12.0, it will be essential to ensure that all JavaScript 3.x-based apps are migrated to a modern JavaScript 4.x-based option. Doing this while using ArcGIS Enterprise 11.5, or earlier, will allow you to view and configure both JavaScript 3.x and 4.x apps side-by-side to ensure parity.

It’s also important to make sure that any workflow reliant on the ArcGIS Data Store tile cache data store and metadata editor classic are evaluated as well.

The steps involved in migrating or recreating your apps will vary depending on the specific application you are looking to migrate.

Migrating from ArcGIS Web AppBuilder to ArcGIS Experience Builder

ArcGIS Web AppBuilder has been replaced by ArcGIS Experience Builder. Starting with ArcGIS Enterprise 12.0, you will no longer be able to view, create, or edit ArcGIS Web AppBuilder apps. In most cases, ArcGIS Experience Builder will be the right tool to build enhanced versions of your web applications, however depending on the features of your apps, you may find another app builders is a better fit.

To begin planning for your migration, review the widget functionality matrix to understand which ArcGIS Web AppBuilder widgets and capabilities have been migrated to ArcGIS Experience Builder. Create an inventory of your current Web AppBuilder apps, identify the components and functionalities being used, and then build new apps in Experience Builder to migrate your workflows. From here, you can add your data, reconfigure widgets, and test your new apps before sharing.

The complexity of your migration effort depends on how many ArcGIS Web AppBuilder apps your organization uses. You will need to assess whether all apps should be migrated or if some can be consolidated or retired. From there, you can create a tailored migration timeline that fits your organization’s needs.

ArcGIS Enterprise 11.5 will provide a strong foundation for migrating from ArcGIS Web AppBuilder to ArcGIS Experience Builder. Most notably, it will include Express Mode in ArcGIS Experience Builder, enabling you and your organization to create modern web experiences with ease. For more information on what is required to migrate from ArcGIS Web AppBuilder to ArcGIS Experience Builder, we encourage you to take advantage of the resources available, including a dedicated Esri Community topic, documentation pages, and blogs.

Migrating from ArcGIS Configurable Apps to ArcGIS Instant Apps

ArcGIS Configurable Apps have been replaced by ArcGIS Instant Apps. While many ArcGIS Configurable Apps were removed at ArcGIS Enterprise 11.0, some templates like Basic Viewer, Compare, and Crowdsource Manager will still be available in ArcGIS Enterprise 11.5. To migrate, take an inventory of your current ArcGIS Configurable Apps, and then reference the table in the deprecation notice for ArcGIS Configurable Apps. This table will provide you with the recommended replacement for each of the deprecated ArcGIS Configurable App templates. In most cases, these recommended replacements will be an ArcGIS Instant App, but you may also consider other ArcGIS apps such as ArcGIS Experience Builder or ArcGIS StoryMaps as a solution.

Once you have your inventory of ArcGIS Configurable Apps and have determined the most suitable replacement for your apps, you can create a new app and configure it to serve the purpose, workflows, and support the data from your existing configurable app. To ensure the app is working as needed, you should test the app and its associated workflows before sharing it with your organization. For additional resources to support your migration effort, be sure to check out the product documentation and blogs.

Moving from Map Viewer Classic to Map Viewer

Map Viewer Classic has been superseded by Map Viewer. Moving from Map Viewer Classic to Map Viewer does not require any migration of content. To get started with Map Viewer, just open Map Viewer from the item details or My Content pages, the Map tab, or the app launcher. Maps created in Map Viewer Classic will open and work as expected in Map Viewer.

Although no content migration is required, Map Viewer provides a new, more intuitive and performant interface and additional tools. As such, your users may need to spend some time adopting Map Viewer and understanding all its offerings. To be ready for the removal of Map Viewer Classic, it is recommended to start using Map Viewer today if you are not already.

Check out the product documentation for guidance on how to get the most out of Map Viewer.

Migrating from the tile cache data store to the object store

In ArcGIS Enterprise 11.4, the ArcGIS Data Store tile cache data store is deprecated and replaced by the object store. This means that the object store is now a component of a base ArcGIS Enterprise deployment.

When migrating from ArcGIS Data Store tile cache data store to object store, it’s important to first evaluate if you are using the tile cache data store; this is the data store historically used to power hosted scene layers. Inventorying your services can be done using the MigrateSceneServices utility in analysis mode, which was introduced with ArcGIS Enterprise 11.4. These service caches can be migrated to the object store by running this tool in execution mode or by item owners directly through the ArcGIS Enterprise portal. Read the blog ArcGIS Enterprise: Migrate to the object store to learn more in-depth about the steps and considerations involved with this migration workflow.

Migrating from metadata editor classic to metadata editor

For a smooth transition, it is recommended to proactively begin adjusting your organization’s workflows to use the new metadata editor introduced in ArcGIS Enterprise 11.3, in preparation for the retirement of the classic metadata editor. If you encounter concerns or obstacles during this process, please share your feedback on the Metadata, Catalogs and Search Esri Community, or reach out to Esri Support for assistance. Read more about the migration from metadata editor classic to metadata editor here.

Why consider ArcGIS Enterprise 11.5?

As your organization prepares for the eventual removal of Map Viewer Classic, ArcGIS Configurable Apps, and ArcGIS Web AppBuilder, and the other changes coming in 12.0, ArcGIS Enterprise 11.5 will provide a strong foundation for necessary preparation and migration work. This is because ArcGIS Enterprise 11.5 will include the latest updates to ArcGIS Experience Builder, ArcGIS Instant Apps, and Map Viewer introduced in the ArcGIS Online February 2025 update. This means that there will be key remaining parity functionality you may have been waiting on in the 4.x-based applications.

Additionally, ArcGIS Enterprise 11.5 will be a long-term support release, guaranteeing patching and support until June 2029. This gives you plenty of time to plan and execute the upgrade to ArcGIS Enterprise 12.0 when your organization is ready.

As with any upgrade, take a thoughtful approach and decide when an upgrade will work best for your organization. The changes coming in ArcGIS Enterprise 12.0 will impact organizations differently depending on their use of JavaScript 3.x-based applications. We recommend starting out by getting an inventory of any content or apps that may need to be migrated and creating a migration plan and timeline. We understand that these changes may be significant for your organization and will be providing additional content to support you. Please connect with us on Esri Community to let us know how we can help you feel prepared for ArcGIS Enterprise 12.0!