Some of the world's largest financial institutions are running their most critical operations on software written in COBOL, a programming language that dates to 1959. Core banking systems, the engines that process every transaction, maintain every account balance, and power every financial product a bank offers, were largely built in the 1980s and 1990s on mainframe infrastructure that was never designed for the demands of digital banking. As we explored in our analysis of how regtech has transformed compliance into a digital product, the entire financial technology stack is being rebuilt around modern software principles. Core banking modernization is the most ambitious and consequential of these rebuilding efforts, because the core system is the foundation upon which everything else depends.
This article examines why legacy core banking systems are failing, the approaches banks are taking to modernize them, the risks involved, and why this transformation will define the competitive landscape of banking for the next decade.
The Legacy System Problem
The core banking systems at most major global banks were built between 1975 and 1995 on mainframe infrastructure using COBOL, PL/I, or other languages that were state-of-the-art for their era. These systems were designed for a world of batch processing, where transactions were collected throughout the day and processed overnight in large batches. They were built for a world where banking happened at branches during business hours, where a bank's customers numbered in the millions rather than hundreds of millions, and where the internet did not exist.
These systems still work. That is both their greatest strength and their most dangerous weakness. They process trillions of dollars in transactions daily with remarkable reliability. But they cannot support the real-time, always-on, multi-channel banking experience that customers now demand. They cannot scale dynamically to handle peak transaction volumes. They cannot integrate easily with modern APIs and cloud services. And they cannot be modified quickly to support new products, features, or regulatory requirements.
The Cost of Legacy
The financial cost of maintaining legacy core banking systems is staggering. Major global banks spend between $1 billion and $3 billion annually on mainframe operations, including hardware, software licenses, maintenance contracts, and the specialized personnel required to keep these systems running. The average age of a core banking system at a top-20 global bank is over 30 years, and the pool of developers who know how to maintain COBOL and mainframe systems is shrinking as retirement claims the generation that built these systems.
Beyond the direct costs, legacy systems impose opportunity costs that are even more damaging. Every new product launch, every integration with a fintech partner, every regulatory change requires custom development work on the core system that takes months or years. While neobanks can launch a new savings product in weeks, traditional banks may require 12 to 18 months to bring the same product to market. This speed disadvantage compounds over time, as traditional banks fall further behind in the features and experiences that attract and retain customers.
Modernization Approaches
Banks are pursuing several distinct approaches to core banking modernization, each with different risk profiles, timelines, and outcomes.
Strangle-and-Replace
The strangle-and-replace approach, also known as the strangler fig pattern, involves building a new core banking system alongside the existing legacy system and gradually migrating functions from the old system to the new one. Individual banking services, such as account opening, payment processing, or loan origination, are rebuilt on the new platform and switched over one at a time, while the legacy system continues to handle the remaining functions.
This approach is the most popular because it manages risk effectively. By migrating incrementally, banks can test each new function thoroughly before switching, and they can roll back to the legacy system if problems arise. The downside is that the migration takes a long time, often five to ten years for a full core banking replacement, and during that period the bank must maintain two parallel systems, which doubles the operational complexity and cost.
Cloud-Native Greenfield
The greenfield approach involves building an entirely new cloud-native core banking system from scratch and migrating all customers and products to the new system at once. This approach is faster and produces a cleaner result, but it carries significantly more risk because there is no fallback to the legacy system if the migration fails.
Several institutions have taken the greenfield approach with notable success. Shuttle Financial, a digital bank built in Australia, launched with a completely cloud-native core banking stack. In the US, Column NA built its core banking infrastructure on a modern ledger designed from the ground up for API access and real-time processing. These greenfield institutions demonstrate what is possible when modern technology is applied to core banking without the constraints of legacy systems.
Platform-as-a-Service Migration
An emerging approach is to migrate core banking functions to core banking platforms as a service provided by specialist vendors. Companies like Thought Machine, Mambu, Temenos, and Finacle offer modern core banking platforms that banks can configure and deploy without building their own systems from scratch. This approach reduces the development burden while still delivering a modern, cloud-native core banking capability.
Thought Machine's Vault platform, for example, provides a configurable, cloud-native core banking system that banks can customize for their specific product and regulatory requirements. Standard Chartered Bank has deployed Vault as the core for several of its digital banking initiatives, while JP Morgan has selected Thought Machine for its next-generation core banking platform. These partnerships demonstrate that even the largest banks are turning to platform providers to accelerate their modernization efforts.
Key Technologies in Modern Core Banking
Modern core banking systems are built on a fundamentally different technology stack than their legacy predecessors.
Cloud Infrastructure
Modern cores run on cloud infrastructure from providers like AWS, Microsoft Azure, and Google Cloud, rather than on proprietary mainframe hardware. Cloud infrastructure provides several critical advantages: dynamic scalability that allows the system to handle traffic spikes without over-provisioning, geographic distribution that ensures low-latency access for customers worldwide, and a pay-per-use pricing model that converts fixed infrastructure costs into variable costs that scale with actual usage.
The migration to cloud infrastructure is not without challenges. Banking regulators in some jurisdictions still have concerns about the security and resilience of cloud services, and some banks operate in markets where cloud adoption faces regulatory hurdles. However, the trend is clearly toward cloud-based core banking, and regulatory frameworks are evolving to accommodate this shift.
Microservices Architecture
Modern core banking systems use microservices architecture, where each banking function, such as account management, payment processing, or loan origination, is implemented as an independent service that communicates with other services through APIs. This architecture provides several advantages over the monolithic structure of legacy systems: individual services can be updated, scaled, or replaced independently without affecting the rest of the system, and new features can be developed and deployed by small, autonomous teams without coordinating with the entire organization.
API-First Design
Modern cores are designed with API-first principles, meaning that every function is accessible through well-documented, standardized APIs from day one. This design enables seamless integration with fintech partners, third-party services, and the bank's own digital channels. The API-first approach is what makes Banking-as-a-Service possible, as it allows banks to expose their core capabilities to external developers in a controlled, secure manner.
The shift to API-first design has profound implications for how banks build and deploy technology. In the legacy world, adding a new integration required custom development work on the mainframe that took months. In an API-first world, new integrations can be established in days or weeks, dramatically accelerating the pace of innovation.
"The banks that are replacing their core systems are not just upgrading technology. They are rebuilding their organizations around the principle that software quality and speed are the primary competitive advantages in financial services."
The Risks of Modernization
Core banking modernization is one of the most complex and risky technology projects an institution can undertake. The risks are well documented, and the history of failed modernization projects is long.
Data migration risk is one of the most significant challenges. Banks have decades of customer data, transaction histories, and product configurations that must be migrated accurately to the new system. Data migration errors can result in incorrect account balances, lost transaction histories, and regulatory violations. The data migration process for a large bank can take 18 to 24 months and require dedicated teams of data engineers and quality assurance specialists.
Operational disruption during the migration period is another major concern. The cutover from the legacy system to the new core must be planned and executed with precision, as any disruption to banking services can affect millions of customers and trigger regulatory scrutiny. Banks typically conduct multiple rehearsals of the cutover process and maintain detailed rollback plans in case of problems.
Organizational change management is often underestimated. A new core banking system requires different skills, different processes, and a different organizational culture. Staff who have spent decades working with legacy systems must learn new tools and workflows. Compliance teams must adapt to new reporting capabilities and requirements. The organizational transformation required to support a modern core is as significant as the technology transformation itself.
The Competitive Landscape
The core banking modernization market has attracted both established technology vendors and innovative startups. The competitive landscape is dynamic, with different players offering different approaches to the modernization challenge.
Established banking technology vendors like Temenos, FIS, and Fiserver have modernized their core banking platforms to offer cloud-native, API-enabled capabilities. These vendors have the advantage of deep banking industry knowledge and established relationships with major banks, but their platforms sometimes carry the architectural constraints of their legacy origins.
Next-generation core banking platforms like Thought Machine, Mambu, and 10x Banking have been built from scratch on modern technology stacks. These platforms offer the architectural advantages of cloud-native design, microservices, and API-first principles without the constraints of legacy code. However, they are still building their track records with large-scale bank deployments.
Cloud providers like AWS, Azure, and Google Cloud are increasingly offering banking-specific services and compliance frameworks that support core banking workloads. These providers are partnering with core banking platform vendors to offer integrated solutions that combine modern core systems with cloud infrastructure and compliance tools.
What Comes Next
The next five years will be decisive for core banking modernization. The institutions that complete their modernization journeys by 2030 will have the technology foundation to compete effectively in a digital-first banking market. Those that delay or fail will face an increasingly difficult competitive position, as the cost of maintaining legacy systems rises and the pace of digital innovation accelerates.
The trend toward composable banking, where banks assemble their technology stack from best-of-breed components rather than relying on monolithic platforms, will accelerate as core banking modernization progresses. This approach allows banks to adopt new technologies, such as AI, blockchain, and real-time payments, without replacing their entire infrastructure each time a new capability emerges.
For customers, the result of core banking modernization will be faster, more reliable, and more innovative banking services. Real-time payment processing, instant account opening, personalized product offerings, and seamless omnichannel experiences are all enabled by modern core systems. The banks that deliver these experiences will earn customer loyalty in an era where switching has never been easier.
Core banking modernization is not just a technology project. It is a strategic transformation that will determine which banks thrive in the digital era and which become relics of an earlier age. The institutions that approach this transformation with the urgency, investment, and organizational commitment it requires will build the financial institutions of the future. The ones that do not will find themselves running increasingly expensive systems that support increasingly unsatisfactory customer experiences, wondering how the industry they once dominated passed them by.