Legacy Software Modernisation: When to Rebuild, Refactor or Replace

IT specialists reviewing an old server and a laptop together while planning a software upgrade

Many New Zealand organisations rely on software that was built ten or even twenty years ago. It still runs the business, but it is getting harder to support, slower to change and riskier to keep. Legacy software modernisation is the process of bringing those systems up to date so they are secure, maintainable and ready for what comes next. The hard part is not deciding that something needs to change. It is deciding how: rebuild from scratch, refactor what you have, or replace it with something else entirely.

This guide explains the main options, the warning signs that it is time to act and a practical way to choose the right path. If you would like an outside view of your own systems, our IT consulting team regularly helps businesses assess ageing software before they commit to a direction.

What counts as legacy software?

Legacy does not simply mean old. A system becomes legacy when it is still important to the business but has become difficult or expensive to maintain and improve. Common examples include:

  • Desktop applications built on outdated frameworks such as Visual Basic 6, Delphi or early versions of .NET
  • Access databases or spreadsheets that grew into business-critical tools
  • Web applications running on unsupported versions of PHP, Java or other platforms
  • On-premises servers that nobody wants to touch in case something breaks
  • Systems where only one developer, possibly long gone, understands the code

Signs your system needs modernising

  • Security concerns. The operating system, framework or database no longer receives security updates.
  • Integration headaches. Connecting to modern tools such as Xero, online payment providers or cloud services is slow, fragile or impossible.
  • Slow change. Small updates take weeks because the code is tangled and poorly documented.
  • Key-person risk. Knowledge of the system sits with one person or one small supplier.
  • Poor user experience. Staff need workarounds, and it does not work on mobile devices or outside the office.
  • Rising running costs. Hardware, licences and specialist support are becoming more expensive every year.
  • Compliance pressure. It is difficult to meet Privacy Act 2020 obligations, such as controlling access to personal information and responding to privacy breaches.

One or two of these signs might be manageable. Several together usually mean the cost of standing still is growing faster than the cost of change.

Legacy software modernisation options compared

There are many technical labels for modernisation strategies, but most decisions come down to three broad paths.

Refactor: improve what you already have

Refactoring means restructuring and updating the existing code without changing what the system does for users. It might include upgrading frameworks, cleaning up the codebase, adding automated tests, moving to a supported database or wrapping parts of the system with modern APIs.

Best when: the core logic is sound, the system mostly does what you need, and the main problems are technical debt, security updates or integration.

Rebuild: start again with modern technology

Rebuilding means designing and developing a new system that does the same job, often better, using a modern architecture. The old system usually runs alongside it until the new one is ready, and data is migrated across.

Best when: the existing technology is too outdated to update, the business has changed significantly, or the system is a genuine competitive advantage that deserves a fresh foundation. Rebuilding is a significant custom software development project, so it needs careful scoping.

Replace: move to an off-the-shelf product

Replacing means retiring the legacy system and adopting an existing SaaS or packaged product, configured for your business. Data is migrated and processes are adjusted to fit the new tool.

Best when: the legacy system handles a common business function, such as accounting, payroll or a standard CRM, where mature products already exist and your process does not need to be unique.

Factor Refactor Rebuild Replace
Upfront cost Low to medium Medium to high Low to medium, plus ongoing licences
Disruption to users Low Medium Medium to high
Fit with your processes Keeps current fit Designed around your needs You adapt to the product
Long-term flexibility Moderate High Limited by the vendor
Risk level Lower, done in small steps Higher, needs strong planning Medium, depends on migration

The middle ground: incremental modernisation

Modernisation does not have to be a single big-bang project. In fact, the safest approach is often incremental. A popular pattern is sometimes called the “strangler fig” approach. New features and modules are built around the edges of the old system, gradually taking over its responsibilities until the legacy core can be switched off.

For example, an Auckland distributor might keep its old order management database running while building a new customer portal and reporting dashboard that connect to it through an API. Over time, order entry, invoicing and stock management move into the new platform piece by piece. Each step delivers value, and the business never has to bet everything on one launch date.

Moving to the cloud is often part of this journey. Shifting hosting from an ageing on-premises server to a managed cloud platform, with proper backups, monitoring and automated deployments, can reduce risk quickly even before the application itself is rewritten. Our cloud and DevOps services cover exactly this kind of work.

How to decide: a practical framework

  1. Map what the system does. List its functions, users, data and integrations. You may find parts nobody uses any more.
  2. Assess the technical health. Have an experienced developer review the code, platform, security and documentation. Is it fixable or fundamentally outdated?
  3. Clarify business value. Which parts are standard, and which reflect a unique way you work? Standard parts lean towards replace; unique parts lean towards refactor or rebuild.
  4. Look ahead three to five years. Consider growth, new channels, mobile access and integrations you will need.
  5. Compare total cost of ownership. Include licences, hosting, support, staff time lost to workarounds and the risk of an outage or breach.
  6. Choose a phased plan. Decide what to tackle first, usually the area with the highest risk or the biggest payoff.

It is common for the answer to be a mix: replace the accounting module with Xero, refactor a stable reporting engine and rebuild the customer-facing parts.

Managing the risks of modernisation

  • Protect your data. Plan data migration early, clean data before moving it and test migrations repeatedly before go-live.
  • Run systems in parallel. Where possible, keep the old system available until the new one has proven itself.
  • Capture hidden knowledge. Interview long-serving staff about the quirks and rules the old system enforces. Many are not documented anywhere.
  • Test thoroughly. Automated tests and user acceptance testing catch issues before they affect customers.
  • Plan training and change management. New software only succeeds if people are confident using it.
  • Think about security from the start. Build in access controls, logging and encryption so the new system meets today’s expectations under the Privacy Act 2020.

What a modernisation assessment should include

Before committing budget, it pays to invest in a short assessment. A useful one should leave you with:

  • An inventory of the system’s functions, users, data stores and integrations
  • A review of code quality, platform support status and known security gaps
  • A clear recommendation for each part of the system: keep, refactor, rebuild or replace
  • A phased roadmap with priorities, dependencies and indicative budget ranges
  • A list of quick wins, such as backups or patching, that reduce risk immediately

With that in hand, you can make decisions based on evidence rather than gut feel, and approach any provider with a clear brief.

Frequently asked questions

How much does legacy software modernisation cost in NZ?

It varies widely with the size of the system and the path you choose. As a typical market range, a focused refactor or cloud migration might start around NZD 20,000 excl. GST, while a full rebuild of a complex business system can run well into six figures. A short assessment is the best way to get realistic numbers for your situation.

How long does modernisation take?

Small refactoring projects can take a few weeks. Larger rebuilds often run over several months and are best delivered in phases, so value arrives early rather than all at the end.

Can we keep using the old system during the project?

Usually, yes. Incremental approaches are designed so the business keeps running on the legacy system while new parts are introduced and tested.

Is it better to rebuild or refactor?

Refactor when the underlying logic is solid and the problems are mainly technical. Rebuild when the platform is too outdated to support, or when your business needs have moved well beyond what the system was designed for.

What happens to our data?

Your data is migrated to the new system. This involves mapping old fields to new ones, cleaning duplicates and errors, and running test migrations so nothing is lost on go-live day.

Do we need to move to the cloud?

Not necessarily, but most modernised systems benefit from cloud hosting through better reliability, automatic backups, easier scaling and remote access. The right choice depends on your data, compliance needs and budget.

Take the first step with a clear assessment

Legacy software modernisation is a significant decision, but leaving an ageing system untouched carries its own growing risks. The right path, whether rebuild, refactor, replace or a combination, depends on your system’s health, your business goals and your budget. If you would like an honest assessment and a phased plan, book a free 60-minute consultation with our Auckland team. We will look at what you have today, talk through the options and help you choose a sensible, low-risk way forward.

Share Article:
About Author

Consectetur sollicitudin cubilia facilisis lobortis lacus a ac phasellus. Mus pulvinar enim suspendisse pharetra id commodo platea nunc aliquet.