For more than six decades, COBOL has quietly powered the world’s most critical systems. While often labelled as a “legacy” language, COBOL remains deeply embedded in the global economy, powering everything from banking transactions and insurance policies to airline reservations and government services. For most organisations, these applications are not peripheral systems but integral to their daily operations and client service.
This longevity is not accidental. As documented in The Early History of COBOL by Jean E. Sammet, COBOL was explicitly designed in 1959 as a common, machine‑independent business language, with a strong emphasis on readability, stability and long‑term maintainability. Even its original designers viewed COBOL as infrastructure rather than innovation – a pragmatic foundation meant to outlast hardware cycles and vendor competition.
This article examines the extent of COBOL’s continued use, why it remains important, and the impacts and risks organisations face when modernising these mission‑critical systems.
How Many COBOL Applications Still Exist?
Although precise numbers are hard to verify, industry estimates consistently point to a massive COBOL footprint:
- Tens of billions of lines of COBOL code are still in production worldwide.
- A significant percentage of global financial transactions – often cited as over 70% – touch a COBOL system at some point.
- Banks, insurers, governments and large enterprises often run hundreds or thousands of COBOL programs supporting core processes.
These applications typically run on mainframes or highly stable midrange systems and have been refined over decades to handle extreme volumes with exceptional reliability.
Why COBOL Systems Remain Critical to Businesses
COBOL applications persist not because organisations resist change, but because these systems deliver unique and proven value – much of it rooted in their original design goals.
As early as 1959, the newly formed COBOL committee prioritised portability, clarity and business alignment over technical elegance. Sammet’s historical account shows that COBOL was intentionally optimised for business continuity – separating data from logic, embedding business rules directly into code and enabling programs to move across machines with minimal change (Sammet, 1981).
In modern enterprises, this translates into several lasting strengths:
- Stability and reliability: Many COBOL systems run for years with near‑zero downtime.
- Performance at scale: They handle massive transaction volumes efficiently.
- Deeply embedded business logic: Decades of regulatory rules, pricing models and exception handling are encoded directly into the applications.
- Client trust: End‑user services, which include payments, claims, benefits and settlements, depend on these systems being correct and always available.
Replacing or modifying such systems directly affects customer experience and organisational credibility.
The Modernisation Imperative
Despite their strengths, COBOL environments face growing pressure. This creates what many organisations experience as a modernisation paradox – systems that were explicitly designed to be long‑lived and adaptable are now among the most difficult to change.
COBOL’s emphasis on stability, backward compatibility and business continuity – all deliberate design decisions – means that change must be approached with extreme caution. Modernisation initiatives often struggle not because the technology is incapable, but because the systems are deeply embedded in decades of operational knowledge, regulatory interpretation and customer trust.
Key drivers forcing modernisation include:
- Ageing infrastructure and soaring operational costs.
- Difficulty integrating with modern digital channels and APIs.
- Shrinking pools of experienced COBOL developers.
- Expectations for faster innovation and time‑to‑market.
As a result, modernisation is no longer optional for many organisations – it is a strategic necessity.
Risks of Modernising COBOL Applications
Modernising core COBOL systems is inherently risky due to their central role in business operations. These risks are exacerbated by the fact that many COBOL applications were never intended to be rewritten frequently; rather, they evolved incrementally over extended periods.
Historical context matters here: early COBOL development deliberately prioritised accuracy, readability and long-term stability over ease of refactoring or replacement. Modernisation efforts that ignore this context often underestimate both technical and organisational risk.
Modernising core COBOL systems is inherently risky due to their central role in business operations:
1. Business Disruption
A failed migration or poorly understood dependency can interrupt critical services such as payments, billing or customer access.
2. Loss of Embedded Knowledge
Much of the business logic exists only in code, not in documentation. Rewriting systems risks losing subtle rules accumulated over decades.
3. Data Integrity and Compliance
COBOL systems often manage highly regulated data. Errors introduced during modernisation can lead to compliance breaches or financial loss.
4. Cost and Timeline Overruns
Large‑scale rewrites frequently exceed budgets and schedules, sometimes delivering less functionality than the original systems.
5. Organisational Confidence
Core system failures can erode trust – internally with stakeholders and externally with clients and regulators.
In Part 2 the common modernisation approaches and how AI can assist will be discussed.
