What it really costs to keep old software running

Every quote to replace an old application comes with a number on it, and it's usually a big one. The other option, leaving things alone for another year, doesn't come with a number at all. That's a big part of why so many businesses hang on to systems long after it stopped making sense. One choice has a price tag, and the other just has consequences nobody totals up.

So it's worth putting a rough number on doing nothing.

The time your team spends working around it

Start here, because it's the easiest cost to see and to measure. Every time your team works around something the software can't do, you're paying for it in wages, week after week. Someone exports data into a spreadsheet, someone else re-types it into another system, and somebody builds the same report by hand every Monday.

Pick the three biggest workarounds and ask the people who do them how long each one takes. Multiply that by their full hourly cost (wages plus benefits and overhead) and then by 52. Most businesses are surprised by the result, and it's usually the smallest of the costs in this post.

The security risk

Once software is out of support, the maker stops sending security fixes. That's what "unsupported" means. Any weakness discovered after that date stays open on your systems for good, and the only protection left is more workarounds: walling the old system off from the rest of your network, limiting who can get to it, and extra safeguards that someone has to keep looking after.

Because this risk may never turn into an incident, it's easy to brush aside. Two things make it more concrete. Cyber insurance renewal forms increasingly ask whether you run unsupported software, and your answer affects both the premium and what's covered. And if you have any compliance requirements at all, an unsupported system tends to come up as a finding in every audit until you deal with it.

The cost of connecting it to anything else

Old systems are expensive to hook up to newer ones. They were built before most software was designed to share information easily, so every connection ends up as a one-off job. It might be a file dropped in a folder overnight, a direct read from the database that nobody feels great about, or a script that runs at 2am and fails without telling anyone.

Building those connections costs money, and each one also makes every later change more expensive, because now there are five fragile links that all have to keep working. This cost keeps growing, which is why replacing an old system gets harder the longer you put it off.

The one person who understands it

There's usually one person who really knows the old system. Sometimes they wrote it, and sometimes they've simply been there longer than everyone who did. Either way, the business depends on knowledge that lives in their head and nowhere else.

It's hard to put a clean dollar figure on that, but you can ask yourself a useful question. If that person gave notice tomorrow, what would the next ninety days look like, and what would you spend getting through them? Whatever the honest answer is, you're carrying that risk today.

What you can't do because of it

This last cost is the hardest to see, because it never shows up as a bill. It's the customer portal you can't offer, the automation you can't add, and the reports your leadership team keeps asking for, all held up because the system at the center of the business can't support them.

Competitors who aren't stuck with the same limits are offering those things. You pay for that in lost ground in your market, and you won't find it on any invoice.

Adding it up

Take the workaround hours, the insurance and audit headaches, the upkeep on the old system and all its connections, and a fair estimate of what losing your one expert would cost. Compare that yearly figure with the cost of replacing the system, spread over the number of years the replacement will last.

For a small tool, the math often comes out in favor of keeping it, and if that's the case we'll tell you. For a system the whole business runs on, the cost of doing nothing is usually higher than anyone expected, and you pay it every year, while the replacement is paid for once.

When keeping it is the right call

To be fair to the old system, sometimes leaving it alone is the right answer. If it's stable, cut off from the internet, not stopping you from doing anything you want to do, and understood by more than one person, it isn't costing you much. Stability is worth something, and replacing software that works just for the sake of it is an easy way to waste money.

So the age of the software matters less than two plain questions. Is it holding you back, and how much are you paying each year to work around it?