Modernise the old system, or rescue the half-built one.

Modernising a legacy system

The safe method is a parallel run: the old system keeps running the whole way through, and each part is retired only once the new equivalent is proven in production. In our experience it’s the approach that reliably works on a business-critical system. Sometimes the right answer is to leave the legacy system alone, and we’ll say so.

Rescuing a broken build

Most stalled projects can be recovered. The code is often further along than it feels, the architecture is salvageable, and the missing pieces are known. Occasionally the honest call is a rebuild, and we’ll tell you that early rather than at month six.

In production

For Media, Entertainment & Arts Alliance (MEAA) we replaced an unstable legacy membership system that needed remote-desktop access just to run, rebuilding it as a web application. For Claims Management Australia we moved an ageing desktop application to the web and redesigned the data for new requirements. For Quickways, an ongoing engagement, we repaired the worst components in place and wrote the migration scripts to fix the structure underneath.