Legacy System

A legacy system is characterized by obsolete technology, scarce skills, high maintenance cost, or architectural mismatch—yet still supports essential business functions. Legacy status is contextual; age alone does not define legacy. EA programs prioritize legacy disposition using risk, cost, and strategic fit criteria.

In Practice

Larkinized LLC documents legacy dependencies, interfaces, and retirement constraints in the repository before migration approval. Heatmaps communicate legacy risk to executives funding modernization. Interim containment strategies—API wrappers, read-only archives—require explicit end dates.

Example

A mainframe policy admin system remains legacy due to COBOL skill scarcity and inability to meet digital channel NFRs.