Umbraco versioning tends to stay in the background until something forces it forward. For many teams, that moment is now.
Umbraco 13 reaches end of life at the end of this year. That shifts this from a “we’ll get to it” topic into something that needs a clear decision.
For most organizations, that decision is the most current Umbraco release - version 17. Not just because it’s the latest release, but because it’s the next long-term support version. It gives teams a longer runway before they have to revisit this again.
At that point, the conversation usually expands. It becomes less about whether the site still works today and more about whether you want to manage the transition now, or later when other pressures force your hand.
Why upgrading to Umbraco 17 is the practical move
Most teams follow a consistent pattern with Umbraco. They move from one long-term support version to the next, skipping the short-term releases in between. It’s not that those versions lack value. They just don’t offer enough stability to justify the effort of upgrading.
That’s what makes the move from 13 to 17 the cleanest path. Versions 14 through 16 are short-term support. Adopting them often means facing another upgrade sooner than expected. Moving directly to 17 resets that cycle and gives you a longer support window.
There’s also a second layer that shows up over time. Your CMS doesn’t operate on its own. It sits at the center of a set of integrations that keeps evolving.
Commerce platforms, marketing tools, and search services move forward. At some point, a package you rely on drops support for your version of Umbraco or .NET, and what used to be a routine update turns into a workaround.
When that happens, the system doesn’t fail all at once. Things just get harder. Upgrades take longer, dependencies drift, and small issues become harder to track down. Staying on the latest LTS version is less about new features and more about keeping the system stable and predictable.
The Benefits of Umbraco 17
Upgrades are often framed around features, but the more meaningful changes show up in how teams work day to day.
One of the more noticeable shifts is how teams are starting to use AI inside the CMS. Umbraco 17 doesn’t lock you into a specific model or workflow, so teams can connect to tools like ChatGPT or Claude in ways that fit how they already work.
This usually doesn’t start with large, customer-facing features. It starts in the back office. Editors use AI to draft content, refine messaging, or generate metadata. From there, it expands as teams get more comfortable.
The back office is also easier to work with and extend. The move to web components and Lit changes how customization happens. Instead of working around the CMS, teams have clearer patterns for adding dashboards and widgets that reflect what they actually need.
Operational data like daily imports or content health can live inside the CMS instead of being tracked elsewhere.
These changes reduce friction during releases. You notice it over time. Teams spend less effort troubleshooting and more time moving work forward, which makes it easier to keep pace with changing needs.
There’s also a moment during most upgrades where teams take a closer look at their content and realize how much of it is outdated. That has always been true, but it matters more now.
If you’re introducing AI into your workflows, that content becomes part of what the system uses to generate outputs. Outdated or inaccurate information has a more direct impact.
The upgrade is a project. The real impact shows up afterward in how much easier it is to work inside the system.
The risks of not Upgrading to Umbraco 17
One of the reasons this decision gets delayed is that everything still appears to be working. The site is live, campaigns are running, and nothing is obviously broken.
The risk doesn’t show up all at once.
Once a version reaches end of life, security updates stop. Known vulnerabilities become easier to exploit because they’re documented and widely understood. Organizations in regulated environments may also find it harder to justify running unsupported software, even if nothing has gone wrong yet.
There’s a reputational risk as well. A compromised or defaced site isn’t just a technical issue. It’s visible to customers and stakeholders, and it raises questions about how the risk was allowed to persist.
What often gets underestimated is how the work changes over time. Waiting doesn’t just delay the upgrade. It adds complexity.
Teams introduce small fixes to keep things running. Dependencies drift. Customizations become harder to trace. By the time the upgrade happens, it’s no longer a clean move from one version to another. It’s an effort to untangle everything that has built up along the way.
The risk doesn’t show up as a single breaking point. It builds until the upgrade becomes more complex than it needs to be.
Determining your path: upgrade or rebuild
The scope of the move depends on where you’re starting.
If you’re on Umbraco 13, this is usually a structured upgrade rather than a full rebuild. You may need to adjust some deprecated features, such as macros or nested content, but the core of the site remains intact. Most teams treat this as a multi-month project, depending on complexity.
If you’re on Umbraco 8 or earlier, the situation changes. The move to .NET Core introduced a different architecture. Moving to version 17 typically means rebuilding the front end, even if the content is migrated.
In many cases, teams use this as an opportunity to revisit the experience more broadly, pairing the technical move with a redesign or updated UX.
Final thoughts
The cost of doing nothing is easy to overlook because nothing breaks all at once.
Things just get harder to maintain, less predictable to extend, and riskier to leave as they are.
Upgrading now lets you plan the work on your terms, instead of reacting later when the timeline is no longer yours to control.
Things just get harder to maintain, less predictable to extend, and riskier to leave as they are.
Upgrading now lets you plan the work on your terms, instead of reacting later when the timeline is no longer yours to control.
As Umbraco Platinum Partners, we at Diagram are well-equipped to help you navigate the decisions around upgrades, with a no-commitment, free consultation. You can schedule a call with us by clicking the "Schedule Here" button below.
