Dimitar Dimitrov is the founder and Managing Partner at Accedia, a leading European AI & Custom Software Development Company.
getty
When did your core banking system last slow down a product launch, regulatory change or strategic initiative?
For many CIOs, that question becomes harder to dismiss after years of modernizing the infrastructure, APIs and digital channels around the platform, while the platform itself has remained unchanged. The gap between modern capabilities and legacy architecture widens over time, until it shows up as complexity, cost and delivery risk.
The default response is to move straight to replacement. The problem with this approach is that it concentrates risk in a single cutover, before dependency on the legacy environment is reduced. The more reliable sequence is to first decouple—separating critical business functions and dependencies from the legacy core—then replace once both environments can run in parallel with defined ownership and decision rights.
Whether your bank is ready for that second step, however, depends on three internal conditions, which I’ll break down below.
My answer is consistent: Decouple first, replace second. Full replacement concentrates on transition risk before the organization is ready to absorb it. The new system is unproven in production; the legacy system cannot yet be retired, and both must be governed simultaneously.
Decoupling changes that: It allows you to progressively move regulatory obligations, operational workloads and integration dependencies off the legacy core, reducing what replacement needs to carry when the time comes. As transformation programs mature, the legacy core becomes increasingly difficult to work around, and the pressure to address it directly grows.
Before committing to full core banking replacement, you need to check if three conditions inside your organization are fulfilled.
The most important question before setting a replacement timeline is whether the legacy core can realistically be retired within it. Most CIOs focus heavily on evaluating the target platform, when the harder challenge is understanding how much the organization still depends on the one it is trying to leave.
If your existing core still supports active regulatory obligations, it remains operationally critical regardless of what your migration road map says. Bringing the new platform live does not transfer those obligations. It creates a second operating environment that your compliance, operations and engineering teams must govern, maintain and keep current in parallel.
This is where many banks underestimate complexity. The larger the regulatory footprint of the legacy core, the more the program shifts from a technology delivery initiative into an organizational coordination challenge across the institution.
A CIO Check: Are material regulatory updates still being delivered to the legacy environment? If they are, your organization has not yet reduced dependency enough to absorb the operational and governance pressure that full replacement creates, making decoupling the more viable step.
Banks that move directly to full core replacement without decoupling first almost always run over time and over budget. IBM found that 94% of banking transformation programs exceed their planned timelines, with delays that directly impact ROI. In my experience, this is usually the point where plans begin losing executive support long before they fail technically. Boards start asking for visible progress while most of the complexity and risk still sit ahead of the organization.
Decoupling helps to change that dynamic. Each migration step produces something measurable: a regulatory obligation transferred, a dependency removed or an operational workload moved off the legacy core. That gives you something concrete to show in quarterly reviews instead of repeatedly defending delayed outcomes.
A CIO Check: Before committing to replacement, define three things explicitly: what the board expects to see after 12 months, which metrics will prove risk is decreasing and what evidence regulators will expect during the transition. If leadership cannot answer those questions from the start, expectations will likely drift, and the program may lose credibility when pressure increases.
Core banking modernization slows when no one has clear authority to decide between regulatory delivery and migration work.
This is the first real test of your governance model. Regulatory commitments, production support and transformation initiatives will inevitably compete for the same delivery capacity. Without predefined decision rights, teams will make local decisions that protect immediate obligations but delay program momentum.
I saw this happening at Accedia while partnering with a U.K. bank on modernizing its core banking system. The bank’s legacy mortgage platform was scheduled for retirement, but regulatory changes continued to require delivery as the new environment entered stabilization. With no clear decision rights, teams prioritized regulatory obligations, but the migration fell behind schedule.
It was clear that the governance gap had to be resolved before any technical work could continue. Leadership assigned separate ownership for the legacy and target environments and defined explicit escalation rights for priority conflicts. The next two regulatory deadlines were met on time, and the migration resumed on a schedule both teams could commit to.
A CIO Check: Ask your internal leaders or core modernization partner to track how often transformation work is paused to accommodate regulatory or operational priorities. If this becomes a recurring pattern, strengthen governance by assigning accountable owners for both the legacy and target platforms and by defining a clear escalation path for priority decisions.
I've seen too many well-planned core modernization programs stall because leadership focused on building the new platform and assumed the legacy system would take care of itself. It doesn't. According to EY, decommissioning consistently receives insufficient attention and resources, and that gap is what leaves most transformations incomplete.
If you're moving toward full core banking replacement, first pressure-test your governance model, your regulatory footprint and your board's timeline expectations. Most of the hard questions in a core banking transition are organizational, and they are easier to answer before the pressure arrives than during it.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。