Guides

Legacy and custom application migrations have the lowest success rate of any workload category at 61%.

The choice between portfolio-based and trigger-based legacy modernisation depends on the artefacts used.

Enterprise legacy transformation changes the estate boundaries and interfaces to ensure the organisation can absorb future change.

The gap between source records and run-time footprints determines the risk of a legacy application migration.

Refactoring only maintains its value when the existing behaviour of the system is strictly preserved.

Legacy system cost reduction requires a charge register that identifies the specific recurring payments to be stopped.

OpenLegacy defines legacy system integration as connecting on-premises systems to cloud technologies via API platforms.

Replatforming protects existing business logic while removing the risks of unsupported technology.

Legacy system security requires treating unsupported systems as exposures with written controls and assigned owners.

A legacy system upgrade is a decision about which current system behaviours must be preserved before technology is named.

Legacy to SaaS migration is only worthwhile when it transfers an unmanageable liability to a third party.

Mainframe modernisation succeeds when estates are treated as sets of capabilities with owned contracts rather than a single monolith.