Now booking enterprise content platform builds for 2026. Contact us

01 Reference · CMS end-of-life

Is your CMS reaching end of life?

The major traditional content platforms all publish an end-of-support date, after which security fixes stop. Reaching it does not break your site the day it passes, but it turns a planned migration into an urgent one. Below is where the main platforms stand, taken from each vendor's own lifecycle page, with the migration guide for each next to it.

Last verified: 25 August 2026. Every date below links the vendor lifecycle page it came from, so you can check any single row at its source before planning around it.


02 End-of-life dates

When support ends for the major platforms.

Platform Support ends Status What the date marks Guide
Drupal 10 9 December 2026 Approaching End of life; no further releases after this date. Only the 10.6 branch carries security coverage until then. All versions and security branches Guide
Umbraco 13 (LTS) 14 December 2026 Approaching End of long-term support for the current LTS branch. Guide
Kentico Xperience 13 31 December 2026 Approaching Security hotfixes only through 2026; all support, including security repairs, ceases from 1 Jan 2027. Guide
Sitecore XP 10.0 & 10.1 31 December 2026 Approaching End of Extended Support; the Sustaining phase running to 31 Dec 2028 excludes security updates. Under the support model in force from 1 Jun 2026, Sitecore lists Extended Support security updates as chargeable. Guide
Adobe Experience Manager 6.5 (on-premise) February 2027 Approaching Adobe states core support for on-premise is currently planned to end by this date; a 6.5 LTS continuation covers both paths beyond it. Adobe Managed Services ends 31 Aug 2026. Guide
Joomla 5 12 October 2027 Approaching End of life for the 5.4 branch; bugfix support ends 13 Oct 2026. Earlier 5.x minors ended as each successor shipped, so only 5.4 is supported today. Guide
Sitecore XP 10.2 31 December 2027 Approaching End of Extended Support; mainstream ended 31 Dec 2024 and the Sustaining phase to 31 Dec 2029 excludes security updates. Under the support model in force from 1 Jun 2026, Sitecore lists Extended Support security updates as chargeable. Guide
TYPO3 v12 LTS 30 April 2026 Ended Free community support ended; paid ELTS adds three years, with a fourth for TYPO3 Partners. Guide
Optimizely CMS 11 No date published Unmaintained Outside the maintained majors (12 and 13) since the 10 Apr 2026 version policy. No published end-of-life date; no committed fixes beyond severe security vulnerabilities. Guide
Sitecore XP 9.3 31 December 2025 Ended End of Extended Support, and with it security coverage; earlier 9.x versions ended sooner. Sustaining runs to 31 Dec 2027 without security updates. Guide
Joomla 4 14 October 2025 Ended End of life. Bug fixes ran to 15 Oct 2024 and security fixes to 14 Oct 2025. Joomla 5.4 is the migration path. Guide
Umbraco 10 (LTS) 16 June 2025 Ended End of long-term support. Guide
Umbraco 8 24 February 2025 Ended End of life. Guide
Drupal 7 5 January 2025 Ended End of life after multiple extensions; no more security updates. All versions and security branches Guide
Drupal 9 1 November 2023 Ended End of life. All versions and security branches Guide

03 Platforms without a fixed date

WordPress, Webflow, Contentful, and Sitefinity don't share a single deadline.

Not every CMS sunsets a version on a calendar. WordPress backports security fixes across versions and has no hard end-of-life, so the reason to leave it is outgrowing it rather than a deadline. Hosted platforms like Webflow and Contentful run one continuously-updated service, so there is no version to reach end of life, though the questions of ownership and portability still apply. Progress Sitefinity runs a rolling lifecycle with long-term-support branches rather than one shared date; check your exact version against the Sitefinity lifecycle policy. For any of these, the decision is about fit, which we covered in five signs you've outgrown your CMS.


04 Platforms that shut down

LightCMS sent its shutdown date to customers by email, then the site itself went dark.

LightCMS is the platform still searched for by name. Its own site carried the announcement by June 2020: “we will no longer be offering the LightCMS Service and have announced its end of life” (archived notice). The shutdown date itself went to customers by email — a Last Date of Service of 31 May 2020, later revised to 31 October 2020 (preserved in third-party records). The site has since gone dark, so the announcement survives only in the Internet Archive. It has no row in the table above because every date there links a vendor page you can still check, and no such page exists for LightCMS: the emailed date survives only second-hand.

A retired hosted platform takes the admin, the export tooling and the content with it, so there is no version to upgrade to and no support tier to buy. Recovering a site in that state means rebuilding from whatever exists outside the platform: a crawl or archive of the public pages, local copies of assets, and whatever the team still holds. That is a different exercise from a migration off a running system, and it is worth reading vendor lock-in for how much of the exit cost gets fixed long before the shutdown notice arrives. Where content is still reachable, the pre-migration checklist covers what to capture first.


05 Sources

Every date is taken from the vendor's own lifecycle page.

On this list? Plan the move now

The earlier you scope the move, the more options you have on timing and budget. Book a 25-minute call and we'll tell you what it involves and whether it's worth doing yet.