Modernisation Guide

When Should You Modernise a Legacy Application — and When Should You Leave It Alone?

Modernisation is not automatically a rewrite. The right choice depends on business value, operational risk, skills, architecture and the cost of change.

Innovation Lead pointing at Digitization on a digital screen. Converting analog records, paperless workflows, and data migration. Modernizing legacy systems for a high-tech future.

Legacy technology is often discussed as though age alone makes a system unsuitable. In practice, some old applications are stable, well understood and economically sensible to retain.

Start with business criticality

Understand what the application does, who depends on it and what failure would cost before choosing a technical strategy.

Separate age from risk

An old platform can be low risk while a recently built application can be fragile. Assess maintainability, security, skills and change frequency independently.

Choose the smallest useful intervention

Rehosting, refactoring, replacing components and exposing APIs may deliver most of the benefit without a wholesale rewrite.

About the author

Contributor to Inside Tech Talk.

View all articles →
Inside Tech Briefing

Like this article?

Get one useful email each week with the enterprise technology developments worth understanding — without the noise.

Inside Tech Briefing

The technology developments worth understanding — without the noise.