Should I Stay or Should I Go?

Print Friendly, PDF & Email
CCG Catalyst Commentary

Should I Stay or Should I Go?

July 2, 2025

I’ve seen community banks grapple with core system modernization throughout my long career as a banker and a consultant. These conversations are often somber, filled with fears of disruption, betrayal by vendors, and the daunting cost of change. Yet, in a world where fintechs and neobanks are redefining banking, modernization is no longer optional. Community banks face a triple threat: outdated systems, unreliable vendors, and fierce competition. The good news? Community banks can evolve without risking it all.

The problem: a broken partnership

The core vendor-banker relationship is often like a marriage entered without really knowing the other person. You discover your partner doesn’t listen. It’s hard to compromise; they don’t understand your problems, nor do they take the time to do so. You might find your core vendor touts their “partnership” credentials, while their solutions feel like they were designed in a vacuum. And, because of how agreements are structured, divorce is hard.  

A major issue is that many vendors lack firsthand banking experience. They’ve never managed a balance sheet or faced a regulator’s scrutiny. The only CAMELS they know are animals. This leaves them out of touch with bankers’ realities. Their modernization attempts — shiny dashboards, a consolidation of two or more first generation cores into a new core that is still a first generation core, or touting cloud-based add-ons — prioritize sales over substance. When banks call for help, they are met with understaffed support teams or boilerplate responses. One banker told me recently their bank waited months for a vendor to fix a critical reporting issue, only to receive a half-baked workaround.

Bankers, meanwhile, dread the risks of modernization. A failed core conversion could mean downtime, lost customers, or regulatory penalties — existential threats for banks with razor-thin margins and a limited IT staff that’s often just one or two people juggling everything from cybersecurity to ATMs. Add to that the competitive pressure from fintechs, and it’s clear why many bankers feel trapped.

Understanding core systems

Before we can have a conversation about what to do, we first need to understand the core system landscape. I’ve written about this extensively here. Most community banks rely on legacy core systems, each with its strengths and limitations:

  • First generation (1960s–1990): Mainframe-based, reliable, but slow with outdated interfaces. Think of it as a sturdy old truck — functional but not flashy.

  • Second generation (1990s–2005): Client-server systems that added online banking but remain clunky, like putting a spoiler on a vintage car.

  • Third generation (2005–2017): Digital core systems emphasizing real-time processing and open architecture. These systems improved data management and customer experience but still face challenges integrating with rapidly evolving digital technologies.

  • Fourth generation (2018 onwards): Cloud-native and API-driven, offering real-time processing and seamless fintech integrations, but rare due to high costs.

     

Switching cores is daunting. Multi-year vendor contracts and proprietary data formats make it feel like rewriting the bank’s DNA. A typical conversion costs hundreds of thousands to millions, halts other initiatives, and demands extensive staff training and data migration. For small banks, it’s like climbing Mount Everest in flip-flops. Understanding what you have and what is out there is a good first step in making the process more palatable.

Assessing your core

If your bank is running a first generation core, it’s likely a reliable workhorse — your ledger is rock-solid, and it gets the job done. But is it the right system, and is your vendor the right partner? Before deciding to stay or switch, ask these critical questions:

  • Does it support your business strategy? If your bank aims to attract younger customers with mobile apps or real-time payments, a first generation core may struggle without costly add-ons. Assess whether your system can integrate with modern tools like APIs or middleware to meet future goals.

  • Is your vendor responsive? A first generation core is only as good as the support behind it. If your vendor’s help desk is unresponsive or lacks banking expertise, even a reliable system can become a liability. Evaluate their track record — how quickly do they resolve issues, and do their solutions align with your needs?

  • Are costs predictable? Legacy vendors often lock banks into long-term contracts with hidden fees for integrations or upgrades. Compare your current costs to alternatives, including the price of staying put versus switching to a different first generation or later generation provider.

  • Can you compete? A first generation core may work, but if competitors offer slicker digital experiences, you risk losing customers. Benchmark your system against peers to see if it’s holding you back.

If your first generation core aligns with your strategy, has reliable vendor support, and keeps you competitive, staying put may be wise. But if it’s a mismatch — or your vendor’s promises fall flat — consider switching to a better-fitting first generation or second generation system. This isn’t about chasing the latest tech; it’s about ensuring your core serves your bank’s unique needs.

A path forward: smart modernization

The assessment phase will help your bank determine whether your current system is meeting your bank’s needs and where the gaps are. In the end, it may require a core system swap, it may not. But it’s important to remember that, even if you decide to stay with your current system, modernization is still an imperative. There are a couple of ways banks can approach this shrewdly and strategically: 

  • Incremental upgrades: Enhance first or second generation cores with APIs or middleware to support modern features like real-time payments or mobile apps. Platforms like Finzly or Narmi make this possible without replacing the core.

  • Fintech collaboration: Join consortiums like the Bankers Fintech Council to share costs and risks with other banks. These partnerships connect banks with fintechs offering cutting-edge solutions tailored to community needs.

  • Vendor accountability: Demand transparent pricing, reliable support, and solutions that align with your bank’s priorities. If vendors fall short, explore competitors or negotiate better terms.

  • Regulatory support: Push regulators for sandbox programs or grants to make modernization less risky. Some parts of the country are already experimenting with these initiatives.

These strategies aren’t pipe dreams — they’re happening now. Banks that adopt them are staying competitive while minimizing disruption.

The risks of inaction

Sticking with a “if it ain’t broke, don’t fix it” mindset may feel safe, but it’s a losing strategy if your core can’t keep up. Legacy systems, even the best first generation cores, struggle with customer expectations. Fintechs and neobanks, unburdened by old technology, are stealing market share with innovative, customer-friendly solutions. Standing still cedes ground to competitors and risks long-term irrelevance.

Community banks have survived wars, recessions, and fintech invasions — they can survive this. But survival demands action. Assess your core, reject complacency, and stop waiting for vendors to lead the way. Explore incremental upgrades, collaborate with peers, and hold vendors accountable. Your customers, shareholders, and community are counting on you. Roll up your sleeves — the future belongs to banks that act.

Subscribe to our Insights