← Back to blog

Umbraco 13 support ends December 14, and the .NET 8 under it already ended: your options

AnuraCode

Flat drawing of colored blocks moving from an old, uneven layout into a clean grid on a new card

If your company website runs on Umbraco 13, two support dates now apply to it. On November 10, 2026, Microsoft ended support for .NET 8, the runtime Umbraco 13 is built on. On December 14, 2026, Umbraco 13 itself reaches end of life.

The site does not stop working on either date. What stops is the fixes: first for the runtime, then for the CMS. This post is for owners, marketing leads and IT leads of sites on Umbraco 13, often built by an agency that no longer looks after them. It covers what the two dates mean, the three paths you have, and what to ask before you choose one.

Two clocks, not one

The CMS. Umbraco 13 is a Long-term Support (LTS) release from December 14, 2023. Umbraco’s support and end-of-life page shows it in its security phase since December 14, 2025, a phase in which “only security issues are fixed.” After December 14, 2026, it is end of life. Umbraco’s Umbraco 13 XLTS page says what that means: “After this date, security patches and updates are no longer provided.”

The runtime. The Umbraco 13 requirements say: “as Umbraco version 13 is based on .NET 8 you will need to follow the .NET 8 supported versions.” Microsoft’s .NET support policy has listed .NET 8 as out of support since November 10, 2026, and it is direct about the risk: “Your use of out-of-support .NET versions may put your applications, application data, and computing environment at risk.” Our post on .NET 8 and .NET 9 end of support covers that date in detail.

So since November 10, Microsoft no longer provides fixes for the runtime under your site. From December 15, Umbraco no longer provides them for the CMS either, unless you pay for extended support.

First, find out what you run

Ask whoever has the site’s code two questions:

  • Which Umbraco version? The project uses the Umbraco.Cms package. A version that starts with 13 means Umbraco 13.
  • Which .NET version? The TargetFramework line in the project file says net8.0 for .NET 8.

If nobody can answer, that is the first problem to solve. Find out who holds the source code, the hosting account and an administrator login for the backoffice (Umbraco’s editing area). Every option below needs them.

Option 1: upgrade to Umbraco 17 on .NET 10

Umbraco 17 is the current LTS release. It came out on November 27, 2025 and reaches end of life on November 27, 2028. In Umbraco’s words, “The most recent LTS is Umbraco 17, supporting .NET 10 LTS,” and Microsoft supports .NET 10 until November 14, 2028. One upgrade resets both clocks for about two years.

Why not Umbraco 18? It is a Short-term Support release from June 2026, and Umbraco’s upgrade notes say it “can only upgrade from Umbraco 16.4 or later, because it no longer includes the migrations from Umbraco 13 to 17.” The way out of 13 goes through 17.

This is a large step, not a version bump. Umbraco 14 replaced the backoffice, and the same upgrade notes call that change “by far the most impactful update of Umbraco in years.” Between 13 and 17, Umbraco removed:

  • The AngularJS backoffice. Backoffice extensions written for it have to be rebuilt for the new extension model.
  • Nested Content and Grid Layout. Umbraco recommends blocks (Block List and Block Grid) instead of these two property editors.
  • Macros. Umbraco points to partial views or blocks in the rich text editor instead.

Every package the site uses also needs a version that works with Umbraco 17.

Umbraco’s blog post Going from Umbraco 13 to 17 (June 30, 2026) describes two ways to do it, and says “Both routes can work well”:

  • Upgrade the existing solution and “run the required migrations in the upgraded instance.” Umbraco sees this as the best fit for healthier, well-understood projects.
  • Start a fresh Umbraco 17 solution and move the content and schema with Umbraco Deploy import/export, which “transforms legacy content and schema during import.” Umbraco says this path can be “especially relevant” for sites with “older backoffice patterns, custom extensions, or legacy data structures.”

Ask before you choose this path:

  • Which custom extensions, packages, Nested Content or Grid Layout fields and macros does the site use, and what happens to each one?
  • Upgrade in place or fresh solution, and why?
  • Can the hosting run .NET 10? Umbraco 17 requires it.
  • Your editors will work in a new backoffice. Who shows them how?
  • Can it be live before December 14? If not, what covers the gap?

Option 2: Umbraco 13 XLTS as a bridge

Umbraco sells Extended Long-term Support (XLTS) for Umbraco 13. From its XLTS page:

  • “You can choose from a 6, 12, or 24 months XLTS coverage,” and coverage “begins the day after End-of-Life.”
  • Updates come through “a secure, private NuGet feed.”
  • The page describes it as security patches only, with a frozen feature set.
  • The page shows no prices. You order through a call with Umbraco; an agency that is an Umbraco partner can go through its partner manager.

XLTS buys time; it does not move the site forward. It fits when the upgrade cannot be live by December 14, or when a contract or regulation requires supported software in the meantime (the page mentions “regulatory and contractual obligations”).

The page leaves one question open: it says nothing about .NET, and Microsoft stopped providing fixes for .NET 8 on November 10. Do not assume XLTS covers the runtime; ask Umbraco.

Ask before you buy:

  • Does XLTS cover only the CMS, or also the Umbraco add-ons the site uses?
  • What happens with the .NET 8 runtime under the site?
  • What does 6 months cost compared with 12? Extensions “must be continuous, with no gaps allowed,” so plan the length with your launch date in mind.
  • Who on your side installs the updates from the private feed?

Option 3: rebuild

Sometimes the old site is not worth carrying forward: the agency is gone, nobody knows the custom code, and most of it would need rewriting for the new backoffice anyway. Then compare the upgrade estimate with a new build, on Umbraco 17 or on another platform.

Ask before you choose this path:

  • What must move: pages, media, forms and their entries, member accounts?
  • Which URLs must stay the same, and which need redirects?
  • Who maintains the new site after launch, and how does it get updates?
  • What runs until launch day: the old site as it is, or the old site with XLTS?

If you do nothing

The site keeps running. But it runs on a runtime Microsoft no longer fixes and, after December 14, on a CMS Umbraco no longer fixes. Microsoft’s support policy is plain: “You are strongly recommended to not use out-of-support software.” If you decide to wait anyway, write down who decided and until when, and install the latest Umbraco 13 and .NET 8 patches.

Checklist

  1. Confirm the Umbraco and .NET versions the site runs.
  2. Find who holds the code, the hosting account and a backoffice admin login.
  3. List custom extensions, packages, Nested Content and Grid Layout fields, and macros.
  4. Choose a path: Umbraco 17 (upgrade in place or fresh solution), XLTS as a bridge, or a rebuild.
  5. If the site will not be on Umbraco 17 by December 14, talk to Umbraco about XLTS now.
  6. Put the next dates in your calendar: November 14, 2028 (.NET 10) and November 27, 2028 (Umbraco 17).

If your site runs on Umbraco 13 and you want a second opinion on which path fits, get in touch.

Sources