Airlines
Wipro · LATAM
India · December 2025
Oracle to Cloud SQL PostgreSQL — LATAM Airlines CROAMIS modernization with 98% automation
South America’s largest airline group successfully migrated its mission-critical CROAMIS module — a 17 TB Oracle database with over 10 million Java lines of code — to Cloud SQL PostgreSQL on GCP. Powered by Newt Global’s DMAP platform, the migration achieved 98% automation, optimized the database to 7 TB, and completed at record speed without disrupting airline operations.
Oracle → Cloud SQL PostgreSQL
17 TB → 7 TB
98% Automation
10M+ Java LOC
DMAP
Google Cloud Platform
Customer
LATAM Airlines Group S.A. via Wipro Limited
- Industry
- System integrator
- Primary Location
- Migration
- Source DB size
- Optimized DB size
- Automation achieved
- Published
- Airlines
- Wipro Limited
- India
- Oracle → Cloud SQL PostgreSQL
- 17 TB
- 7 TB
- 98% via DMAP
- December 25, 2025
Source Oracle database size across 29 schemas
Automation delivered by DMAP for schema & SQL remediation
Java lines of code remediated for Cloud SQL compatibility
Optimized database size post-migration on GCP
Background
LATAM Airlines Group S.A. is the largest airline group in South America and one of the largest globally by passengers transported, operating both passenger and cargo businesses across the continent and beyond. Wipro Limited, a global systems integrator headquartered in Bengaluru, India, serves as LATAM’s strategic technology partner — and engaged Newt Global to lead the Oracle modernization initiative.
The target system, CROAMIS, is one of LATAM’s most critical operational modules — deeply embedded in the airline’s day-to-day operations. Migrating a system of this scale and complexity to Google Cloud SQL PostgreSQL required an approach that could handle massive data volumes, thousands of code objects, and intricate inter-schema dependencies — all without disrupting live airline operations.
The challenge
Prior attempts at manual code conversion had already been made before Newt Global was engaged — yet the project remained stuck. Runtime failures caused by dynamic SQL and fundamental Oracle–PostgreSQL compatibility differences continued to block progress. The project needed a structured, systematic approach to overcome these barriers within a tight delivery window.
Key obstacles
- Dynamic SQL in the application code resisted standard conversion tooling available in the market
- Deep Oracle-specific constructs (procedural logic, data types, and SQL dialects) incompatible with PostgreSQL/AlloyDB
- 4.6 million lines of Java and NodeJS code requiring systematic remediation at scale
- 40+ team members spread across 5 time zones, demanding rigorous program management
- No proven end-to-end toolchain existed for a migration of this scope and complexity
The solution
Newt Global was brought in during the last week of June 2024. The team immediately introduced the Cloud Migration Cockpit — a structured, transparent framework that provided a clear migration path with defined phases for database, data, and application conversion. This gave all 40+ team members across time zones a shared operational picture from day one.
DMAP-powered SQL conversion
Newt used DMAP to identify and convert unresolved dynamic SQLs within the application code — the core blocker that had stalled previous efforts. DMAP automated the conversion of remaining schema objects, eliminating manual guesswork.
DB schema & data migration validation
Database schema and data migration were validated end-to-end using DMAP's built-in validation framework, ensuring parity between Oracle and AlloyDB throughout the process.
Comprehensive cutover plan
The cutover strategy covered initial data load, Change Data Capture (CDC) for continuous sync, and Reverse CDC (rollback) capability — ensuring a safe, recoverable production transition with no data loss risk.
Controlled program management
Focused governance on Go Live and Day 2 operations ensured a smooth transition. The team worked through weekends alongside Hughes's engineers to hit every milestone — adapting numerous interfaces and shell scripts for AlloyDB compatibility.
The result
The Hughes ECOM application and its associated Oracle databases were seamlessly migrated to AlloyDB within 12 weeks — a timeline that many considered impossible given the scale and complexity of the system. The project was tested rigorously across four environments before production cutover, with all interfaces and shell scripts adapted for full AlloyDB compatibility.
12 wks
Full Oracle to AlloyDB production cutover, end to end
4.6M LOC
Java and NodeJS code successfully remediated and validated
4 envs
Rigorous pre-production testing environments validated before go-live
Zero
Data loss at cutover with CDC and Reverse CDC rollback safety net
The success of this first step — internally named TelecomVera — gave Hughes immense confidence in their ability to modernize further workloads on Google Cloud. The project set a new internal benchmark for enterprise Oracle migrations at scale.
Technology stack
Oracle Database
AlloyDB for PostgreSQL
Java
NodeJS
DMAP
Cloud Migration Cockpit
CDC (Change Data Capture)
Reverse CDC
Google Cloud Platform
Key outcomes
- Production cutover achieved in 12 weeks
- 4.6M lines of Java/NodeJS code remediated
- All Oracle databases migrated to AlloyDB
- Four test environments validated before go-live
- Interfaces and shell scripts adapted for AlloyDB
- CDC + Reverse CDC rollback plan executed flawlessly
- 40+ cross-timezone team coordinated seamlessly
About Hughes Network Systems
A Fortune 500 company and leader in networking technologies and services, Hughes enables essential connectivity for communities, businesses, and governments worldwide. Named a Leader in the 2023 Gartner® Magic Quadrant™ for Managed Network Services.
About Newt Global Consulting
A leader in both heterogeneous and homogeneous database migration with application remediation. Newt’s DMAP platform delivers end-to-end, light-speed solutions for database, data, and application modernization on Google Cloud.
Ready to migrate?
See how DMAP can accelerate your Oracle to AlloyDB or Cloud SQL migration.
