Legacy System Modernisation Strategies
Legacy system modernisation addresses the accumulated technical debt of organisations that have been running software for years or decades. Legacy systems constrain business agility, create operational risk, drive high maintenance costs, and make talent acquisition difficult. Yet migrating them is expensive, risky, and disruptive. Understanding the available strategies enables making the right choice for each situation.
Modernisation Strategies (Gartner's 6 Rs)
- Retain: Keep the system as-is — justified when replacement cost exceeds benefit or the system is stable and low-risk
- Retire: Decommission the system — when the functionality is no longer needed
- Rehost ("lift and shift"): Move to cloud infrastructure without code changes — fast, low risk, limited benefit
- Replatform: Minor changes to optimise for cloud (containerisation, managed database services) — moderate effort, moderate benefit
- Refactor/Re-architect: Significant code changes to improve architecture without changing functionality — high effort, high benefit for long-lived systems
- Replace: Replace with a commercial or custom-built modern system — highest effort, highest transformation potential
The Strangler Fig Pattern
For large systems, the Strangler Fig pattern (Martin Fowler) incrementally replaces legacy functionality: new functionality is built in the new system; existing functionality is migrated piece by piece; the legacy system "dies" gradually as functionality moves. This avoids "big bang" migrations that are high-risk and take years.