Umbraco 13 XLTS vs upgrading: what each actually costs
Umbraco sells extended support for version 13 in 6, 12, or 24-month blocks - but does not publish the price. Here is the full cost of each route: the XLTS fee structure and what it quietly excludes, versus what an upgrade to 17 actually involves.
What XLTS actually is
Extended Long-Term Support is Umbraco HQ’s paid bridge past end of life. For Umbraco 13, coverage starts December 15, 2026 – the day after EOL – and you buy it in 6, 12, or 24-month blocks. Coverage must be continuous with no gaps, patches arrive through a private NuGet feed, and you get critical security patches only: no bug fixes, no features, a frozen platform. The details are on Umbraco’s XLTS page.
Notice what is not on that page: a price. XLTS is sold through a sales call, or through your Umbraco partner. That is worth pausing on, because the first cost of XLTS is that you cannot budget it from public information.
The real cost of the XLTS route
The fee is only the visible part. Count all four costs before choosing this branch.
- The fee itself – recurring, per period, negotiated. If coverage must run 12 or 24 months because your upgrade planning has not started, the total climbs accordingly.
- The runtime problem XLTS does not solve. Umbraco 13 runs on .NET 8, and Microsoft ends .NET 8 support on November 10, 2026. Umbraco can patch Umbraco; it cannot patch Microsoft’s runtime. With XLTS you are paying for a patched CMS on an unpatched foundation.
- Ecosystem drift. Package authors follow current versions. Every month on a frozen platform widens the gap your eventual upgrade has to cross – which makes that upgrade more expensive, not less.
- The upgrade you still owe. XLTS removes nothing from the roadmap. At the end of the coverage period, the full upgrade cost is still waiting – now with a larger version jump and more drift behind it.
The real cost of the upgrade route
An upgrade from 13 to 17 is a one-time project, and its size is driven almost entirely by your custom code: backoffice extensions, packages, and integrations. Content and document types usually migrate cleanly. From my project experience, a standard site with well-maintained custom code lands at a few weeks including testing; heavily customized solutions take meaningfully longer, which is exactly what a compatibility review exists to find out before anyone commits to a number.
The upgrade also buys things XLTS never will: .NET 10 under your site with support into late 2028, current packages, and access to features and performance work instead of a frozen platform.
When XLTS genuinely wins
XLTS is the right call in three situations: the budget is formally frozen and cannot be unfrozen this year; the site is scheduled for decommissioning or replatforming and needs a secure runway; or the estate is so complex that a properly planned migration simply cannot land before December. In each case, buy the shortest block that covers the plan – with a written upgrade date attached.
For everything else, my position is blunt: XLTS is renting time at a negotiated price to defer a cost that only grows. If the money for two XLTS periods exists, the money for the upgrade exists – and one of those purchases you only make once.
Deciding with evidence instead of a sales call
The full picture of your options – risks, timelines, and the rebuild alternative – is on the Umbraco 13 end-of-life page. If you want the comparison made concrete for your site, a short migration assessment reviews your custom code, packages and infrastructure and gives you a written scope with approach, risks and timeline – a real number to hold against the XLTS quote. Book it here.