--- title: The New York Times cut Oracle migration time from 18 to... description: The New York Times migrated its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months instead of an estimated 18. The... canonical: https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The New York Times cut Oracle migration time from 18 to 5 months | daily.dev og:description: The New York Times migrated its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months instead of an estimated 18. The... og:url: https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7 og:image: https://api.daily.dev/og/posts/yec4k3Kr7.png og:image:alt: The New York Times cut Oracle migration time from 18 to 5 months og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The New York Times cut Oracle migration time from 18 to 5 months **[AWS Database Blog](https://daily.dev/sources/aws-database-blog)** · 11 min read · 0 upvotes · 0 comments ## Summary The New York Times migrated its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months instead of an estimated 18. The team used an AI-agent-native approach built on Amazon Bedrock with Claude Opus 4.6, paired with AWS DMS Schema Conversion, to remediate embedded Oracle SQL across roughly 6 million lines of code in Java, Python, Go, Groovy and shell scripts. The initial scan found about 110,000 conversion items across three schemas. At go-live the system sustained 18,500 requests per second with zero revenue impact and 100% row-level data accuracy. NYT is now applying the same pattern to three more Oracle workloads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How long did it take The New York Times to migrate its subscription system from Oracle to PostgreSQL? The New York Times completed the migration of its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months, down from an initial rule-based estimate of 18 months, a 72% reduction. The migration covered roughly 110,000 conversion items across three schemas and about 6 million lines of application code, with zero revenue impact at cutover. _daily.dev surfaces real migration timelines like this for teams estimating their own Oracle-to-Postgres move._ ### What AI model did Mactores and AWS use to convert embedded Oracle SQL in multi-language code? The migration used Claude Opus 4.6 running on Amazon Bedrock, orchestrated by the Mactores Aedeon Agent, to convert embedded Oracle SQL across five languages: Java, Gradle/Groovy DSL, Python, Go, and shell scripts. The agent ran iterative validation cycles, converting code, testing it against Aurora PostgreSQL, and feeding errors back to Claude for self-correction, scaled via Amazon Bedrock AgentCore. _developers evaluating AI code-conversion tools can track how models like Claude handle legacy SQL migrations on daily.dev._ ### What throughput did Amazon Aurora PostgreSQL sustain after replacing Oracle for a high-traffic production system? Aurora PostgreSQL sustained 18,500 requests per second at go-live for The New York Times' PLATO subscription revenue system, with full production throughput maintained and no degradation, plus 100% row-level data accuracy after cutover from Oracle. _anyone benchmarking Aurora PostgreSQL against Oracle for production workloads can find real numbers like this on daily.dev._ ## Similar posts on daily.dev - [Migrating mission-critical payments at Nubank to Amazon Aurora PostgreSQL](https://daily.dev/posts/migrating-mission-critical-payments-at-nubank-to-amazon-aurora-postgresql-uhkwmxh9s) · AWS Database Blog · 5 upvotes · 0 comments - [12 business days to move a data platform: how Pedro migrated Kilo into Anaconda](https://daily.dev/posts/12-business-days-to-move-a-data-platform-how-pedro-migrated-kilo-into-anaconda-kobb5lteo) · Kilo Blog · 0 upvotes · 0 comments - [Databricks vs. Oracle in 2026](https://daily.dev/posts/databricks-vs-oracle-in-2026-0rsjwsxs0) · databricks · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#database](https://daily.dev/tags/database), [#oracle](https://daily.dev/tags/oracle), [#amazon-bedrock](https://daily.dev/tags/amazon-bedrock) [View this post on daily.dev](https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The New York Times cut Oracle migration time from 18 to 5 months","url":"https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7"},"datePublished":"2026-10-26T17:25:32.866Z","dateModified":"2026-10-26T17:28:31.226Z","description":"The New York Times migrated its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months instead of an estimated 18. The...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c4c3801db8be222778e1ddb9c7cf248d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c4c3801db8be222778e1ddb9c7cf248d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS Database Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS Database Blog","logo":"https://media.daily.dev/image/upload/s--En-avd2a--/f_auto,q_auto/v1780213446/logos/aws-database-blog?_a=BAMAMiWQ0","url":"https://daily.dev/sources/aws-database-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,database,oracle,amazon-bedrock","timeRequired":"PT11M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS Database Blog","item":"https://daily.dev/sources/aws-database-blog"},{"@type":"ListItem","position":3,"name":"The New York Times cut Oracle migration time from 18 to 5 months"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-new-york-times-cut-oracle-migration-time-from-18-to-5-months-yec4k3kr7#faq","mainEntity":[{"@type":"Question","name":"How long did it take The New York Times to migrate its subscription system from Oracle to PostgreSQL?","acceptedAnswer":{"@type":"Answer","text":"The New York Times completed the migration of its PLATO subscription revenue engine from Oracle to Amazon Aurora PostgreSQL in about 5 months, down from an initial rule-based estimate of 18 months, a 72% reduction. The migration covered roughly 110,000 conversion items across three schemas and about 6 million lines of application code, with zero revenue impact at cutover. daily.dev surfaces real migration timelines like this for teams estimating their own Oracle-to-Postgres move."}},{"@type":"Question","name":"What AI model did Mactores and AWS use to convert embedded Oracle SQL in multi-language code?","acceptedAnswer":{"@type":"Answer","text":"The migration used Claude Opus 4.6 running on Amazon Bedrock, orchestrated by the Mactores Aedeon Agent, to convert embedded Oracle SQL across five languages: Java, Gradle/Groovy DSL, Python, Go, and shell scripts. The agent ran iterative validation cycles, converting code, testing it against Aurora PostgreSQL, and feeding errors back to Claude for self-correction, scaled via Amazon Bedrock AgentCore. developers evaluating AI code-conversion tools can track how models like Claude handle legacy SQL migrations on daily.dev."}},{"@type":"Question","name":"What throughput did Amazon Aurora PostgreSQL sustain after replacing Oracle for a high-traffic production system?","acceptedAnswer":{"@type":"Answer","text":"Aurora PostgreSQL sustained 18,500 requests per second at go-live for The New York Times' PLATO subscription revenue system, with full production throughput maintained and no degradation, plus 100% row-level data accuracy after cutover from Oracle. anyone benchmarking Aurora PostgreSQL against Oracle for production workloads can find real numbers like this on daily.dev."}}]} ```