Case Study
Telecommunications · United States
Oracle to AlloyDB with Java app remediation — 12 weeks, end to end
Hughes Network Systems’ ECOM platform — a 4.6 million line-of-code Java and NodeJS application — was fully migrated from Oracle to AlloyDB on Google Cloud in under 12 weeks, including schema conversion, data migration, and complete application remediation.
Oracle → AlloyDB
Java · NodeJS
4.6M LOC
Google Cloud Platform
DMAP
Customer
Hughes Network Systems, LLC
- Industry
- Location
- Migration
- Application
- Timeline
- Team size
- Cloud platform
- Telecommunications
- United States
- Oracle → AlloyDB
- ECOM (Java + NodeJS)
- 12 weeks end to end
- 40+ across 5 time zones
- Google Cloud Platform
Lines of code migrated (Java + NodeJS)
Weeks from engagement to production cutover
Rigorous test environments before go-live
Team members across 5 time zones
Background
Hughes Network Systems, LLC is a Fortune 500 company and a recognized leader in networking technologies and services. Named a Leader in the 2023 Gartner® Magic Quadrant™ for Managed Network Services, Hughes enables essential connectivity for communities, businesses, and governments worldwide.
Hughes’s ECOM platform is a business-critical application spanning 4.6 million lines of code in Java and NodeJS. Backed by Oracle databases, the system drives significant e-commerce operations and serves as a cornerstone of Hughes’s digital infrastructure. Modernizing this platform to Google Cloud’s AlloyDB was essential for long-term scalability and cost efficiency — but the complexity of the migration posed severe challenges.
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.
