Most businesses still running HCL Domino believe it is close to free. You bought it years ago, it still works, and there is no obvious monthly invoice that makes you flinch when it lands. On paper, it looks like a settled, sunk cost that you can safely leave off the spreadsheet.
The problem is that the real cost of Domino rarely shows up as a single line item. It shows up as security exposure, slower work, downtime risk, and a growing dependence on a platform that fewer and fewer people can support. These costs are real money, but they are spread thin and disguised, which is exactly why they get missed.
This article is written for the finance-minded owner or operations leader who controls the budget and cares about risk and return, not about technology for its own sake. It breaks down where the money actually leaks, gives you a short self-scoring assessment to gauge your exposure, and explains how a modern setup turns an unpredictable liability into a predictable cost. The goal is not to alarm you. It is to help you see the numbers you are not currently counting.
"We already own it" is one of the most common reasons companies delay moving off HCL Domino. It feels financially responsible to keep using something you have already paid for, and nobody wants to spend money replacing a system that still turns on every morning.
But owning a platform is not the same as it being cheap to run. Think of a paid-off delivery van. The purchase is done, yet it still costs you fuel, servicing, insurance, and a driver who knows how to keep it on the road. As it ages, the repairs get more frequent, the parts get harder to find, and one day it lets you down on an important delivery. Nobody would call that van free.
Domino is the same. The purchase was the easy part and it happened long ago. The ongoing cost is in keeping it secure, supported, patched, and connected to everything else your business uses. Those costs are quietly real even when nobody is sending you a bill for them, and like the aging van, they tend to grow rather than shrink over time.
For a budget owner, it helps to see the cost in clear categories rather than as a vague sense of "old system, probably expensive somehow." Here is where the spend and the risk usually hide, and why each one matters financially.
Legacy platforms are harder to keep patched and harder to defend on cyber-insurance applications and client security reviews. That has a direct financial edge in two ways. First, a single security incident on an unsupported system can cost more than years of modernisation, once you add up downtime, recovery, lost data, and reputational damage. Second, insurers increasingly price coverage based on the systems you run, and unsupported software can raise your premiums or narrow what you are covered for.
Outdated interfaces, manual workarounds, and processes designed for a different era mean staff spend time fighting the system instead of doing the work. If a handful of people each lose even twenty or thirty minutes a day to clunky steps and re-keying, that adds up to a meaningful salary cost across a year. It is invisible because it never appears as an expense, but you are paying it in wages regardless.
The pool of people who genuinely understand HCL Domino keeps getting smaller as specialists retire and new engineers never learn it. Scarce skills cost more per hour and are slower to find, and reactive break-fix help is at its most expensive precisely when you need it most, in the middle of an outage. You are exposed to a supplier market that is moving against you.
When Domino does not connect cleanly to the other tools you rely on, teams paper over the gaps with duplicate data entry, spreadsheets, and shadow processes. Every one-off HCL Domino integration script that someone built years ago is a maintenance liability with no clear owner, and every manual bridge between systems is both a labour cost and a source of errors. The friction is constant and it compounds.
Depending on your exact version and setup, there are still licensing, hosting, hardware, and maintenance costs to keep the environment alive. These do not disappear because the software is old. In many cases they quietly rise as hardware ages and specialist support becomes harder to source.
Individually, none of these is dramatic enough to force a decision. Together, they are a steady drain that most businesses never add up into a single number, which is exactly the problem.
If you take one thing from this article, make it this. The largest cost of staying on Domino is not any of the categories above. It is continuity risk, the possibility that the system your business depends on goes down and cannot be brought back quickly.
If Domino still supports your email, approvals, documents, databases, or internal processes, then the entire operation depends on it staying up and on someone being able to fix it when it does not. In many firms, that "someone" is one or two individuals. When they are unavailable, or when they leave, a routine issue can escalate into a business problem within hours.
Put a rough number on it for your own business. If your core systems were down for a full day, what would that cost in lost billable time, missed deadlines, idle staff, and unhappy customers? For most SMBs the figure is uncomfortably large, and it dwarfs the cost of the modernisation that would have prevented it. That is the exposure that does not fit neatly on a spreadsheet but can outweigh every other cost in a single bad week.
Want a clear number instead of a guess? Contact Cortavo for a cost and risk review.
This pattern shows up most often in firms with roughly 10 to 50 staff in document-heavy fields such as legal, manufacturing, accountancy, and professional services. The system works, so it gets left alone. Over time the hidden drag builds. Manual workarounds become the normal way of doing things, processes calcify around old software, and the business leans harder on a platform that fewer people can support.
It is not a sign of poor management. It is simply what happens when a system quietly does its job for long enough that nobody has a pressing reason to look at it. The danger is that "it works" and "it is a good financial decision" are not the same statement, and the gap between them widens every year.
Give your business one point for each statement below that is true. It takes about two minutes and gives you a rough but honest read on your exposure.
The value of the exercise is not the exact score. It is that it turns a vague feeling into something concrete enough to act on.
|
Score |
Exposure Level |
What It Means |
Recommended Action |
|
0 to 2 |
Lower exposure |
Hidden costs are modest for now. |
Confirm your version and support status, maintain proper backups, and review again in one year. |
|
3 to 5 |
Moderate exposure |
Hidden costs are likely increasing, and continuity risk is real. |
Start assessing your options before a forced decision arrives on someone else’s timetable. |
|
6 or more |
High exposure |
Continuity and security risks are material, and the impact on the business is likely significant. |
Add this to your near-term planning list rather than delaying it until next year. |
Not every business needs to migrate immediately, and it is fair to weigh the cost options. Broadly there are three financial paths.
You can optimize in place, tightening up support, documentation, and security around your existing setup. This is the lowest upfront spend, but it does not remove the underlying continuity and talent risk. It buys time rather than solving the problem, which can be the right call if a full move is not feasible this year.
You can upgrade to a supported version, which reduces immediate security exposure but keeps you inside the same shrinking ecosystem, with the same long-term talent and dependency questions.
Or you can migrate to a modern platform, which carries the highest upfront cost but resolves the underlying risk and, crucially, makes your ongoing costs predictable. For most firms the honest comparison is not "cheap old system versus expensive new one." It is an unpredictable old system with a rising, hidden cost versus a modern one with a known, budgetable cost. Once the hidden costs are counted, migration often wins on total cost of ownership as well as on risk.
The reason a modern setup usually wins financially is not just newer features. It is predictability, which is something finance leaders value for good reason.
A migration to Microsoft 365 or Google Workspace, paired with ongoing managed IT support, converts a lumpy, unpredictable risk into a clear monthly cost. Instead of hoping the old system keeps running and absorbing surprise expenses when it does not, you get a supported environment with defined security, defined support, and someone accountable for keeping it working. Patching, backups, and monitoring happen as a matter of routine rather than as an emergency. The key-person risk is replaced by a documented service.
For most finance leaders, trading an unknown and growing downside for a known operating cost is an easy trade once the real exposure is visible. The hard part is simply seeing the exposure in the first place, which is what this assessment is designed to help with.
If you want an outside read on what your current setup is really costing you, contact Cortavo for a scoped cost and risk assessment.
There is no single sticker price, which is exactly why it is so easy to underestimate. Beyond any remaining licensing, hosting, or hardware, the real cost is spread across security exposure, staff time lost to slow workflows and manual workarounds, the rising price of scarce HCL Domino support, and the continuity risk of depending on a platform few people can maintain. The honest answer is that most businesses are spending more than they think, just not in a form that shows up as one obvious invoice. A scoped assessment that adds these together usually produces a number that surprises people.
It can be, and the risk grows over time. Older platforms are harder to keep patched and harder to defend on security reviews and cyber-insurance applications, and attackers actively look for unsupported software. The severity depends on your version, how exposed the system is to the internet, and how well it is currently managed. The key point for a budget owner is that an unsupported or poorly maintained environment turns security from a manageable line item into an unpredictable liability that can arrive all at once.
The hidden costs are the ones that never appear as a purchase. They include time lost to clunky workflows, duplicate data entry caused by weak integrations, expensive reactive support, the fragility of depending on one or two key people, and the potential cost of downtime or a security incident. There is also an opportunity cost, since money and attention tied up in maintaining old systems cannot be spent on growth. Because none of these is a clean monthly bill, they tend to be excluded from the "it is basically free" mental math.
Staying looks cheaper only if you count the original purchase and ignore the ongoing drag and risk. Once you include support costs, lost productivity, security exposure, and continuity risk, migrating to a modern platform with managed IT often works out lower in total cost, and it is almost always more predictable. The right answer for your business depends on your size, how much still lives inside Domino, and your appetite for risk, which is precisely what a scoped assessment is designed to clarify with real numbers rather than assumptions.
If a full move is not realistic right now, the priority is to reduce the risk you can reduce cheaply. Make sure the environment is properly backed up and that you have tested restoring it. Write down how the critical parts work so you are not wholly dependent on one person's memory. Tighten security around access, and confirm your version and support status. This does not remove the underlying issue, but it lowers your exposure and buys you time to plan a migration on your own schedule rather than in a crisis.