Imagine a banking system designed in the 1990s, a monolithic architecture where every modification requires months of development and endless testing. This is the challenge faced by Marginalen Bank, a regional bank that decided to replace its legacy system with a cloud-native platform. Their success, documented by Mambu and Avenga, offers a valuable model for any financial institution grappling with obsolete infrastructure.
Migrating a core banking system is not a simple technological update. It is a high-risk operation, as tragically demonstrated by the case of TSB Bank in the United Kingdom in 2026, where a migration attempt led to a veritable operational "meltdown," blocking customer access to their accounts for days. Yet, faced with competitive pressure and customer expectations for seamless digital services, this transformation has become a strategic necessity. Deloitte highlights in its 2026 outlook that banks must navigate macroeconomic headwinds, stablecoin disruption, and the rise of AI, which demands agile infrastructures.
This article analyzes Marginalen Bank's journey to extract practical lessons. We will examine their migration approach, identify common mistakes to avoid through counter-examples, and propose a decision-making framework to assess your own modernization project.
The Marginalen Bank Case: A Roadmap for Cloud Migration
Marginalen Bank's transformation, conducted in partnership with Mambu (cloud banking platform provider) and Avenga (system integrator), illustrates a methodical approach. According to reports from Avenga and Mambu, the project aimed to replace the old legacy core banking system with a fully integrated cloud-first architecture. Success rests on several key pillars:
- Complete Data Migration: The team ensured a comprehensive and secure transfer of historical data to the new platform, thus avoiding the creation of information silos.
- Microservices and Cloud-Native Architecture: The choice of Mambu allowed for the adoption of a microservices-based architecture, offering scalability and flexibility far superior to the old monolith.
- Total Integration: The new system was not deployed in parallel to the old one in a fragmented manner but replaced the entire core business in a unified ecosystem.
This approach contrasts with partial or "lift-and-shift" migrations that simply replicate the limitations of old systems in the cloud. OpenLegacy defines cloud modernization as the process of transforming legacy systems and applications to leverage cloud technology and architecture. Marginalen Bank applied this principle in depth.
Pitfalls to Avoid: The Bitter Lessons of Past Failures
To understand what worked at Marginalen, it is instructive to examine what failed elsewhere. The "Common Mistakes" section is crucial for any planner.
- Underestimating the Complexity of Data and Process Migration: The failure of TSB Bank (UK) is the archetypal example. As reported by Medium, the bank attempted to migrate its core banking system from an old owner (Lloyds) to a new platform (Sabadell) in a "big bang." The result was catastrophic: millions of customers locked out, erroneous transactions, and a lasting crisis of confidence. The lesson? A "big bang" migration without exhaustive testing and a solid rollback plan is extremely risky.
- Settling for "Re-hosting" (Lift-and-Shift) Without Architectural Redesign: Moving a legacy monolithic application to a VM in the cloud without rethinking it brings only marginal benefits (such as reduced hardware costs). The real gain – agility, time-to-market, personalization – comes from decomposition into microservices. Galileo Financial Technologies notes that the monolithic architecture of legacy systems makes them difficult to modify and integrate.
- Neglecting Specialized Expertise: As shown by Artezio's expertise in developing digital banking platforms, replacing a core banking system requires deep skills in financial architecture, regulatory compliance, and cloud engineering. Attempting to do it solely with internal resources can be perilous.
Decision Framework: Assessing Your Own Migration Path
Faced with a legacy system, several options are available. Here is a simple framework to assess yours, inspired by observed strategies.
| Strategy | Description | Advantages | Risks / Disadvantages | Suited for... |
| :--- | :--- | :--- | :--- | :--- |
| Re-hosting (Lift-and-Shift) | Moving the existing application to cloud infrastructure (IaaS). | Fast, minimal code changes. | Does not solve legacy architecture problems (lack of agility). | A temporary solution or for non-critical applications. |
| Refactoring (Replatforming) | Adapting the application to use managed cloud services (PaaS). | Improves operational efficiency without major redesign. | Limited gains in business agility. | Systems that function well but are costly to operate. |
| Complete Replacement (Rearchitecting/Replacing) | Rebuilding the application as cloud-native microservices or adopting a new platform (like Marginalen). | Maximum agility, scalability, innovation. | High cost and complexity, project duration. | Critical core systems that hinder innovation (the case in this article). |
| Hybrid or Progressive Approach | Deploying new services as microservices (e.g., payments) while maintaining the old core. | Reduces risk, allows for a gradual transition. | Creates integration complexity, maintains technical debt. | Large banks with very complex systems, as mentioned for PAOB in Hong Kong. |
To choose, ask yourself these questions: What is the business impact of stagnation? What is our appetite for risk and investment? Do we have the internal expertise or must we partner with a specialist like Avenga or Artezio?
The Strategic Imperative Beyond Technology
Marginalen Bank's migration was not an isolated IT project but a business transformation. In the landscape described by Deloitte for 2026, where banks must scale AI and combat data fragmentation, a legacy system is a ball and chain. A modern, flexible banking core becomes the necessary foundation to:
- Develop new financial products (like innovative interest-bearing accounts) quickly.
- Integrate partner ecosystems (fintechs, insurers) via APIs.
- Personalize the customer experience in real-time thanks to a unified and accessible view of data.
- Respond to regulatory requirements with greater agility.
The Marginalen case shows that a successful migration is possible with a clear vision, competent partners, and meticulous execution that avoids the pitfalls of poorly prepared "big bangs." It demonstrates that for a regional bank or any institution, the challenge is no longer whether to modernize its core banking, but how to do it in the safest and most effective way to unlock its future growth potential.
To Go Further
- Mambu and Avenga power Marginalen Bank's core banking transformation – The detailed account of Marginalen Bank's successful migration to a cloud-first architecture.
- A Blueprint for the Re-Platforming of Legacy Mainframe and AS/400 ... – An article analyzing, among other things, the failure of TSB Bank's migration as an instructive counter-example.
- 2026 banking and capital markets outlook | Deloitte Insights – Strategic trends and challenges for the banking sector in 2026, highlighting the need for agility.
- Cloud Modernization: Definition, Strategies, Tips + More - OpenLegacy – A definition and strategies for cloud modernization of legacy systems.
- Galileo Core Modernization – Upgrade Your Banking Infrastructure – A perspective on the challenges of legacy core systems and modernization pathways.
- Digital Banking Platform Development – Presentation of expertise in developing modern digital banking platforms.
- Core Banking Systems Market in China – Vendors, SIs, and Trends – Mentions a hybrid approach of deploying microservices alongside an old system, as for PAOB in Hong Kong.