When your custom software becomes a legacy problem
Legacy software is not always a rebuild job. We take a look at when to maintain your custom system affordably, and when an upgrade due to vendor end-of-life becomes essential.
We built a custom system for a client 11 years ago. Over time, it quietly became the exact problem it was built to solve. That is more common than most business owners realise, and a meaningful share of IT spend in South African businesses now goes into keeping ageing, bespoke systems on life support rather than moving the business forward.
The good news is that a legacy system does not automatically mean an expensive rebuild. Often the smart move is to maintain what you already have. But there is a point where maintenance is no longer enough, and knowing the difference can save you a great deal of money and risk.
Software ages with your business, not with the calendar
A distribution business came to us this year with a familiar problem. Quoting a single job meant three people, two spreadsheets and half a day. Branch pricing, reseller pricing and stock levels had all been bolted onto a system originally built for a company a third of its current size.
Nobody had done anything wrong. The business had simply outgrown its software years before anyone noticed. That is how legacy systems are born. Not from bad code, but from a business that keeps changing while its software stands still.
Maintenance is often the affordable answer
A full rebuild is not the automatic answer, and it is rarely the cheapest one. In many cases we can keep legacy software running well for years at a modest cost. Targeted fixes, small enhancements and keeping the underlying parts healthy get far more life out of a system than most people expect. If your software still does the job, and the technology underneath it is still supported, maintaining it is usually the sensible choice. We are happy to do exactly that.
The one thing maintenance cannot fix
There is a hard limit, and it is not set by us. Every system sits on a stack of underlying technology, such as an operating system, a database and a development framework. Suppliers like Microsoft support these for a set period, and then that support ends. Once a platform reaches end of life, the vendor stops releasing security patches.
That is the moment when “leave it alone, it still works” becomes a real risk. An unsupported system is not just slower or clunkier, it is a security exposure. Known vulnerabilities stay open, which is exactly the kind of gap that leads to breaches, downtime and compliance problems under POPIA. When your platform hits end of life, upgrading stops being optional housekeeping and becomes a matter of protecting the business.
Netgen can maintain or rebuild your legacy software
Custom software is not a once-off purchase. It has to keep changing shape as your business does, or it slowly becomes the legacy problem you paid to avoid. We build, maintain and rescue business systems from Cape Town and Johannesburg, working across a broad technology stack that spans .NET, C#, Angular, React, PHP and Python, so we can support and modernise systems on almost any platform. Whether the right answer is maintaining your existing custom software or a full software rescue and rebuild, we will give you a straight assessment of what your business actually needs. If your system has not changed in five years, or you are not sure whether it is still supported, speak to our team for a second opinion.
