top of page

The Legacy Catch-22: Why banks and credit unions can't stay on old systems and can't afford to leave

Nov 5
4 min read

Banks now spend about 70 percent of their IT budgets keeping the technology they already have running. That figure comes from Accenture's 2026 banking trends research, which also found technology costs have grown four times faster than banking revenue over the last fifteen years.


The obvious fix is to replace the old systems. But despite this, plenty of bank and credit union leaders keep the old systems running anyway.


The reason is what's inside them: customer histories, transactions, loan files, and the decisions behind them, any of which the institution may have to produce for a regulator years from now. Leaving puts that at risk, while staying gets more expensive every year. We've started calling this the “legacy catch-22.”


Why banks and credit unions can't just walk away from legacy systems


A bank isn't only running software. It's sitting on years of customer and transaction history that it may need to account for long after the people who created it have left.


The rules make sure of that. Under the Bank Secrecy Act, a bank generally has to keep most records for at least five years, and that's before you count what lending, disputes, exams and investigations can reach back for. None of those obligations care which system the records live in. If an examiner asks, the answer has to be there, and it has to hold up.


Migrations make people nervous for a simple reason. They move what the new platform needs, which is rarely everything, and the pieces left behind have the ones someone asks about two years later.


The move itself can go badly wrong, too. TSB's 2018 switch to a new platform left millions of customers locked out of their accounts for weeks, and UK regulators eventually fined the bank £48.65 million. Set a known cost against a risk like that and it's easy to see why so many boards leave things where they are.


Which leads to the obvious follow-up: what does leaving things where they are actually cost?


What staying on legacy banking systems really costs


Staying put feels safe, but the bill keeps moving. Support contracts get pricier as systems age, and the handful of people who really understand them retire or get poached. Somewhere along the way, the institution ends up running old and new side by side, held together with spreadsheets and manual workarounds.


You won't find any of that as a single line in a board pack. It shows up as a little more spend each year, which is how technology costs end up racing ahead of revenue.


Then there's security. Financial firms already carry one of the biggest breach bills of any industry, $5.56 million on average in 2025 according to IBM, behind only healthcare. Systems that are hard to patch and harder to monitor don't make that any easier.


For a lot of community banks and credit unions, though, the bigger cost doesn't show up in the budget at all.


How legacy systems hold community banks and credit unions back against fintechs


It's what they can't do. A fintech launching today has no thirty-year-old core to work around, and it's winning business. Cornerstone Advisors found that digital banks and fintechs took 44 percent of new checking accounts opened in 2024.


Institutions aren't ignoring this. In Cornerstone's latest survey, more than 80 percent of banks and credit unions plan to spend more on technology in 2026, but many of them also keep missing the deployments they planned.


Spending more and still falling behind is an odd place to be. Part of the explanation is simple: when so much money and attention goes into keeping yesterday running, there isn't much left over for what customers and members want next.


Why "stay or leave" might be the wrong way to frame legacy systems in banking


Most conversations about legacy systems in banking end up in the same place. Either you keep paying to run the old systems, or you take your chances with a big migration. Put like that, it's no wonder so many institutions stay.


That framing quietly assumes something, though: that keeping the history means keeping the system. We're not convinced it does, and once you stop assuming it, the choices in front of a leadership team look quite different.


How that works in practice, what a regulator would want to see, and where the institutions that have broken out of this tend to start are things we'd rather talk through properly than squeeze into a blog post.




So that's what we're doing. On Tuesday, November 17 at 2:00 pm ET / 11:00 am PT, we're sitting down for 45 minutes with people who see this problem from very different seats.


Alan Morley has spent more than 25 years in financial crime and regulatory risk, and he brings the regulator's view.


Richard Rotondo works with community banks and credit unions on technology and sees the competitive pressure up close.



It's a roundtable rather than a slide deck, and we'll take your questions as we go.


 
 
bottom of page