Is HCL Domino Legacy IT? The UK Government's New Definition Says No
Under the UK government's new definition of legacy IT, HCL Domino is not legacy.
It passes all seven criteria the Government Digital Service (GDS) published on August 17, 2026 for the Legacy IT Risk Assessment Framework. The updated definition replaces every previous definition used across the framework, and it opens with a sentence worth reading twice:
"Legacy IT are systems whose continued use creates a persistent, unacceptable burden or risk and can no longer be supported or secured effectively or economically."
Then GDS spells out exactly what that does and doesn't mean:
"This definition is deliberately centred on burden or risk, rather than age, technology type, hosting model or whether a technology is unfashionable."
Age is out. Hosting model is out. Unfashionable is out, explicitly, in a government publication.
If you've spent the last decade being told your platform is legacy because it's old, this is the most useful paragraph HM Government has produced in years. It swaps an argument about vintage for an assessment you can evaluate on business terms.
Key Takeaways
- Risk-Based Classification: GDS's August 17, 2026 definition classifies legacy IT by burden and risk, explicitly not by age, technology type, or hosting model.
- Active Support Stream: HCL Domino is on an active release stream (14.5, 14.5.1, Fix Pack 1) with published support dates.
- Modern Front-Ends: Existing HCL Domino applications can gain web, mobile, and AI front-ends without re-platforming.
- Mainstream Skills: Developers do not need HCL Domino-specific skills; the platform supports standard JavaScript, React, REST APIs, and Node.js.
- Extended Support Runway: Extended Support for v9–v11 runs through June 2030 and is a bridge to upgrade, not a destination.
How the GDS Seven-Criteria Legacy Test Works
A system counts as legacy if it breaches the unacceptable threshold on any one of seven criteria. There's no scoring and no averaging; one breach is enough. You land on Accepted, Action-Required (legacy within 12 months), or Legacy (remediate as an urgent priority).
Therefore, let's put HCL Domino through it, one criterion at a time.
| GDS legacy criterion | Where HCL Domino sits |
|---|---|
| 1. Out of support: beyond OEM (original equipment manufacturer) support date. | It's on an active release stream. HCL Domino 14.5 shipped in June 2025, HCL Domino 2026 (14.5.1) on March 19, 2026, and Fix Pack 1 on July 16, 2026. Current versions carry published support dates, so this one passes. You can check where your release sits on the HCL Product Lifecycle page. |
| 2. Missing or inadequate contracts: lapsed licenses, no continuity path. | Current licensing, support and upgrade paths are available from HCLSoftware and our partners, on modern terms, and more than 90% of customers are already on modern HCL licenses. This is a contract question, not a platform question. Passes. |
| 3. Lack of required skills: too few people who can maintain it. | Modern HCL Domino architectures decouple application development from platform maintenance. Developers do not need HCL Domino-specific skills; the platform supports standard JavaScript, React, REST APIs, and Node.js. This allows organizations to recruit mainstream full-stack developers who interact with the platform's data via open interfaces. For platform management, HCL provides structured enablement paths and active community support, so succession planning relies on standard IT skill sets rather than niche expertise. Passes. |
| 4. Inability to meet user or business needs: cannot meet current or future requirements. | Business requirements fail when a platform limits integration, mobility, or security. That's not the case with HCL Domino, since it decouples backend business logic from the user interface, allowing organizations to deploy modern web, mobile, and PWA (progressive web app) front-ends while keeping underlying workflows and security intact. Passes. |
| 5. Unsuitable hardware: outdated, under-capacity, unrepairable. | Runs on current Windows and Linux, on-premises in your own data center or in the cloud, whether that's a hyperscaler such as AWS or Azure or a local provider such as IONOS. Passes. |
| 6. Failure to meet minimum cyber security standards: persistent exploitable weakness. | Actively maintained, with modern authentication and encryption built in and regular security fixes. That includes a plan for full Post-Quantum Cryptography (PQC) readiness well before 2030, and HCL Domino already supports next-generation standards such as ML-KEM ciphers (NIST's standardized post-quantum key encapsulation algorithm) and SHAKE-256 hashing (part of the NIST SHA-3 standard). Add modern authentication protocols like OIDC (OpenID Connect), TOTP (time-based one-time passwords) and passkeys, and this is a platform keeping pace with cybersecurity rather than falling behind it. Passes. |
| 7. Reliance on a legacy dependency: depends on something itself classified legacy. | A current release has no dependency on out-of-support components. Also, every release is pen-tested, and anything deprecated is flagged in the release notes and the HCL knowledge articles for HCL Domino. Passes. |
What HCL Domino Customers Actually Ask for When They Say “Modernize”
Since 14.5.1 is the current shipping version, if you're running HCL Domino v9, v10 or v11, these versions sit on Extended Support through June 2030, and Extended Support is a runway, not a destination: it's a paid arrangement to keep the lights on while you upgrade. If you are running Lotus Notes or IBM Domino, i.e., prior to HCL Domino v11, it's an upgrade opportunity, not a dead end.
Remember, unlike other solutions, upgrading the desktop client and server is straightforward; one of this enterprise collaboration platform core strengths is that proven business solutions keep running: upgrades have little or no impact on the custom-developed code, so they continue working unchanged. Desktop client and server updates are easy to do.
Meeting Modern Enterprise Requirements
- Criterion 4 is usually about applications, and what we hear from customers are requests to: Integrate an existing application with another enterprise process (e.g., a SaaS solution).
- Deliver the UI in a new form factor such as mobile or web.
- Utilize DevOps or SIEM (security information and event management) tools and cloud backup solutions.
- Add AI-based decisioning (or vibe coding).
On AI, HCL Domino IQ brings AI inference to your users and developers in the core of the platform, across all client experiences, without any of your data leaving your estate, so you don't need to re-platform at significant expense to get there.
That isn't a platform failing to meet current business needs. Those are incremental improvements that carry little risk, don't threaten business continuity, and are part of today's platform from HCLSoftware. You can measure the effort in days, not months or years.
The True Cost: Modernization vs. Rip-and-Replace
The alternative is to rip out the whole platform at considerable expense and real business risk, for little incremental value. If you need those applications documented, that's doable too.
Every platform accumulates technical debt if it is not upgraded, and every mainstream platform offers the same kind of incremental modernization described above to maintain the business value of its solutions for the foreseeable future.
The right conversation is about total cost of ownership (TCO): what it costs to keep proven applications running and modernized, versus what a rip-and-replace program costs in budget, risk, and lost time. Let's make that decision on the facts, not on a perception of age.
Frequently Asked Questions
1. Does the GDS definition apply outside the UK government?
GDS wrote it for the UK central government. Its value elsewhere is that it is vendor-neutral and measurable: seven criteria, one threshold each, and no averaging.
2. I'm still on HCL Domino v9, v10 or v11. Am I legacy?
Not under this definition. Those versions sit on Extended Support through June 2030, which is a paid runway to keep the lights on while you upgrade to the current release.
3. Will upgrading break my existing applications?
Upgrades have little or no impact on custom-developed code, so proven business solutions continue working unchanged after you update the desktop client and server.
4. Do I need specialist skills to modernize an HCL Domino application?
No. The platform supports standard JavaScript, React, REST APIs, and Node.js, so mainstream full-stack developers can work with HCL Domino data through open interfaces. In addition, our emerging Mosaic Vibe Coding for Domino makes this modernization a simple conversation for the application owner.
5. Can I add AI without data leaving my environment
Yes. HCL Domino IQ runs AI inference in the core of the platform, across all client experiences, without your data leaving your estate.
Ready to Modernize Your HCL Domino Environment?
Run your own HCL Domino estate through the seven criteria, then talk to the HCLSoftware team about the upgrade or modernization path that fits your business needs.
Start a Conversation with Us
We’re here to help you find the right solutions and support you in achieving your business goals.
