Legacy system modernisation
Decision brief for Legacy system modernisation
Use this when a system blocks important changes or is difficult to test and operate. Age alone is not a reason for a rewrite; maintenance or a bottleneck fix may suffice. Ongoing support differs from a defined modernisation project.
Start with boundaries, dependencies, actual rules and data ownership. Characterisation tests capture behaviour worth preserving before choosing a separable component. Work requires authorised source access, documentation, sanitised examples and business decisions about conflicting behaviour. We do not promise zero downtime or preserve old defects without review.

