← Back to case studies

Case study / Walmart Global Tech India

Role period: Dec 2023 – Jun 2025

Migrating 7.5M production users and enabling SSO

Moving millions. Keeping identity connected.

A production-user migration, a new database, and a more connected sign-in experience across global markets.

Role

Senior Software Engineer · IAM Team

Scope & ownership

Production identity migration across multiple global markets, including SSO and legacy authentication issues.

Tools & practices
  • Data migration
  • SSO
  • Distributed systems
7.5M

production users migrated

Total production user identities migrated to a new database.

The context

Identity infrastructure sits on a critical path: it connects people to the systems they use. The WCP initiative brought production users onto a new database while addressing legacy authentication issues and enabling single sign-on.

My contribution

  1. 01

    Led the migration of 7.5 million production users to a new database.

  2. 02

    Designed and executed migration strategies for multiple global markets.

  3. 03

    Helped achieve SSO and resolve legacy authentication issues.

  4. 04

    Coordinated sprint planning, resources, and reporting with senior management.

Constraints & scope

  • Production user identities across multiple global markets.
  • A database transition coupled to SSO and legacy authentication behavior.

Evidence & validation

Reported outcome

  • 7.5 million production user identities migrated; SSO enabled and legacy authentication issues addressed.
Evidence boundary

The delivered scope and outcome are based on my professional experience. Internal benchmarks, production topology, rollout records, and alternative evaluations are not published here. The engineering considerations below describe how I reason about this class of system; they do not assert undisclosed implementation details.

How I would evaluate this system

  • Reconcile identity counts and stable identifiers by market; investigate mismatches before advancing.
  • Compare sign-in error rates and latency through a staged rollout, with explicit stop and recovery criteria.
  • Validate session and authorization behavior independently of migration throughput.

Technical analysis

Engineering considerations for this class of system. The delivered work is described in the contribution and implementation sections.

Migration progress and correctness are different signals

Moving records establishes progress; matching identity coverage and authentication behavior establishes correctness. For this class of migration, compare record reconciliation with sign-in success, error trends, and a clearly defined recovery boundary. A rollout should advance because evidence supports it, rather than because a batch completed.

Google SRE: evaluating a staged rollout (opens in a new tab)

Keep the identity contract explicit

SSO connects authentication, authorization, and session behavior. Review which identifiers remain stable, how existing sessions behave during a transition, and which authorization guarantees must survive the database change. OAuth security guidance is relevant when OAuth is part of the identity flow; it does not establish which protocol this project used.

IETF: OAuth 2.0 security best practices (opens in a new tab)

System overview

An illustrative migration path
01Production users
02Migration
03New database
04Connected identity
An illustrative migration path

A production migration changes a live service, not just data at rest. Coordinating the transition across markets and keeping authentication connected are important parts of the engineering problem.

Results

7.5 million production users migrated, with SSO enabled and legacy authentication issues addressed.

Next case study / CommerceIQ

Planning in motion