How a Leading Indian Insurance Provider Modernized a 20TB Workload and Eliminated Oracle Licensing Costs

Overview

A leading Indian insurance provider was dependent on a complex, 20TB Oracle database setup. This dependency caused high enterprise licensing costs and limited cloud-native scalability. Mydbops led the modernization to Amazon Aurora PostgreSQL using AWS DMS. By converting 2,000+ tables and rewriting hundreds of complex code objects, the client successfully achieved zero Oracle licensing costs and established a highly scalable database setup without disrupting daily insurance operations.

↑

↓

100%

License Cost Savings

Eliminated enterprise Oracle licensing fees

↑

20TB

↓

Data Migrated

Successfully migrated a critical transactional dataset.

2.68 Billion

↑

↓

High-Speed Migration

Migrated in 4 hours to minimize cut-over downtime.

Zero

↑

↓

Vendor Lock-in

Transitioned completely away from proprietary contracts

Oracle

Consulting Services

About

The client is a major Indian insurance provider managing millions of active policyholders and claims nationwide. Operating at an enterprise scale, their daily policy administration, underwriting, and customer service workflows are powered by a high-volume database setup spanning nearly 20 Terabytes of active data. This critical platform processes billions of database records across more than 2,000 tables to support continuous, always-on transactional operations.

★★★★★

I would like to extend my sincere appreciation to your team for the support provided during the data migration and conversion activities for our AWS MAP 2.0 project for our Insurance company. Your contribution across Oracle to PostgreSQL migration, schema conversion, migration execution, and overall technical collaboration played an important role in helping us successfully complete this phase of the program. The partnership demonstrated by your technical team throughout the migration activities, particularly while navigating various migration complexities and environment-specific challenges, is acknowledged and appreciated.

Project Lead (Confidential)

AWS MAP 2.0 Database Modernization Program

Deployment Type

Database Stack

Outcome

Cloud-Based Deployment

Migration from Oracle to Amazon Aurora PostgreSQL

100% Elimination of Oracle Enterprise License Costs

Deployment Type

Cloud-Based Deployment

Database Stack

Migration from Oracle to Amazon Aurora PostgreSQL

Outcome

100% Elimination of Oracle Enterprise License Costs

Business Challenges

Overview

The client's Oracle environment supported core insurance operations. They needed to move to a modern, cloud-native platform while ensuring that existing application logic, data integrity, and operational workflows continued to function as before.

Platform Dependency: Strong reliance on Oracle-specific features and scheduled jobs caused high vendor lock-in and expensive licensing fees. These costs limited the budget for creating new databases and writing new features.

‍Scale and Complexity: Managing a footprint of over 2,000 tables and 20TB across multiple business modules meant any migration carried real risk to business continuity and data integrity.

‍Code Conversion Obstacles: Oracle PL/SQL logic could not simply be transferred. Hundreds of views, materialized views, and procedures required a complete rewrite to function in PostgreSQL.

‍Cut-over Downtime Risks: Standard migration methods for a 20TB dataset would cause extended downtime, which was not feasible for an active customer-service and underwriting platform.

Goals

The key objectives the client was aiming to achieve:

→ Eliminate Oracle enterprise licensing fees to redirect budget to new development. 

→ Migrate the 20TB legacy database to a managed Amazon Aurora PostgreSQL environment. 

→ Preserve application logic and operational workflows without disruption. 

→ Complete the migration with minimal operational downtime. 

→ Set up a scalable, cloud-native foundation for future growth.

Risks if Not Addressed

If left unresolved, these challenges posed serious risks

Risks & Impact if Not Addressed

Performance Issues

Without resolving replication lag and fragmented tables, query performance would continue to degrade, leading to a frustrating customer experience during peak hours.

Business Continuity Risks

Non-standardized backup policies increased the risk of data loss and prolonged outages, potentially disrupting thousands of orders in real-time.

Revenue Loss

Poor performance and downtime during peak times directly impacted Swiggy’s ability to fulfill customer demand, resulting in lost revenue and dissatisfied users.

Escalating Costs

Continued reliance on oversized, under-optimized infrastructure would lead to unnecessary monthly spend, straining the company’s profitability.

Developer Inefficiency

Lack of a stable and scalable database foundation meant developers spent significant time firefighting performance issues instead of innovating on features.

Performance Issues: Replication lag and fragmentation slow order searches and transactions.
Business Continuity Risks: Non-standardized backups mean longer recovery times and higher data-loss risk.
Revenue Loss: Slow page loads or timeouts during peak hours lead to failed checkouts.
Escalating Costs: Over provisioned, under-optimized servers strain profitability
Developer Inefficiency: Engineers spend more time firefighting than building new features

Goals

The key objectives the client was aiming to achieve:

→

[Goal 1]

→

[Goal 1]

→

[Goal 1]

Solution Provided by Mydbops

Mydbops acted as the migration partner, delivering an end-to-end program focused on risk reduction, code conversion, and business continuity. The new architecture was built on Amazon Aurora PostgreSQL, providing a managed, highly available platform.

▸ Audit and Assessment:

Analyzed the 20TB database, mapping dependencies for 2,000+ tables and identifying exact conversion needs for the business logic.

‍

▸ Code and Schema Migration: 

Rewrote 265 views, 7 materialized views, and about 165 procedures from Oracle PL/SQL to PostgreSQL logic. Legacy Oracle scheduled jobs were moved to native pg_cron jobs.

‍

▸ Parallel Data Loading: 

Resolved data volume challenges by splitting data using primary-key ranges. This module-wise strategy allowed the team to load data concurrently, reducing the migration timeline.

‍

▸ CDC-Based Synchronization: 

Used AWS DMS for Full Load plus Change Data Capture (CDC). This kept the target Aurora PostgreSQL environment synchronized with the Oracle source until the final cut-over, ensuring zero data loss.

Oracle Source

20 TB Source Volume
2,000+ Tables
PL/SQL DB Triggers
Legacy Scheduled Jobs

Extract

AWS DMS Layer

PK Range Splitting
Parallel Loading
CDC Synchronization
Consistency Validation

Load

Aurora Target

Aurora PostgreSQL
Rewritten Core Logic
Native pg_cron Jobs
Highly Available Stack

Results and Impact

Key Outcomes

✅ 100% Elimination of Oracle Licensing Costs

‍Removing proprietary software licenses directly freed up the budget needed to build new databases and write new features.

‍

✅ Modernization of 20TB of Data

‍Successfully transferred a large dataset supporting policy, underwriting, and claims to a cloud-native platform, improving operational efficiency.

‍

Operational Areas	Legacy Oracle Setup	Mydbops Aurora PG
Licensing Model	Expensive enterprise licensing fees with high vendor lock-in.	✓ Cost-effective cloud-managed setup with zero licensing fees.
Innovation Agility	New development blocked by high cost commitments on software licenses.	✓ Budget freed up to focus on application logic and feature additions.
Job Scheduling	Dependent on proprietary, Oracle-specific scheduling features.	✓ Clean cloud operations with native, open PostgreSQL pg_cron scheduling.
Scalability	Rigid architecture demanding heavy manual capacity provisioning.	✓ Managed cloud architecture supporting highly scalable operations.

‍

✅ Preserved Business Logic

Converted over 437 database code objects and managed 2,000+ tables. The application's core logic continued to function accurately, resulting in zero impact on daily operations.

‍

✅ Reduced Migration Window

‍By utilizing primary-key-based range splitting, Mydbops migrated 2.68 billion (268 crore) records for a single large table in 4 hours, lowering operational risk.

Core Big Table

Oracle DB

2.68B Rows

DMS Run 1 (Concurrent) PK: 1 - 670M

DMS Run 2 (Concurrent) PK: 671M - 1.34B

DMS Run 3 (Concurrent) PK: 1.35B - 2.01B

DMS Run 4 (Concurrent) PK: 2.02B - 2.68B

Target Engine

Aurora PostgreSQL

Loaded in 4 Hours

A Partner You Can Trust

‍For organizations running large data environments, the main challenge is finding a reliable partner to manage the transition safely.

Mydbops provides the technical database expertise needed to handle complex migrations. From cost reduction to cloud operations, we ensure your migration is cost-effective, secure, and aligned with your business demands.

Consult with a Migration Expert

Consult with a Migration Expert →

Need Expert Database Solutions?

Talk to a Database Expert Today!

Database solutions are provided by mydbops expert team

Mydbops set up High Availability (HA) Solutions with InnoDB or Percona Clusters, ensuring continuous uptime and fault tolerance.

Thank You!

We’ve got your request, our expert team will be contacting you shortly.

Oops! Something went wrong while submitting the form.