In April 2026, Telangana’s MeeSeva platform transitioned from the proprietary Oracle database to the open-source PostgreSQL database, signifying a pivotal shift in the management of a crucial public-service platform that had been reliant on Oracle for approximately 15 years. This migration not only represents a technological upgrade but also serves as a potential blueprint for other governmental bodies aiming to cut down on recurring software costs.
Ravikiran Tirumala, the Commissioner of Electronic Services Delivery in Telangana, highlighted the financial implications of this move in a LinkedIn post, revealing that the annual costs associated with Oracle licensing and maintenance had reached around ₹10 crore. The migration to PostgreSQL is projected to eliminate this recurring expenditure, thereby reallocating funds towards more pressing public needs.
The initiative began in 2023, as the state sought to explore avenues for reducing its reliance on proprietary software licenses. Following extensive discussions across various government committees, the migration was successfully executed in April 2026. The technical intricacies of this transition were shared at the IndiaFOSS 2026 conference by Hari P Kiran, founder and CEO of OpenSource DB, who oversaw the migration process. Additionally, French database expert Gilles Darold, the creator of the Ora2Pg migration tool utilized in this project, documented the migration process, noting that the MeeSeva platform, which processes around 80,000 government-to-citizen transactions daily, experienced less than four hours of downtime during the transition.
Why does the move matter?
Government technology systems often have long lifecycles, and once applications and databases are established around a specific technology, transitioning away from it can be fraught with challenges. The MeeSeva platform offers over 500 services to citizens and businesses, and the migration encompassed more than 85 microservices, three Oracle servers, and 1,939 tables. The task was not merely to install PostgreSQL and deactivate Oracle; it required ensuring that all software components interfacing with the database continued to operate seamlessly.
Mr. Kiran emphasized the importance of maintaining data integrity and performance throughout the migration. Following the successful transition, he reported that MeeSeva had processed nearly 200 million transactions across 5,000 service centers, with no data loss or critical issues arising post-migration.
What is PostgreSQL?
Oracle Database, developed by Oracle Corporation, is proprietary software, whereas PostgreSQL is an open-source relational database that does not incur licensing fees. This distinction is crucial for Telangana, as the state identified Oracle licensing as a significant recurring cost. However, it is important to note that open-source solutions are not devoid of expenses; organizations still require infrastructure, skilled personnel, security measures, monitoring, backups, and ongoing maintenance.
The appeal of PostgreSQL for Telangana was not solely its lack of licensing fees but also the opportunity to decrease dependence on a single vendor while reducing overall costs. Mr. Kiran articulated this perspective during his presentation at IndiaFOSS, stating, “Every rupee spent on a proprietary database license is a rupee not spent on the public.”
What did the migration involve?
The migration process utilized Ora2Pg, an open-source tool designed by Mr. Darold, which automated approximately 60-70% of the transition. The remaining tasks necessitated manual intervention, including the adaptation of application code, data validation, and performance tuning. The team had to scrutinize Oracle-specific functions and rework various database constructs to ensure compatibility with PostgreSQL.
The migration was executed in phases, with the system initially writing data to both Oracle and PostgreSQL, allowing for validation of the new environment prior to the final switch. Ultimately, Oracle was decommissioned, and PostgreSQL became the primary database, with Mr. Kiran reporting zero incidents on the PostgreSQL database for two consecutive quarters following the migration.
How much did Telangana save?
The ₹10 crore figure referenced by Mr. Tirumala pertains to the annual costs associated with Oracle licensing and maintenance that Telangana will no longer incur. Mr. Darold corroborated this, estimating the previous Oracle expenses at approximately .2 million annually, while noting that the migration cost was below 0,000.
Was it risky?
The migration entailed considerable technical and administrative risks. Mr. Kiran mentioned that the project underwent multiple steering committee reviews due to the critical nature of MeeSeva, necessitating assurance to government officials that the transition would not disrupt citizen services. Remarkably, the migration was completed with less than four hours of downtime, a period during which MeeSeva services were temporarily unavailable.
The new architecture was designed with automatic failover capabilities, targeting a recovery time objective of approximately 30 seconds. This means that in the event of a primary database failure, the system can seamlessly switch to a backup, ensuring minimal disruption. Rather than simply replicating the existing Oracle architecture, the team opted to redesign and consolidate elements of the database architecture to optimize performance within the PostgreSQL environment.
What does this mean for other governments?
The experience of Telangana does not imply that all government systems currently operating on Oracle can be effortlessly transitioned to PostgreSQL. Mr. Kiran noted that some MeeSeva services lacked staging environments, complicating conventional testing. Consequently, the team had to simulate production conditions and conduct extensive validation prior to the final cutover, along with having a rollback plan in place should the migration encounter issues.
This case illustrates the complexities involved in reducing reliance on proprietary technology after years of use, offering insights into the challenges and considerations that other governments may face in similar endeavors.
Could open source become a government cost-cutting tool?
Eliminating proprietary database licensing fees can indeed lead to reduced recurring technology expenditures. However, the overall economics must be assessed throughout the system’s lifecycle. Migration incurs costs, and open-source systems necessitate skilled personnel, infrastructure, and ongoing support and maintenance. The risks associated with transitioning a mission-critical system must be weighed against the costs and risks of remaining with existing technology.
Mr. Kiran advocates for governments to scrutinize their recurring proprietary software expenses and evaluate whether open-source alternatives could fulfill the same functions. He pointed out various government systems—such as land records, taxation, pensions, transportation, health, education, and citizen portals—as areas where proprietary database licenses contribute to ongoing costs.
Ultimately, the lessons from Telangana may extend beyond merely replacing proprietary software with open-source options; they may prompt governments to reconsider the value of proprietary technology in light of its recurring costs and vendor dependencies.
