Legacy System Modernisation — The Strangler Fig Approach
The safest way to modernise legacy systems is the strangler fig pattern: gradually replace components while the old system keeps running. Start with the highest-risk or most business-critical module first.
The safest way to modernise a legacy system is the strangler fig pattern: build new components alongside the old system and gradually route functionality to them until the legacy system can be retired. Start with the module that creates the most business risk or maintenance cost. Avoid the big bang rewrite — it fails more often than it succeeds.
What legacy modernisation means
Legacy system modernisation is the process of updating or replacing an existing software system that is still in production but is difficult to maintain, expensive to run, or unable to meet new business requirements. The problem is not always the technology — sometimes the system works but the business needs it to do things it was never designed for. Modernisation addresses both scenarios.
The four approaches
There are four main approaches to legacy modernisation. Each suits a different situation:
| Approach | Risk | Timeline | Best for |
|---|---|---|---|
| Big bang rewrite | Very high | 6-18 months | Small, well-understood systems with no live dependencies |
| Strangler fig | Low | 12-36 months | Complex, business-critical systems that cannot afford downtime |
| Rebuild from scratch | High | 9-24 months | Systems where the existing codebase is beyond repair |
| Retire and replace | Low | 3-9 months | Commodity functions (CRM, HR, accounting) with good alternatives |
For most businesses, the strangler fig approach delivers the best balance of safety and progress. It allows you to modernise without stopping operations.
Strangler fig explained step by step
The strangler fig pattern works like this: identify the most painful or most critical module first. Build a new version of that module as a standalone service alongside the old system. Route traffic for that module to the new version using a proxy or feature flag. Test thoroughly in production with real traffic. Once the new module is stable, retire the old module. Repeat for the next module. Over time, the entire legacy system is replaced with zero downtime at any point.
This approach is called strangler fig after the tropical plant that grows around a host tree and eventually replaces it entirely. The key advantage is that you can stop at any point — if business priorities change, you have a partially modernised system that still works.
Risk management
The three biggest risks in legacy modernisation are data migration errors, business logic gaps (the old system had undocumented rules), and stakeholder fatigue from long projects. Mitigate data risks with parallel running and reconciliation reports. Mitigate logic gaps by involving the people who use the system daily — they know the edge cases that no document captures. Mitigate fatigue by delivering something visible within the first three months. For more on why projects go wrong, see our analysis of why software projects fail.
Choosing a partner
Legacy modernisation is not a project for a generalist agency. The partner needs deep experience in both the old technology (whatever that is) and modern architectures. They also need the discipline to work incrementally. A partner who proposes a full rewrite with a distant delivery date should be treated with caution. For guidance on evaluating partners, see our guide to choosing a software development partner and the broader discussion of build versus buy decisions.
Frequently asked questions
Legacy system modernisation is the process of updating or replacing outdated software systems with modern technology while preserving business functionality. It can involve rehosting, refactoring, rebuilding or replacing components.
The strangler fig pattern is a software modernisation approach where you gradually replace parts of a legacy system with new components while the old system continues running. New functionality routes to the new system, and over time the legacy system is entirely replaced.
It depends on the system. If the existing system runs critical business processes with known edge cases, rebuild incrementally (strangler fig). If the system is a commodity function (e.g. CRM, HR system), replace with an off-the-shelf product.
Most medium-scale modernisation projects take 6-18 months. A full strangler fig replacement of a large system can take 2-3 years. The key is to show value early by replacing the most painful module first.
The main risks are data loss during migration, business disruption during cutover, scope creep, and underestimating the complexity of legacy business logic. These are all manageable with the right approach and experienced technical partners.