COBOL remains in some core banking environments because the code is only one part of a working operational system: business rules, data structures, batch jobs, transaction processing and connected services have to keep working together. Replacing it can mean rebuilding and verifying that wider environment, not simply translating source code. There is no reliable universal price for leaving COBOL; the cost depends on the scope, dependencies, migration plan and continuity controls.
Why COBOL still runs some banking systems
In a long-running core, the value lies not in the language by itself but in the operational behavior built around it. A system may encode years of business rules and connect to data stores, transaction monitors, batch reconciliation, customer services and other applications. A working system can therefore be difficult to change without putting essential processes at risk.
As an Amazon Associate I earn from qualifying purchases.
IBM’s vendor-published M&T Bank case study illustrates one kind of constraint: it says complex core-system data structures could make creating or changing applications take more than six weeks, even for minor changes. The publication date is not stated in the retrieved result, and this is a case-specific example, not an industry-wide measure.
The available evidence does not establish what share of commercial banks, core systems or transactions use COBOL. The U.S. Government Accountability Office’s 2025 report says that two selected Treasury systems used COBOL and assembly. Those federal examples show that the languages remain in use in critical systems, but they do not measure commercial banking prevalence.
#1 Best Overall
- Murach's Mainframe COBOL
- Mike Murach & Associates
- ABIS BOOK
Why leaving is more than rewriting code
A bank has to understand what the existing system does and how other processes rely on it before it can safely change or retire it. Some of that understanding may live in technical documentation and code; some may depend on experienced staff who know how exceptions and day-to-day operations work. Deloitte’s modernization guidance identifies long-tenured employees’ knowledge as one consideration alongside legacy technology.
- Business behavior: Identify the rules, exceptions and transaction outcomes the replacement must preserve.
- Data and interfaces: Map data structures and connections to other applications and services so records and dependent processes continue to work.
- Batch and operational routines: Account for scheduled processing and reconciliation as well as customer-facing transactions.
- Service continuity: Plan verification and staged transitions around the services customers and staff depend on. IBM’s Co-operative Bank case describes migration involving core banking, treasury and finance, with explicit concern about avoiding customer impact.
IBM Redbooks recommends a fit-for-purpose transformation roadmap and cautions that moving several technology layers at once is a major risk. That is a planning principle, not proof that one migration pattern suits every institution.
What the cost of leaving COBOL includes
The total depends on what “leaving” means: replacing selected transactions, replacing a larger core, or moving the surrounding platform as well. The sources available do not establish a representative all-in cost for a commercial bank replacing a COBOL core. GAO’s cost and risk observations concern government legacy IT, so they should not be treated as a banking price benchmark.
| Cost area | What the work may involve | What is established |
|---|---|---|
| Discovery and business-rule recovery | Document behavior, exceptions, interfaces, data, batch processing and operational knowledge before setting replacement scope. | Deloitte identifies legacy technology and long-tenured employee knowledge as modernization considerations; it does not provide a standard price. |
| Rebuild or replacement | Reimplement required behavior in a different language or platform, or adopt a packaged core. The scope depends on what the bank chooses to replace. | The reviewed sources provide no universal cost for this work. |
| Data and integration transition | Move or reconcile records and maintain connections between old and new components during transition. | No universal cost is quantified in the reviewed sources. |
| Verification and continuity | Test expected behavior, stage transitions and protect priority services while changes take effect. | IBM’s Co-operative Bank case describes migration of core and priority services with concern for customer impact; it is not a general cost estimate. |
| Parallel running and contingency | Plan how old and new components will coexist where needed, and define how to respond if a transition fails. | These are prudent planning considerations, not costs measured by the cited cases. |
| Ongoing operation after the decision | Compare the continuing costs and change constraints of the existing environment with the cost of transformation and the new arrangement. | The reviewed sources do not establish that retiring legacy technology automatically produces savings. |
A large named number can be misleading when the project scope differs. IBM Community reported in 2025 that CIBC upgraded 40,000 COBOL applications over three years. That is an application-upgrade example, not the cost or duration of replacing a bank’s core or leaving COBOL.
Rank #3
What a bank can do instead of a one-shot replacement
There is no universally superior option in the reviewed evidence. The decision is about fit: which constraints matter most, what must change, and how much transition risk the institution can manage.
| Approach | Questions to compare |
|---|---|
| Keep and improve the existing system | How long do changes take? Are the skills and support available? What are operating costs and constraints? Can services be exposed or extended safely? |
| Modernize around the core or replace transactions incrementally | What is the boundary between old and new? Can components operate together? How much integration overhead is acceptable, and how will customer services be protected? |
| Replace a larger core or move to another platform | Does the new arrangement cover required business behavior? How will data migration, verification, contingency, total transition cost and dependence on a vendor be handled? |
IBM describes gradual replacement of core transactions with modern Java while retaining a mainframe role. It is an example of incremental modernization, not a recommendation for every bank. IBM Redbooks’ warning about changing multiple layers at once is relevant when comparing any broad transformation plan.
Rank #4
How to make a credible cost estimate
Rather than start with a headline price, a bank can make the estimate decision-specific and expose its assumptions:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Define the outcome. Specify whether the aim is to improve the current core, replace certain transactions, or retire a larger system and its surrounding platform.
- Map dependencies and behavior. Identify data, interfaces, batch routines, exceptions and operational knowledge that the target must support.
- Set transition boundaries. Decide which components change together and which remain in place during staged work; account for integration between them.
- Cost verification and continuity explicitly. Include the work needed to demonstrate expected behavior, transition priority services and prepare contingency plans.
- Compare ongoing states. Evaluate the existing system’s operating and change constraints against the cost and risks of the proposed replacement, rather than assuming retirement equals savings.
- Label assumptions and uncertainty. Separate known scope from unresolved dependencies, and do not present an estimate from a case study or government system as a sector benchmark.
The key distinction is between the price of changing code and the total cost of changing a live banking environment. The latter depends on business scope, connected systems and the controls needed to preserve service.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
