Migrating Your Core to the Cloud Without Downtime

Almost every bank already uses the cloud for something. For the core, almost none. That gap isn't chance: it's fear, and it has a name. It's called downtime.

The figure is telling. Although more than 90% of financial institutions have already adopted the cloud for some workload, barely around 3% of core workloads—the back-end, the ledger, what actually holds the bank up—had migrated, according to a study by Harvard's Program on International Financial Systems. The core is the last frontier. And the barrier isn't technical or regulatory in the first instance: it's the perfectly rational terror that the system running 24/7 will go down during the move.

In the region the lag is greater. In Latin America, 68% of large banks have a formal cloud strategy—below North America's 91%—according to Accenture, and close to 60% of banking cores still run on legacy technology, per Finnovista as reported by Galileo. Fear of downtime keeps much of banking trapped in systems that no longer suffice.

The fear is justified: what happens when it goes wrong

It's not an invented ghost. In 2018, the British bank TSB tried to migrate its core and it went so badly it left close to two million customers without access to their money for weeks. The final tally: more than 225,000 complaints, a loss close to £330 million, 80,000 customers who left, and a regulatory fine of £48.65 million for risk-management failures, as Computer Weekly reported. Migrating the core badly can cost more than not migrating it. That's why the right question isn't whether to migrate, but how to do it without a single blackout.

You can migrate without downtime: how

The good news is that "switch off the old, switch on the new"—the weekend cutover—is no longer the only path, and in fact it's the most dangerous. The approaches that work for systems that can't stop share one idea: coexistence and gradual migration.

• Parallel run (dual-run). The old and new systems operate at the same time with the same data. The old one handles real traffic while the new is validated in the background, until it proves it balances exactly the same.

• Change data capture (CDC). Instead of the fragile "dual write," changes from the old core are replicated to the new in real time, keeping them synchronized throughout coexistence. It's the consensus method for moving data without switching off.

• Blue-green and canary. Either you have two identical environments and switch traffic in a controlled way, or you promote users to the new system little by little, measuring at each step. And always with the rollback door open.

A dose of realism is in order, because the uncomfortable part must be said too: these programs take time. A 2025 EY analysis found that parallel-run periods often stretch 12 to 24 months beyond the estimate. Doing it without downtime is possible; doing it in a weekend is not. Anyone who promises you the latter is selling you the TSB risk.

What the CNBV will ask of you (and is worth knowing first)

In Mexico, migrating the core to the cloud isn't just a technical decision; it's a regulated one. The Banking Single Circular requires prior CNBV authorization to contract cloud services with third parties located outside the country, and its Annex 52 sets minimum operating and security requirements. The framework calls for vendor due diligence, operational continuity and recovery plans, audit rights and—crucially—data portability: being able to migrate to another provider or back to your own premises. Article 328 adds that the provider must reside in a jurisdiction whose laws protect personal data. Designing the migration while ignoring this means crashing into the regulator mid-project.

It's worth it: the other side of the scale

The fear is real, but staying isn't free either. McKinsey estimates the cloud can add around 5 points of EBITDA in banking, with much of the value coming from greater IT resilience, in its analysis of the global value of the cloud, plus elasticity for variable demand and lower cost of experimenting. An honest caveat: that value doesn't arrive just from "being in the cloud"—McKinsey itself documents banks that took months to provision infrastructure for lack of automation. The cloud enables; what captures the value is how you implement it.

How we see it at WAU

At WAU we migrate cores to the cloud with operations running: parallel run, real-time change capture, parity validation, and rollback always available—with the CNBV regulatory route mapped from day one, not discovered halfway. We don't sell weekend cutovers; we build transitions your customers don't notice.

If your core needs the cloud but fear of downtime has you stuck, let's talk. We'll show you how it's done without switching anything off. 👉 Book a conversation with our team.

Sources

• PIFS (Harvard) — Cloud Adoption in the Financial Sector and Concentration Risk (2023)

• Accenture — The ultimate guide to banking in the cloud (cloud strategy by region)

• Galileo — Core Banking Modernization in Latin America (Finnovista figure)

• Computer Weekly — TSB hit with huge fine after IT migration disaster (2022)

• EY — Core banking technology modernisation: what's next? (Oct 2025)

• CNBV — Annex 52 of the Banking Single Circular (minimum operating and security guidelines)

• McKinsey — Projecting the global value of cloud (5 points of EBITDA in banking)