ArcGIS Enterprise 12.x is Out Now: Planning for Your Upgrade and What to Expect

February 6, 2026

Jess Sourbeer

ArcGIS Enterprise 12.0 has arrived, marking the next chapter in the evolution of Esri’s ArcGIS Enterprise platform. This release introduces a range of new capabilities and refinements across performance, security, and application development, setting the stage for how organizations will build, deploy, and scale GIS moving forward. For many teams, this represents the first real glimpse into where the platform is headed and how today’s systems can begin aligning with what’s next.

The release of ArcGIS Enterprise 12.x represents an important milestone for Enterprise GIS, introducing platform enhancements that most organizations will eventually adopt. While 12.0 itself is a short-term release, it provides an early opportunity to understand upcoming shifts and prepare for a smoother transition to the next long-term support release especially for organizations with custom web applications built on the ArcGIS API for JavaScript 3.x, as well as applications created with ArcGIS Web AppBuilder and ArcGIS Configurable Apps.

It is mission critical to plan for this change to avoid unexpected disruptions.

Understanding Breaking Changes

A breaking change occurs when a platform update causes existing applications or code to stop functioning as expected.

While the ArcGIS API for JavaScript 3.x was officially retired in July 2024, it continued to be available through ArcGIS Enterprise 11.5. With the release of ArcGIS Enterprise 12.0, that support ends. The 3.x API and products built on it, including custom applications, ArcGIS Web AppBuilder, and ArcGIS Configurable Apps, are no longer included or supported in the platform.

Graphic illustrating the ArcGIS Enterprise 12.0 upgrade, showing legacy JavaScript 3.x applications transitioning to Enterprise 12.0, with icons representing Web AppBuilder and Configurable Apps on the left and a warning symbol indicating breaking changes on the right, all displayed in blue tones.

As a result, organizations running applications built on JavaScript 3.x will encounter breaking changes when moving to Enterprise 12.0 or future releases. These applications will need to be migrated to modern frameworks in order to remain supported and compatible with the evolving ArcGIS platform. Organizations that wait to address these changes risk compressed timelines, limited testing windows, and higher upgrade complexity. Planning early allows teams to approach this transition thoughtfully, preserving functionality, minimizing disruption, and aligning applications with the direction of the platform.

Why Planning Ahead Matters 

Waiting until an upgrade is unavoidable can introduce challenges such as:

  • Increased technical debt

  • Limited time for testing and validation

  • Higher risk during production upgrades

  • Difficulty maintaining or extending legacy codebases

Planning ahead gives organizations the time and flexibility to:

  • Inventory existing applications and their dependencies

  • Identify which applications should be modernized, refactored, or retired

  • Incorporate new capabilities available in the ArcGIS Maps SDK for JavaScript (4.x) as part of the transition

Taking a proactive approach reduces risk and helps ensure a smoother transition to ArcGIS Enterprise 12.0 and future releases.

Recommended Migration Path

As organizations prepare for ArcGIS Enterprise 12.x, aligning applications with Esri’s modern development frameworks is key to maintaining support, performance, and long-term flexibility. At a high level, recommended migration paths include:

  • Custom JavaScript 3.x applications should be migrated to the ArcGIS Maps SDK for JavaScript (4.x) to ensure continued support and compatibility with current and future Enterprise releases.

  • ArcGIS Web AppBuilder applications should be transitioned to ArcGIS Experience Builder, which provides a more flexible, modern framework for building configurable web experiences.

  • Configurable applications should be evaluated and migrated to ArcGIS Instant Apps or other modern alternatives that better align with the evolving ArcGIS platform.

Diagram showing recommended migration paths for ArcGIS applications, with arrows indicating transitions from JavaScript 3.x custom applications to the ArcGIS Maps SDK for JavaScript 4.x, from Web AppBuilder to ArcGIS Experience Builder, and from Configurable Apps to ArcGIS Instant Apps.

Blue Raster Can Help You Upgrade

As organizations plan for ArcGIS Enterprise 12.x, the focus often extends beyond the platform upgrade itself. Key steps include assessing the current environment, developing a modernization roadmap, testing early and often, and identifying opportunities to take advantage of newer capabilities across the ArcGIS ecosystem.

Cloud-Capabilities-Blue-Raster

Blue Raster works with organizations throughout this process, helping to:

  • Plan and execute ArcGIS Enterprise 12.x upgrades

  • Modernize applications built on the ArcGIS API for JavaScript 3.x

  • Preserve critical application functionality during transitions

  • Explore and implement capabilities available in modern ArcGIS APIs and frameworks

We partner with teams to ensure both platforms and applications evolve together, supporting a smoother transition today while positioning systems for what comes next.

Scroll to Top