Database
November 12, 2026
1 views
2 min read

The New York Times cut Oracle migration time from 18 months to 18 weeks

Curated by Patrick
Source: AWS Database Blog
The New York Times cut Oracle migration time from 18 months to 18 weeks
Tech Daily Byte Analysis

The NYT’s engineering team, together with AWS and the AWS partner Mactores, replaced a sprawling Oracle estate that spanned three schemas, 110 000 conversion items and roughly 6 million lines of code across Java, Groovy, Python, Go and shell scripts. By leveraging AWS Database Migration Service (DMS) Schema Conversion for bulk DDL changes and the Mactores Aedeon Agent—an AI‑native tool built on Amazon Bedrock’s Claude Opus 4.6—the project automated both schema transformation and the tedious remediation of embedded Oracle SQL. Continuous replication kept the source and target in sync, while a reverse‑replication path allowed a zero‑risk cut‑over that preserved full production throughput at go‑live. The effort eliminated about 200 CPU‑worth of Oracle licensing and positioned PLATO for multi‑region Aurora deployment.

The migration illustrates how generative‑AI services are moving from experimental to production‑grade utilities in enterprise data modernization. Traditional rule‑based converters struggle with heterogeneous codebases; Bedrock’s language‑agnostic model can ingest mixed‑grammar files and generate PostgreSQL‑compatible replacements, dramatically shrinking manual effort. AWS’s bundling of DMS, Schema Conversion, Step Functions and Bedrock creates a turnkey stack that rivals specialist migration consultancies, potentially reshaping the competitive dynamics between cloud providers and third‑party migration firms. As more media and subscription‑based businesses confront costly legacy licenses, the NYT case may accelerate adoption of AI‑augmented migration pipelines across the industry.

Looking ahead, the success hinges on the fidelity of AI‑generated code and the robustness of the rollback mechanism. Any subtle semantic drift in translated SQL could surface under peak traffic, risking data integrity or performance regressions. Organizations should therefore invest in extensive automated testing and staged rollouts, and monitor the evolving licensing model for Bedrock, which could affect total cost of ownership. Additionally, the repeatability of this approach will be tested as NYT scales PLATO across regions and integrates newer Aurora features, offering a real‑world barometer for AI‑driven migrations at enterprise scale.

Key Takeaways

The NYT cut an 18‑month Oracle‑to‑PostgreSQL migration estimate down to 18 weeks by pairing AWS DMS with an AI‑powered code conversion agent.

Mactores’ Aedeon Agent, running on Amazon Bedrock’s Claude model, handled multi‑language SQL remediation that traditional tools could not automate.

Eliminating roughly 200 CPU‑equivalent Oracle licenses reduces ongoing licensing spend and opens the path to Aurora’s multi‑region resilience.

Future risk management will focus on validating AI‑generated code and ensuring the reverse‑replication fallback remains reliable under production loads.

About the Source

This analysis is based on reporting by AWS Database Blog. Here is a short excerpt for context:

Learn how The New York Times migrated its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in 18 weeks instead of 18 months using an AI-agent-native approach on Amazon Bedrock with AWS DMS to automate schema conversion and multi-language code remediation at enterprise scale.
Read the original at AWS Database Blog

More in Database