Software Planning 8 min read

When to Rebuild an Old System and When to Keep It

The signals that tell you whether patching or replacing your old software is the right call, with a practical assessment framework.

Best for: IT leaders, operations managers Practical guide for business decision-makers

Who this is for

IT leaders and operations managers dealing with ageing software they're not sure is worth keeping.

Question this answers

Should I invest in fixing our old system or is it time to start planning a replacement?

What you'll leave with

  • Clear signals that a system needs replacing vs repairing
  • How to assess your system's true maintenance cost
  • A practical audit framework you can run yourself

The signals

Old software isn't automatically bad. Some systems built 15 years ago still work beautifully because they were well-designed and the requirements haven't changed much. Age alone isn't a reason to rebuild.

The question is whether the system is helping or hindering your business.

Warning signs that suggest replacement:

  • Maintenance costs are rising year over year
  • You can't find developers who know the technology
  • The vendor has stopped supporting it
  • New business requirements are impossible or prohibitively expensive to implement
  • Your team spends more time working around the system than working with it
  • Security vulnerabilities can't be patched
  • Integration with modern systems is difficult or impossible

When to keep the old system

  • It does what the business needs, even if the UI is dated
  • Maintenance costs are stable and reasonable
  • The technology still has community support and available developers
  • Required changes are feasible within the existing architecture
  • Replacing it would disrupt operations with no proportional business benefit

When to replace

Replace it if three or more of these sound familiar

  • Annual maintenance exceeds 30% of estimated rebuild cost
  • The technology has no active developer community
  • Critical business requirements can't be implemented
  • Security vulnerabilities exist that can't be patched
  • Staff workarounds have become the norm, not the exception
  • Integration with modern tools requires custom middleware

How to assess your system

  1. Calculate total cost of ownership: Licensing, hosting, maintenance hours, support contracts, workaround time, opportunity cost of features you can't build.
  2. Assess technical health: Is the codebase maintainable? Are there automated tests? Is the architecture sound?
  3. Map business requirements: List the top 10 things the business needs in the next 2 years. Can the current system deliver them?
  4. Evaluate risk: What happens if the system fails? If the one person who knows it leaves? If a security vulnerability is exploited?
  5. Get a second opinion: An external technical assessment removes internal bias and often reveals issues that insiders have normalised.

Key takeaways

  • If maintenance cost exceeds 30% of rebuild cost annually, replacement usually makes sense
  • Technology obsolescence alone isn't a reason to rebuild, business limitation is
  • The best assessment combines financial analysis with technical assessment
  • Most systems fall in the grey zone, that's where modernisation (not full rebuild) is usually the answer
Legacy SystemsSoftware PlanningTechnical Debt

Meet the person

Written by the person who does the work

This guide comes from real projects. If it raises a question about your own system, you can ask the founder directly.

HELLO PEOPLE designs, builds and looks after AI, software, app and data solutions for Australian businesses, with senior expertise on every project and a scope agreed before work starts. For software, that means starting with how your business runs, not with the code.

Since 2007, HELLO PEOPLE has delivered more than 100 projects from Perth for small and medium businesses across Australia: custom software and apps, system integrations, data migrations, reporting and dashboards, and AI that works inside the systems a business already runs.

I lead every engagement myself. I trained in accounting before moving into IT, hold accounting and IT professional qualifications and an MBA, and bring more than 20 years of experience across sales, service delivery, inventory and compliance. I am also a PhD candidate in AI at Curtin University, researching retrieval-augmented generation (RAG), so the technology is always judged by what it does for the business.

  • An old-fashioned service

    Small and boutique. The person who scopes your software is the person who builds it, and the same person is there on launch day.

  • Quick responses

    No ticket queue and no account manager in between. You hear back within one business day, usually sooner.

  • A long-term partner

    The first release is the start, not the end. When you need the next system, integration or report, you call the same person, who already knows your business.

Related guides

Modernisation 10 min read

Rebuild vs Modernise vs Patch

The three approaches compared.

Read guide
Modernisation 7 min read

Signs Your System Is Costing More Than It's Saving

Quantifying legacy system cost.

Read guide

Ask the author

Still have a question?

Ask it here and it comes straight to the founder. No sales call, no obligation, and a real answer even if the answer is that you do not need us.

Kasun Wijayamanna, Founder Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.