Skip to main content
Celestibia Solutions

Banking CRM Migration from Private Cloud to Microsoft Azure

An Indian private-sector bank’s core banking CRM moved to Azure Kubernetes Service with geo-replicated DR: 25% cost savings, 30-minute RTO, RBI compliant.

Discuss a similar project
  • Migration
  • Banking & Financial Services
  • India
  • Microsoft Azure
Legacy private cloudCore CRMCRMAPIDatamigration wavesAzure primary regionFront Door, AKS, Azure SQLAzure standby regionSQL geo-replicageo-replicationRTO 30 minutesRBI requirements met
Workloads move from the private cloud into Azure in waves; the database replicates to a standby region.
cost savings
25%
recovery time objective achieved
30 min
compliance requirements met
RBI

At a glance

Engagement
Migration
Industry
Banking & Financial Services
Platform
Microsoft Azure
Region
India
Client
Leading private-sector bank, name withheld
Technologies
5 in the delivered stack

Services delivered

Before and after

The bank’s core banking CRM ran on a legacy private cloud with frequent outages. Reserve Bank of India (RBI) requirements meant the platform needed high availability and data residency, and the existing environment could not scale for month-end peaks.

Before

  • More than 200 microservices had to move without disrupting a regulated, customer-facing system.
  • Disaster recovery had to meet a defined recovery time objective while keeping data in-country.
  • Network security had to be enforced at the edge and between services.

After

  • 25% cost savings
  • 30 min recovery time objective achieved
  • RBI compliance requirements met

The solution

Solution path

  1. Legacy private cloud
  2. Azure Front Door
  3. Azure Kubernetes Service
  4. Azure SQL geo-replicated

How it was delivered

  1. Phase 1

    Lift-and-shift of 200+ microservices to Azure Kubernetes Service (AKS).

  2. Phase 2

    Azure SQL with geo-replication for disaster recovery.

  3. Phase 3

    Azure Firewall and Azure Front Door for perimeter and application security.

Technology stack

  • Azure Kubernetes Service
  • Azure SQL
  • Geo-replication
  • Azure Firewall
  • Azure Front Door

Questions about this project

Which Azure services were used in the banking migration?

The microservices were moved to Azure Kubernetes Service, data to Azure SQL with geo-replication for disaster recovery, and the perimeter was secured with Azure Firewall and Azure Front Door.

What recovery time did the bank achieve after migration?

The migrated platform achieved a 30-minute recovery time objective (RTO), alongside 25% cost savings and RBI compliance.

Related services

Cloud Consulting ServicesStrategy, architecture, migration and managed infrastructure across AWS, Azure and GCP.Managed Kubernetes ServicesDesign, security, upgrades and operations for EKS, AKS and GKE clusters.Cloud Disaster Recovery & Business ContinuityRTO/RPO design, backup, replication and tested failover across clouds.Cloud Security ServicesAssessments, IAM hardening, posture management, VAPT and compliance automation.

Related technical articles

Case study · InsightsSecure Banking Application Migration from Private Cloud to Microsoft Azure (opens on insights.celestibia.com)Technical article · InsightsTop 15 Cloud Security Best Practices to Prevent Data Breaches in Production (opens on insights.celestibia.com)

Planning something similar?

Whether you're migrating, cutting costs, securing your infrastructure or exploring startup programs, start with the Cloud Readiness Survey.

Discuss your projectMore case studies

What happens next

  1. Answer six questions about your cloud setup, spend and priorities. It takes about three minutes.
  2. A Celestibia engineer reviews your answers within one business day.
  3. You get tailored recommendations and the AWS programs you are likely to qualify for.

Monday to Friday, 10 AM to 7 PM IST