Why not migrate COBOL all at once?

Because a "big bang" replacement of the core concentrates enormous risk: any functional divergence affects real operations. The recommended pattern is strangler fig —incremental replacement with coexistence and output parity— which lets you roll back each step and preserves operational continuity.

What is it usually migrated to?

Typically to Java or Python on a microservices architecture, exposing the core behind APIs. The key is not the target language, but extracting and validating the business logic accumulated in the COBOL without losing behaviour.

What role does DORA play in this?

DORA requires operational resilience: service continuity, traceability and control of ICT risk. A COBOL core that few know how to maintain is a risk under that lens, and modernisation must preserve continuity, the ability to roll back, and documentation throughout the migration.

Glossary · Technical · Legacy modernisation

COBOL — the legacy core of banking and insurance

COBOL is a 1959 language that still runs the transactional core of much of banking and insurance: batch processes, accounts, policies, settlements. It is not a harmless relic: decades of undocumented business logic and the retirement of those who maintain it make it critical technical debt and a continuity risk.

Why it is still alive (and why it is a risk)

COBOL persists because it is reliable and moves enormous transaction volumes at predictable cost. The risk is not the language itself, but its context: talent shortage (the people who know it are retiring), coupling to mainframe and batch, lack of documentation and difficulty evolving at the pace of the business. Under DORA, moreover, dependence on systems that few know how to maintain is an operational resilience risk.

Modernisation strategies

Strangler fig — extract functionality into new services that coexist with the COBOL until it is emptied and retired, without a high-risk "big bang".
API encapsulation — expose the COBOL core behind a service layer to decouple consumers before rewriting.
Selective rewrite to Java/Python with output parity verified before each cutover.
Operational continuity — coexistence periods and comparison of results between the legacy and the new system.

Related in the glossary

See also technical debt and Oracle Forms, other common legacy fronts in banking and insurance.

How Vermont Solutions helps

COBOL core modernisation without disrupting operations

We apply strangler fig to the core: logic extraction, coexistence with output parity and phased rewriting, with Tier-1 operational continuity and DORA alignment.

See legacy and core modernisation →

Last updated: 2026-06-19. Editorial content by Vermont Solutions, citable with attribution.