Fem månader kvar att uppgradera
Umbraco 13 når End of Life den 14 december 2026. Den underliggande plattformen .NET 8 når slutet av Microsofts support ännu tidigare, den 10 november 2026.
Er webbplats kommer inte plötsligt att sluta fungera när dessa datum passerar. Däremot upphör ordinarie säkerhetsuppdateringar och support, vilket gör lösningen allt svårare och mer riskfylld att underhålla.
Organisationer som använder Umbraco 13 bör därför utvärdera sina uppgraderingsalternativ i god tid före slutdatumen, i stället för att vänta tills ett säkerhetsproblem eller en förändring i driftmiljön tvingar fram en akut migrering.
What does end of life mean?
Once Umbraco 13 reaches end of life, it will no longer receive standard updates, technical support, or critical security patches from Umbraco.
The website may continue operating, but over time you may face:
Unpatched security vulnerabilities
Compatibility problems with hosting and integrations
Packages that no longer support the version
Increased maintenance and upgrade costs
Concerns during security reviews and supplier assessments
End of life does not mean immediate failure. It means the safety net has been removed.
Why should you begin planning now?
An Umbraco upgrade is rarely completed by changing a version number.
Custom code, packages, integrations, Forms, search functionality, backoffice extensions, deployment pipelines, and hosting environments must all be reviewed and tested.
Starting early gives you time to:
Identify incompatible or abandoned packages
Review custom functionality and integrations
Decide whether to upgrade or rebuild
Test content, forms, search, and redirects
Check SEO, performance, and accessibility
Prepare a safe deployment and rollback plan
A planned upgrade is usually cheaper and safer than an emergency migration performed after support has already ended.
Could this affect GDPR or NIS2 compliance?
Using Umbraco 13 after end of life is not automatically unlawful.
However, GDPR requires organizations processing personal data to maintain security measures appropriate to the risk. Once security patches are no longer available, it may become harder to demonstrate that an application is being maintained appropriately.
NIS2 may also be relevant to organizations operating in critical sectors such as healthcare, energy, transportation, finance, digital infrastructure, and public administration.
Organizations covered by NIS2 must manage risks involving vulnerability handling, system maintenance, incident response, and supplier security. An unsupported CMS can therefore create an avoidable issue in security and supplier assessments.
Financial organizations may also need to consider DORA, which places additional emphasis on ICT risk, legacy systems, and vendor-support end dates.
These regulations do not specifically require an Umbraco upgrade. The concern is whether continuing to run unsupported software creates an unmanaged or insufficiently documented risk.
Should you upgrade to Umbraco 17?
For most organizations remaining with Umbraco, Umbraco 17 LTS is the natural target.
Umbraco supports an LTS-to-LTS upgrade path from Umbraco 13 to Umbraco 17. However, packages, custom code, integrations, and backoffice extensions may still require significant work.
There are generally two approaches:
Upgrade the existing solution
This may be appropriate when the current implementation is well structured, packages remain supported, and technical debt is limited.
Build a clean Umbraco 17 solution
A fresh implementation may be preferable when the existing project contains outdated architecture, unsupported packages, extensive customization, or significant technical debt.
The correct approach depends on the condition and complexity of the current website.
What if you cannot upgrade before December?
Umbraco offers Extended Long-Term Support, known as XLTS, for Umbraco 13.
XLTS provides additional access to critical security patches after the standard support period ends. It can be useful when an organization needs more time to complete a safe migration.
However, XLTS should generally be treated as a temporary bridge, not a permanent alternative to upgrading.
Start with an Umbraco 13 assessment
An upgrade assessment should identify:
Packages and dependencies that require replacement
Custom code and integrations that need updating
Backoffice extensions that must be rebuilt
Hosting and deployment changes
Security, SEO, accessibility, and performance risks
Whether an upgrade or clean rebuild is the better option
The expected scope, timeline, and cost
Planning now gives you control over the process. Waiting until the deadlines approach means competing for development capacity, compressing testing, and increasing the risk of running unsupported software.
Plan your Umbraco 13 upgrade
I have worked with Umbraco since version 4 and help organizations assess, upgrade, and modernize complex Umbraco solutions.
Get a clear understanding of your current implementation, technical risks, upgrade options, and recommended next steps before support ends.