Table of Contents
Banks across India and globally are moving to the cloud with the same pitch in their slide decks: lower cost, faster innovation, modern infrastructure. The outcomes are telling a different story. Only one in three financial services firms report satisfaction with post-migration operating costs. More than six in ten cloud migration projects come in materially over budget.
Banks across India and globally are moving to the cloud with the same pitch in their slide decks: lower cost, faster innovation, modern infrastructure. The outcomes are telling a different story. Only one in three financial services firms report satisfaction with post-migration operating costs. More than six in ten cloud migration projects come in materially over budget.
The gap is not about cloud being the wrong destination. It is about how banks are getting there. The dominant strategy, lift-and-shift, looks like the safest path on paper. In practice, it is quietly becoming the most expensive mistake in BFSI technology spend today.
The destination is right. The route is wrong.
You Cannot Move Broken Systems to Expensive Infrastructure and Call It Transformation
The lift-and-shift pitch is hard to argue with in a steering committee. Take your existing systems, move them to AWS or Azure exactly as they are, no redesign, no refactoring. Fast timelines. Minimal disruption. A clean line item that says the bank is now on the cloud.
The reason it keeps disappointing is structural, not tactical. A lift-and-shift treats the cloud as a cheaper data centre. It is not. The cloud is a different economic model, billed by the hour, priced for elasticity, optimised for services you redesign your applications to consume. If you carry your legacy architecture across without changing it, you inherit every inefficiency you already had and start paying premium rates to host it.
Join Our Newsletter
Get exclusive insights on banking, fintech, regulatory updates and industry trends delivered to your inbox.
You Built for the Worst Day of the Year. Now You Are Paying for It Every Hour.
Most BFSI data centres were sized for peak. The IPO listing day. The festival weekend. The salary credit cycle. That logic made sense on-premises because the cost of overprovisioning was sunk capital. Servers sat at twelve to eighteen percent utilisation on a normal Tuesday and nobody got a bill for the idle capacity.
Lift those same workloads into the cloud without redesigning them and the economics invert. The idle capacity is now metered. You are paying hourly for peak-sized infrastructure that runs at a fraction of utilisation, with none of the elasticity that should have made the cloud cheaper in the first place. It is the worst of both worlds: capex discipline replaced by opex sprawl, with no compensating gain in agility or resilience.
Renting expensive hardware you do not need, with no ability to scale down, is not a cloud strategy. It is a procurement decision dressed up as transformation.
Lift-and-Shift Is One Option of Four. It Should Rarely Be the Default.
The strategic question is not whether to migrate. It is what each workload deserves. A bank’s application portfolio is not uniform, and a serious modernisation programme stops pretending it is. There are four credible routes, and most banks should be using all of them, sequenced deliberately.
The mistake is not picking rehost. The mistake is picking rehost for everything because it is the easiest conversation to have with the board. A portfolio approach forces a harder conversation, and that is precisely why it works.
They Move Slowly Where It Matters and Quickly Where It Does Not
The institutions getting cloud economics right start with an audit that most banks skip. Which systems carry strategic weight. Which are commodity utilities. Which are blocking innovation. Which are stable enough that touching them is more risk than reward. That triage decides the route for each workload, not a blanket migration mandate.
They then sequence carefully. Rehost what is genuinely fine. Replatform what needs efficiency. Rearchitect the few systems that determine competitive position. The cost curve looks worse in year one and meaningfully better by year three, because every additional workload moved this way reduces marginal cost rather than increasing it.
The other thing they do, which is easy to miss, is treat modernisation as a launchpad rather than a finish line. The cloud-native data platform is what makes AI usable. The refactored customer journey is what allows embedded finance partnerships. The managed services layer is what cuts the regulatory reporting cycle from weeks to days. None of that is reachable from a lift-and-shifted estate.
The Direction Is Clear. What Varies Is How Prepared Each Player Is to Act on It
Taken as a whole, the Master Direction is a considered piece of regulation. It does not try to slow the industry down. It tries to put the right structure around a segment that has grown very fast and, in some areas, outpaced the oversight that should have come with it. The approach to small merchant onboarding shows that the RBI is thinking about inclusion alongside risk, which matters for how the next phase of payments growth actually plays out.
For physical PAs, the December 31, 2025 deadline for authorization is the immediate pressure point. Meeting the net worth requirement, putting governance frameworks in place, and building the agent monitoring systems that simplified due diligence demands none of that happens quickly. Teams that start now will be better placed than those that treat this as something to deal with later.
And in the medium term, the institutions that get their compliance foundations right are the ones that will be able to move faster on the commercial opportunity. A more trusted, better regulated merchant ecosystem is good for everyone operating in it, including the aggregators that helped build it.
The Right Question Is Not How Fast. It Is What Architecture
Cloud migration in BFSI has been framed as an infrastructure project for too long. Procurement timelines, vendor contracts, data centre exits. The framing is what produces lift-and-shift as the default answer, because that is the shape of question being asked.
The banks pulling away from the pack are running a different conversation at the top. What architecture makes us faster on credit decisions, more compliant by default, more profitable per customer, more ready for the next regulatory shift. Cloud is one input into that answer. It is not the answer.
Moving problems to someone else’s server and paying by the hour for the privilege is not transformation. It is a more expensive version of the system you wanted to leave behind. Redesign or regret. There is no third option that survives a finance review at year three.
Rethinking Your Cloud Strategy?
Cloud migration should create business value, not just bigger bills. We work with banks, NBFCs, and fintechs to make sure technology investments deliver measurable outcomes.
