Umbraco 13 reaches end of life on 14 December 2026. After that date Umbraco stops releasing security patches for it. Your site will keep running, but every new vulnerability stays open. You have three real options: upgrade to Umbraco 17, pay for extended support to buy time, or move to another platform. This guide explains each one so you can pick the right one for your business, including when staying on Umbraco is the right answer.
We are a Webflow agency, not an Umbraco agency. We have no Umbraco upgrade to sell you, so you can weigh this guide against the advice of the agencies that do.
What Happens on 14 December 2026
Umbraco gives each Long Term Support (LTS) version two phases. In the support phase it fixes bugs and security issues. In the security phase it fixes security issues only. Umbraco 13 left its support phase on 14 December 2025, so bug fixes have already stopped. On 14 December 2026 the security phase ends too.
Umbraco's own advice is not to run 13 after end of life. Sites "will technically continue to function", but you are on your own when something breaks or a vulnerability is published.
Which Umbraco Version Are You On?
Umbraco 13 is not the only version at risk. Most older versions are already past end of life. If you are not sure which version you run, your developer or hosting provider can confirm it in a few minutes.
- Umbraco 7 (LTS): end of life 30 Sep 2023. Unsupported for over 3 years.
- Umbraco 8 (LTS): end of life 24 Feb 2025. Unsupported.
- Umbraco 9, 11, 12 (Short term): end of life 2022 to 2024. Unsupported.
- Umbraco 10 (LTS): end of life 16 Jun 2025. Unsupported.
- Umbraco 13 (LTS): end of life 14 Dec 2026. Security patches stop on this date.
- Umbraco 14, 15, 16 (Short term): end of life 2025 to 2026. Unsupported.
- Umbraco 17 (LTS): end of life 27 Nov 2028. Supported (bug fixes until 27 Nov 2027).
- Umbraco 18 (Short term): end of life 25 Jun 2027. Supported.
Umbraco 19, a short term release, is due on 10 December 2026. For most businesses on 13, the realistic target is 17, the current LTS version.
If you are on 7, 8 or 10, you have been without security patches for some time. The decision below applies to you too, and there is less reason to wait.
What Upgrading From 13 to 17 Involves
Moving from 13 to 17 is more than a version bump. Two big changes sit between them.
- A new backoffice. Umbraco 14 replaced the old AngularJS backoffice with a new one built on web components and Lit. Umbraco calls it "the most impactful update of Umbraco in years". Any custom property editors, dashboards or backoffice extensions built for 13 have to be rebuilt.
- A new version of .NET. Umbraco 13 runs on .NET 8. Umbraco 17 runs on .NET 10, so your code and hosting have to move as well.
Other changes in the same jump include new API endpoints for the backoffice and the removal of some older content types and bundling tools. Packages you rely on also need versions that support 17.
Umbraco describes two routes. You can upgrade in place and run the migrations, or build a fresh Umbraco 17 site and move your content across. Umbraco itself says the second route is "especially relevant" for sites with custom extensions or legacy data structures. In other words, for many sites the upgrade is close to a rebuild. That is what makes it worth asking whether to rebuild on Umbraco or somewhere else.
Extended Support: Paying to Wait
Umbraco HQ sells Extended Long Term Support (XLTS) for version 13. It covers security patches only, for 6, 12 or 24 months from the day after end of life. There are no new features and no bug fixes, and no code changes are needed on your side. Umbraco does not publish the price; you request a quote.
XLTS is a sensible choice when you need time. For example, if you are mid way through a bigger change or waiting for next year's budget. It is a recurring cost to keep a version alive, not a solution, so set a date by which you will decide what comes next.
When Staying on Umbraco Is the Right Answer
Upgrading to Umbraco 17 is the right choice for a lot of businesses. It usually is if:
- Your site is deeply connected to other systems such as an ERP, a CRM, a member portal or custom booking logic built in .NET.
- You have your own .NET developers, or a long term Umbraco partner who knows your code.
- You need to host on your own infrastructure, for example inside your own Azure tenancy for security or procurement reasons. Umbraco can do this. Hosted platforms such as Webflow cannot.
- Your site is an application, not just a website, with logged in users, complex permissions or heavy custom functionality.
- Your editors are happy with how they work today and the site does what the business needs.
If most of these are true, upgrade to 17. Talk to an experienced Umbraco partner, budget for the backoffice changes, and use XLTS if you need more time.
When Moving Platform Is the Right Answer
Moving makes sense when the website is mainly a marketing site and the upgrade cost buys you very little. It usually is if:
- The site is for marketing: services, case studies, news, team pages and enquiry forms.
- Your marketing team waits for developers to change a page, add a landing page or update content.
- You do not have .NET developers, and finding or paying for Umbraco developers is a struggle.
- The site needs a redesign anyway, so you would be paying to upgrade a site you plan to replace.
- Hosting, patching and upgrades take time and money that you would rather put into the site itself.
In that case a hosted platform such as Webflow removes the upgrade cycle. Hosting, security and updates are managed for you, and your team edits pages and CMS content without a developer. If you choose to move, you pay for a rebuild once rather than again at the next end of life.
What Moving Costs, and How You Keep Your Rankings
A move is a website project. The cost depends on the number of templates, the amount of content, any integrations and whether you redesign at the same time. We price each project after a short scoping call, not from a rate card.
The risk most businesses worry about is losing search traffic. That risk is managed with a clear process:
- Record every URL that ranks or has links pointing to it, from Search Console, your sitemap and web archives.
- Map each old URL to its new page with a 301 redirect, and keep the same URL where you can.
- Carry over titles, descriptions and structured data, and keep the content that ranks.
- Rebuild forms and integrations (CRM, analytics, consent) before launch, and test them.
- Check Search Console after launch and fix any pages that drop out.
Rankings are lost through skipped redirects and missing content, so the redirect map is the part of the project to get right.
Common Questions
When does Umbraco 13 reach end of life?
On 14 December 2026. Umbraco stops releasing security patches for version 13 on that date. Bug fixes already stopped on 14 December 2025, when 13 moved from its support phase into its security phase. Your site will keep working after the date, but new vulnerabilities will not be fixed.
Can I upgrade straight from Umbraco 13 to 17?
Umbraco treats 17 as the next LTS target for sites on 13, and its guidance covers going from 13 to 17. The jump crosses the new backoffice introduced in version 14 and moves from .NET 8 to .NET 10, so custom backoffice code has to be rebuilt. Umbraco also suggests a fresh 17 build for sites with legacy data structures.
What is Umbraco XLTS and how much does it cost?
XLTS is Extended Long Term Support sold by Umbraco HQ. It keeps security patches coming for 6, 12 or 24 months after end of life, with no new features or bug fixes. Umbraco does not publish a price, so you need to request a quote. Treat it as time to decide, not a permanent answer.
Is it safe to keep running Umbraco 13 after December 2026?
The site will still load, but no new security issues will be patched. The risk grows over time as vulnerabilities are found in Umbraco, .NET 8 and the packages you use. If your site handles logins, payments or personal data, plan your upgrade or move before the deadline, or cover the gap with XLTS.
Should we upgrade to Umbraco 17 or move to Webflow?
Upgrade if your site is deeply integrated, you have .NET developers or you must host on your own infrastructure. Move if the site is mainly for marketing, your team waits on developers for changes, or it needs a redesign anyway. Either way the work is a project, so compare the two costs side by side.
Will moving from Umbraco hurt our Google rankings?
Not if the move is planned. Record every URL that ranks or has links, redirect each one to its new page, carry over titles and descriptions, and check Search Console after launch, fixing any page that drops out. Problems come from skipped redirects and lost content, not from the platform change itself.
How long does a move take?
A typical marketing site takes six to eight weeks from discovery to launch. Larger sites with many templates, a lot of content or integrations take longer. If 14 December is close, extended support can cover the gap so you are not forced to launch in a hurry.
We are on Umbraco 8 or 10. Does this apply to us?
Yes, more urgently. Umbraco 8 reached end of life in February 2025 and 10 in June 2025, so neither gets security patches today. Going from 8 to 17 is a full rebuild in practice, which makes it a good point to compare upgrading with moving platform.
Need a Second Opinion?
If you are deciding between upgrading and moving, we will look at your site and tell you which route we would take, including when the answer is to stay on Umbraco. Get in touch or use the Project Planner.
.avif)
