Upgrade on the same platform
Stay with your vendor and move to a supported version. This is usually the shortest path when the platform still fits your needs.
Guide
What CMS end of life means for your website
Your site keeps running the day support ends. What stops are the fixes. Here is what changes, what it puts at risk and how to plan the next step.
In short
End of life is the date a CMS vendor stops maintaining a version of its software. After that date, the vendor no longer ships fixes, including security fixes, for problems discovered later. The website still works, but every new vulnerability stays open until you upgrade or move to another platform.
How support winds down
Support rarely stops all at once
Most vendors reduce support in stages. The names change from one vendor to the next, but the pattern is the same.
01
Full support
The vendor fixes bugs, ships security patches and keeps the version compatible with new browsers, hosting and add-ons.
02
Security fixes only
Often called extended, limited or security support. Bugs stay unfixed and nothing new is added. Only security problems get patched. Some vendors charge for this phase.
03
End of life
No more patches of any kind. Newly found vulnerabilities stay open, and add-ons, hosting providers and integrations gradually stop supporting the version.
Dates to watch
Several popular versions reach their last support date by the end of 2027
Dates from each vendor's published support policy.
Check your exact versionEnd of vendor support
December 9, 2026
End of vendor support
December 14, 2026
End of vendor support
December 31, 2026
End of vendor support
December 31, 2026
Joomla 5
Joomla CMS versionsEnd of vendor support
October 12, 2027
What is at risk
Four risks that grow after end of life
Security
Vulnerabilities discovered after the end-of-life date are never patched by the vendor. They are often published, which makes unpatched sites easier targets.
Compliance
Security reviews, audits and client questionnaires often ask whether your software is still supported. An end-of-life CMS can be flagged as a finding you have to explain or fix.
Hosting and add-ons
An older CMS can tie you to older versions of .NET, PHP or databases, which have their own end dates. Modules and integrations also stop releasing updates for old versions.
Cost
Paid extended support, custom patches and workarounds add up. Each version you skip also makes the eventual upgrade bigger.
Your options
Three ways forward
Buy time with extended support
Some vendors sell extra support for older versions. It can cover the gap while you plan, but it postpones the upgrade rather than replacing it.
Move to another platform
If the upgrade is close to a rebuild anyway, it can be the right time to compare platforms and move your content, redirects and integrations.
How Sengo helps
A clear timeline, then a plan that fits your platform
We start from what you already have. We look at your version, modules, integrations and hosting, then show you when each support date hits and which path makes sense.
01
Stabilize
Secure the current platform so it keeps running while the next step is prepared.
02
Upgrade or migrate
Move to a supported version or a new platform in stages, with content, redirects, SEO and integrations planned.
03
Evolve
Keep the platform up to date so it does not become a problem again in a few years.
Frequently asked questions
Will my website stop working on the end-of-life date?
No. Your site keeps running. What stops is the vendor's maintenance: no more fixes for bugs or for security problems discovered after that date.
Can I keep running an end-of-life CMS?
Technically, yes. The risk grows over time as new vulnerabilities appear and as hosting, modules and integrations stop supporting the version. Most organizations use that time to plan an upgrade or a migration.
What is the difference between end of support and end of life?
Vendors use the terms differently. Often, end of full support means bug fixes stop while security fixes continue for a while. End of life usually means all fixes stop. Check your vendor's policy for the exact dates of each phase.
How do I find out which version I am running?
The version usually appears in your CMS admin area, often in an About or system information screen. Your developer or hosting provider can also confirm it.
When should I start planning?
As soon as you know your date. The time needed depends on the size of the site, the number of integrations and whether you upgrade or change platforms. A short assessment gives you a realistic timeline.