Type: FAQ
Category: Umbraco Cloud > Versions & Upgrades
Tags: end-of-life, EOL, end-of-service, EOS, XLTS, extended support, LTS, STS, unsupported version, migration, rebuild, upgrade, dedicated hosting, security patches

Product: Umbraco CMS, Umbraco Cloud
Version: All versions

Every Umbraco version reaches End-of-Life (EOL) at some point. After that, it is no longer supported: sites on it still run, but they no longer receive security or compliance patches. On Umbraco Cloud, projects left on an End-of-Life version go through the End-of-Service (EOS) process, which ends with the project being taken offline. Moving to a supported version before then takes the project out of that process entirely.
​

Each Umbraco version is either a Long-term Support (LTS) version, supported for three years, or a Short-term Support (STS) version, supported for one year. When that time is up, the version reaches End-of-Life. On Umbraco Cloud, STS versions follow the End-of-Service dates of the LTS version before them.

After End-of-Life, a version gets no further releases: no security patches, no compliance fixes, and no technical support. For the End-of-Life dates of each version, see Long-term Support (LTS) and End-of-Life (EOL).
​

End-of-Service is the Umbraco Cloud process for projects left on a version that has reached End-of-Life. It starts when Extended Long-term Support (XLTS) is no longer available for that version, usually 24 months after its End-of-Life date. Until then, the project keeps running on shared hosting as before. After that, two stages follow, and you are notified before each one:

Moving to a supported version before End-of-Service takes the project out of the process. You can find the End-of-Service dates for each version in the End-of-Service Policy.

If you self-host rather than run on Umbraco Cloud, the End-of-Service process does not apply to you, but the End-of-Life dates above still do: an unsupported version stops receiving security patches wherever it runs.
​

If you need more time before moving to a supported version, Extended Long-term Support (XLTS) is a paid option that keeps security and compliance patches coming after a version has reached End-of-Life. It is available for Long-term Support (LTS) versions, and for Umbraco 7 and Umbraco 8. It is not available for Short-term Support (STS) versions, such as Umbraco 9.
​

XLTS gives you time to plan the move to a supported version on your own schedule, but it does not replace the move. Coverage runs for a limited period, usually up to 24 months after End-of-Life, and then ends. When XLTS is no longer available for your version, the End-of-Service process starts for Umbraco Cloud projects.
Because the coverage differs per version, check with the Umbraco team what XLTS would cover for your site and until when, before you build a plan around it. See Extended Long-term Support (XLTS).
​

The way forward is to upgrade or migrate to a version that is still supported. Aim for the current Long-term Support (LTS) version: it gives you the most time before your site reaches End-of-Life again. Do not aim for a version that has already reached End-of-Life, even if it is newer than the one you are on.

How much work this is depends on the version you are coming from, how much custom code and how many packages the site has, and its dependencies. Some moves are an upgrade, others are closer to a rebuild, so it is worth scoping early. The Upgrading and Migration documentation covers the paths for each version.
​

The right route depends on the site's size, how much custom code it has, and its dependencies. If you are on Umbraco Cloud, contact Umbraco and ask for an End-of-Service session, and we will help you map out the options. If you are already in a support conversation, ask to talk to a human agent.

Last updated on October 28, 2026