A platform reaching end-of-life is not only a technical calendar event. It is a business risk signal. When a CMS, framework, runtime or major dependency no longer receives support, security fixes or ecosystem attention, the system becomes harder to maintain and more expensive to change.
The right response is not always a full rebuild. But it should always start with a review.
Why end-of-life matters
Kruso’s Umbraco end-of-life article shows the practical issue clearly: when platform versions stop receiving support, organisations face security, compliance and operational risks. The same pattern applies beyond Umbraco. Unsupported software may continue to run, but the company loses the safety net around it.
Risks can include:
- missing security updates;
- unsupported dependencies;
- compatibility problems;
- weaker vendor or community support;
- blocked feature development;
- harder recruitment or handover;
- increasing operational uncertainty.
End-of-life does not mean “panic.” It means “stop guessing.”
Review the actual dependency chain
A platform upgrade is rarely just one upgrade. The application may depend on themes, plugins, custom modules, build tools, hosting assumptions, database versions, API integrations and deployment scripts.
A review should identify:
- core platform version;
- framework/runtime version;
- database dependencies;
- third-party plugins or packages;
- custom extensions;
- hosting environment;
- deployment process;
- test coverage;
- integrations;
- security-sensitive components.
This helps estimate whether the upgrade is routine, complex or a rebuild in disguise.
Understand what the business still needs
Before upgrading, ask whether the system still fits the business. A platform upgrade can be the right time to remove unused features, simplify workflows, improve accessibility, clean up data structures or move parts of the system into a better architecture.
Questions include:
- Which features are actually used?
- Which content, workflows or integrations are obsolete?
- Which parts are painful because the platform is old?
- Which parts are painful because the business process changed?
- Would a smaller upgrade solve the problem?
- Is a replacement product more suitable for some functions?
The goal is not to modernise everything. It is to modernise what matters.
Choose the right path
There are usually four options:
1. Patch and maintain temporarily
Useful when the business needs time, risk is understood and a larger decision is pending. This should be time-limited.
2. Upgrade in place
Appropriate when the current architecture is healthy and the platform offers a supported migration path.
3. Replatform selectively
Useful when parts of the system should move to a new foundation while preserving valuable workflows or data.
4. Rebuild or replace
Relevant when the current system no longer matches the business need or the old architecture blocks safe change.
Twoday’s application modernisation framing around different modernisation paths is useful here: there is no universal answer.
Do not ignore operation
An upgrade project should also improve operation where possible. NoA Ignite’s maintenance checklist for platform health is relevant: documentation, updates, logging, testing, rollback, backups, monitoring and security are not extras. They are what keep the upgraded system from becoming the next unmanaged risk.
Memory(One) perspective
A platform end-of-life event is a natural trigger for a Technical Review & Roadmap. The review should help the company decide whether to upgrade, replatform, rebuild, replace or maintain temporarily. The best outcome is not the newest version. It is a system the business can operate and change with more confidence.
Sources and inspiration
- Kruso — Time to future-proof your website: Umbraco 8 and 10 are nearing end-of-life: https://www.kruso.group/en-DK/updates/time-to-future-proof-your-website-umbraco-8-and-10-are-nearing-end-of-life
- NoA Ignite — Keep your Optimizely platform in top shape: https://noaignite.com/insights/keep-your-optimizely-platform-in-top-shape-with-these-maintenance-best-practices/
- NoA Ignite — Optimizely CMS 13 is here: https://noaignite.com/insights/optimizely-cms-13-is-here-what-to-adopt-and-when/
- Twoday — Modernization of applications: https://www.twoday.com/blog/modernization-of-applications