Legacy software: when to modernize, and when to leave it alone
Custom Software · 5 min read
Legacy software: when to modernize, and when to leave it alone
Every established business has one: the old system. Written years ago, understood by one person, powering something important. Vendors love to say it “needs modernizing” — usually right before quoting a rewrite. The truth is more useful: some legacy systems genuinely need replacing, some need a careful renovation, and some are best left exactly where they are. Here’s how to tell which one you own.
Leave it alone when it’s quietly winning
Old is not the same as broken. If the system is stable, does its one job well, changes rarely, and the platform still receives security updates — the boring move is the right one. “It’s not modern” is an aesthetic complaint, not a business case. Spend the money where a problem actually lives.
Modernize around it when the core is sound
The most underrated option is the middle one: keep the reliable core and build modern pieces around it. A web portal in front of an old database. An integration that frees its data for other systems. A new module for the workflow that changed, while untouched workflows stay untouched. This is renovation instead of demolition — a fraction of a rewrite’s cost and risk, and often it buys the old system another productive decade.
Replace it when the ground is shifting
The genuine replacement signals: the platform no longer gets security patches; the one person who understands it is retiring; every business change takes months because nobody dares touch the code; or the system actively blocks what the business needs next. When those stack up, a rewrite stops being vanity and becomes maintenance — and it should be done the way any build should: discovery first, data migrated like a release, and the old system retired module by module, not in one heroic weekend.
Three honest questions: Is it still safe to run? Can anyone maintain it? Does it block what the business needs next? Three good answers — leave it. One bad one — renovate around it. All three bad — replace, carefully.
Beware the rewrite reflex
Developers (yes, us included) are drawn to clean slates; businesses are better served by working software. When we assess a legacy system, the deliverable is a recommendation with the trade-offs and prices attached — including, regularly, “keep it, and here’s the small thing to fix.” A vendor whose every assessment ends in a rewrite isn’t assessing; they’re selling.