From Oracle to Postgres for 40 Million Users: What a National G2C Migration Actually Looks Like
October 20–23
Telangana's MeeSeva platform delivers over 500 government services to 40 million citizens across India's sixth-largest state. This April '26, we migrated the entire stack from Oracle to PostgreSQL, not as a pilot, not in parallel, but as a full production cutover for a system handling 100K transactions per day.
This talk is a practitioner's account of how that migration happened, what broke, and what we'd do differently.
I'll cover: - How we assessed Oracle-specific dependencies (PL/SQL packages, materialized views, proprietary datatypes) and scoped the migration - What Ora2Pg handled automatically, what required manual rewriting, and where its limitations forced architectural decisions; the performance tuning we did post-migration, query plan differences, index strategy changes, and connection pooling adjustments for PostgreSQL - How we managed the cutover for a 24/7 citizen-facing service with zero tolerance for downtime; and the measurable outcomes: licensing cost reduction, operational changes, and where PostgreSQL exceeded or fell short of Oracle.
The talk is tool-agnostic and vendor-neutral. Whether you're migrating a government platform, a financial system, or an enterprise ERP, the patterns, dependency analysis, automated-vs-manual conversion ratios, performance regression testing, cutover planning, are the same. I'll share the decision frameworks, not just the results.
