GeekyAnts migrated one of India’s largest banks from .com to .in during a code freeze
RBI deadline. Code freeze. Peak traffic. See how GeekyAnts executed a seamless .com to .in migration for one of India’s biggest banks.
Author
Subject Matter Expert
Date
Book a call
Table of Contents
Background Information: On February 7, 2025, the RBI mandated that banks migrate to the new domain framework before the October 31 deadline. The bank’s internal release policy restricted major changes until after Diwali in October, compressing the execution timeline. Here’s how the migration was delivered on time — without disrupting a single transaction.
Getting the exception approved
A code freeze is a commitment. To get one approved at a bank of this scale, you need to demonstrate that the change carries less risk than leaving it undone.
Discovery before the freeze started
- A full audit of 100+ external partner integrations and their domain dependencies.
- Domain segmentation: specialist teams assigned to critical product areas such as the Loans Expressway, where user journeys had unique architectural dependencies that a generic migration approach would have broken.
2 AM deployments and what they covered
The technical scope covered five categories:
What changed during the migration windows
- Backend microservices: environment variables and base URLs updated to reference the .in domain.
- Infrastructure: Ingress rules updated to accept .in traffic into the pods. SSL/TLS certificates are provisioned to prevent browser security warnings.
- Firewall layers: WAF rules updated across AWS WAF, Nginx, and Palo Alto to allow traffic from the new domain.
- CDN and cache: old .com references purged. CDN reconfigured to serve exclusively from the .in origin — required to ensure Diwali offer pages served accurate, fresh content.
- SEO continuity: 301 redirects implemented from .com bookmarks and indexed URLs to .in equivalents. CORS policies updated to allow API calls from the new domain.
- Identity systems: Keycloak and internal email infrastructure migrated to .in.
The trust problem: telling customers before they notice
What the migration actually required
The code freeze added a constraint that forced every decision to be made in advance. There was no room to discover a missed WAF rule at 3 AM during Diwali week. The discovery phase and the segmentation of teams by domain were the risk controls that made the nocturnal execution possible.
As a result, the bank met its RBI compliance deadline. No customer transaction was interrupted during the festive period. The domain change was invisible to end users.
Three things that made this work
1. Discovery before the constraint hit
The 100+ partner audit and the domain segmentation happened before the freeze. By the time the deployment windows opened, there were no unknowns left in the scope.
2. The deployment window as a forcing function
Working in 3-hour nocturnal windows with no room for incident response concentrated the team’s planning. Every step was scripted, every rollback condition defined, before the first change went live.
3. Communication ran ahead of the technical change
About this Project
The migration was executed by GeekyAnts in partnership with the bank’s internal engineering and compliance teams. The work spanned infrastructure, security, CDN, identity, and product communications. If you are working through a comparable constraint — regulatory deadline, legacy system dependency, or a change that cannot go wrong during a peak period — the approach documented here is one we have tested and delivered under production conditions.
Related Articles.
More from the engineering frontline.
Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
Mar 17, 2026
AI PODs: Bridging the 6-Month Gap Between Prototype and Production
Most AI projects stall between PoC and production. AI PODs close the execution gap with specialist teams, cost control, and production-ready delivery.
Mar 3, 2026
Why Fast Pipelines Fail to Deliver Fast Releases
Why do fast pipelines fail to deliver fast releases? Uncover the leadership, operational, and cultural shifts that drive consistent release velocity.
Feb 27, 2026
Building a Smart Healthcare CRM Platform for hospitals: AI Engagement, Operational Efficiency & Compliance
Healthcare CRM development for modern hospitals with AI-driven patient engagement, real-time EHR integration, operational efficiency, audit-ready compliance, and measurable ROI.
Feb 27, 2026
While Most ERP Upgrades Fail, How U.S. Enterprises Get Them Right
Given the high 70% failure rate of ERP modernization projects, this guide examines the financial, compliance, and strategic triggers for U.S. enterprises to modernize. Learn the critical steps—from data cleansing and composable design to people-centric change management—to ensure a successful migration and unlock AI-driven growth.
Feb 18, 2026
Integrating BNPL Rails Into Legacy US Bank Cores Without Risk
Learn how US banks integrate BNPL rails into legacy cores using the Strangler Pattern, microservices, and compliant AI without outages or rewrites.
Feb 17, 2026
Cloud ERP Integration with AI Process Automation: Real-Time Decision-Making for US Companies
Modernize your enterprise with Cloud ERP and AI process automation. This guide explores using Event-Driven Architecture and Agentic AI to reduce "time to decision," cut costs by 80%, and enable continuous financial close. Follow our 30/60/90-day implementation roadmap to transform static records into real-time operational insights.