In reality, replacing a core is often akin to ‘heart surgery’ where the existing core is benchmarked against a new generation then replaced, while the surrounding architecture is retained. However, this approach is not only risky but outdated and unnecessary. Why?
There are a few fundamental issues with this approach. First, with the focus on pure functionality as a benchmark, true digital transformation is addressed only by a modern architecture, tech stack and a complete rethink of the development processes. This requires a revamp of the status quo: teams need to be upgraded and up-skilled, investments need to be made, and the ownership must belong to the business leaders not technology. Incumbents also tend to upgrade the current Core Banking but in the cloud, this approach is indeed less risky but remains nothing but the same. No fundamental transformation or redesign, some even opt for an in-house built Core Banking, imagine that! Thousands of hours to build something that will never be better than a new modern core banking supported by a composable architecture.
A business roadmap is crucial – incumbent banks need to reinvent themselves and must be led by a revamped offering of current and new banking services.
Unfortunately, the traditional ‘build and migrate’ approach or just upgrade the current Core Banking remains commonplace among core replacement programs. And a transformation that follows the principle of ‘compare the core functionality, minimize customization and continue the previous journey’ will fail to deliver true digitalization. Without a complete redesign and rethinking of how a bank will innovate and deliver banking services, a transformation will never deliver on its promise.
The time is right for CxO and bank business leaders to rethink and reimagine their current operating models to deliver digitalization that delivers on its promise of bank transformation.
In practice much of the banking industry has not reached the end of transformation, however most incumbents should endorse the END OF MIGRATION.
The best approach with minimal disruption to business as usual is to build ‘a bank within the bank’ to support the launch of new products and to minimize the integration points with legacy infrastructure. This adjacent approach empowers a bank to build a new bank with a composable architecture, microservices, event-driven, with a complete new tech stack and a new generation core banking. All this modern technology can – and should – be built in public cloud, because with private clouds the required CAPEX investments will usually be prohibitively high. After a period of reflection, most regulators have approved public cloud, and it seems inevitable that remaining ones will do so in the near future.
Next-generation core banking systems are fast, scalable, and extremely powerful and flexible product engines, with focus on product and client ledgers. This contrasts with building and packing all the functionalities in a single box as was the norm with the previous generation of core banking platforms. New solutions must be viewed continually in the context of a bank transformation, rather than simply improving what has gone before.