--- schema: "swft.publication/v1" id: "company-amazon-q-migrations" title: "Amazon Q migrations: an AI factory for fleet-wide Java upgrades" description: "How Amazon Q Developer transformed Java applications at fleet scale, what its savings figures mean, where people stayed involved, and why the product is retiring." summary: "Amazon Q Developer turned Java modernization into a repeated line: analyze an application, create a plan, change code and dependencies, build and test it, then ask a developer to review the result. Amazon reports fleet-scale savings, while the public evidence omits the full complexity mix and the product is moving toward end of support." canonical: "https://swft.io/companies/amazon-q-migrations" author: "SWFT Editorial" author_type: "Organization" published: "2026-09-01" modified: "2026-09-02" kind: "case-study" section: "Companies" tags: ["Amazon Q Developer", "Java code transformation", "AI application modernization", "fleet migration", "software maintenance factory", "AWS Transform"] evidence_labels: ["INFERENCE", "OBS", "SELF-REPORT"] source_ids: ["amazon-q-end-of-support", "amazon-q-java-milestone", "amazon-q-java-transform"] authorship_disclosure: "AI-drafted from the cited public sources and independently checked by a second AI editorial-review agent (Codex) for source fit, claim boundaries, overlap, and reader utility. SWFT Editorial is responsible for corrections." --- # Amazon Q migrations: an AI factory for fleet-wide Java upgrades Amazon turned Java upgrades into repeated analyze, plan, transform, build, test, and review jobs, then began moving customers to successor products. > **Authorship:** AI-drafted from the cited public sources and independently checked by a second AI editorial-review agent (Codex) for source fit, claim boundaries, overlap, and reader utility. SWFT Editorial is responsible for corrections. ## Quick answer Amazon Q Developer turned Java modernization into a repeated line: analyze an application, create a plan, change code and dependencies, build and test it, then ask a developer to review the result. Amazon reports fleet-scale savings, while the public evidence omits the full complexity mix and the product is moving toward end of support. Amazon's clearest software-factory case is a fleet-wide maintenance job. Amazon Q Developer analyzed older Java applications, planned an upgrade, changed dependencies and code, built and tested the result, and returned a reviewable diff. Amazon reports very large savings, while the exact product that performed the work is now being retired. ## What was Amazon Q Developer's Java migration workflow? Amazon built Code Transformation to move Java 8 and Java 11 applications to Java 17. Its [2023 launch account](https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/) describes three broad stages. First, the service analyzes the application in a managed environment and creates a project-specific transformation plan. It inspects dependencies, deprecated APIs, and build requirements. Next, it updates dependencies and source code. Finally, it builds the transformed application, runs available tests, and returns the changed files, summary, and build results for a developer to review. The result can be successful or partial. A partial transformation may contain useful updates even though the application does not compile yet. A developer still decides whether to accept, repair, and commit the changes. This is a **migration line** rather than open-ended feature development. The target state, Java 17, is known in advance. Compilation and existing tests provide useful proof. Similar applications can enter the same workflow at fleet scale. ## What internal scale did Amazon report? The launch article says an internal Amazon team of five upgraded 1,000 production applications in two days. It reports an average of about ten minutes per application and says the longest took less than an hour. A later [AWS milestone article](https://aws.amazon.com/blogs/devops/amazon-q-developer-just-reached-a-260-million-dollar-milestone/) says Amazon used Q Developer to migrate tens of thousands of production applications. AWS estimated that the work avoided more than 4,500 developer-years and produced performance improvements worth $260 million per year. These numbers are Amazon's self-reported estimates. The 2024 article says the time-saved estimate was based on the number of Java dependencies migrated and a typical manual time of a day or more per dependency. It is not a randomized or independent productivity study. The public milestone material does not disclose the full mix of application size, dependency complexity, test coverage, or manual work behind the portfolio. The early throughput example should therefore not become a forecast for every difficult legacy application. ## What did the agent automate, and what stayed with people? The transformation agent automated discovery, plan generation, dependency changes, deprecated-code repair, compilation, and available tests. The managed build environment gave each attempt a consistent place to run. People still selected the application, reviewed the plan and diff, handled partial transformations, assessed behavior not covered by tests, and committed the result. Existing tests constrained what the workflow could prove. A compiling application can still behave incorrectly, and an application with weak tests leaves more risk for review. The public material does not report how many attempted applications failed, how many partial transformations people completed, how many changes were reverted, the defect rate after release, or total review attention. ## Is Amazon Q Developer still the current product? No. In an [April 2026 end-of-support announcement](https://aws.amazon.com/blogs/devops/amazon-q-developer-end-of-support-announcement/), AWS said new Q Developer IDE accounts and subscriptions would stop in May 2026. The IDE plugins and paid subscriptions, including Java and .NET code transformation, are scheduled to reach end of support on April 30, 2027. AWS directs new Java modernization work to AWS Transform custom and directs general agentic development to Kiro. Existing eligible customers can continue using Q Developer during the transition. The historical factory result remains useful, but readers should not treat Q Developer Code Transformation as Amazon's long-term product direction. ## Why is this still a useful software-factory case? The migration had a standard destination, many candidate applications, a repeatable plan, a managed execution environment, executable proof, and a human acceptance point. It converted a maintenance portfolio into a queue of comparable work units and let a small team oversee much more execution. The product transition adds another lesson. A factory architecture should preserve task specifications, validation rules, migration records, and source-control history outside any one model or vendor surface. The line needs to survive a tool replacement. ## What can a product team copy? Choose a costly maintenance campaign with a clear target version and a reliable build. Segment applications by complexity before making a throughput forecast. Generate a visible plan. Run compilation and tests in a controlled environment. Return partial work with exact failure evidence. Track attempts, accepted migrations, manual completion, review time, defects, operating savings, and tool-transition risk. Report easy and difficult cohorts separately. A dramatic result from selected simple applications should not become the forecast for every legacy system. ## How we know - **First-party report (SELF-REPORT)** AWS describes Code Transformation's analysis, plan, dependency and source updates, managed build, tests, reviewable output, and early 1,000-application internal result. Sources: [Upgrade your Java applications with Amazon Q Code Transformation](https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/). - **First-party report (SELF-REPORT)** AWS reports tens of thousands of Amazon production migrations, more than 4,500 estimated developer-years avoided, and $260 million in estimated annual performance savings. Sources: [Amazon Q Developer just reached a $260 million dollar milestone](https://aws.amazon.com/blogs/devops/amazon-q-developer-just-reached-a-260-million-dollar-milestone/). - **Observed artifact (OBS)** AWS announced that Q Developer IDE transformation features will reach end of support on April 30, 2027 and directs new modernization work to AWS Transform custom. Sources: [Amazon Q Developer end-of-support announcement](https://aws.amazon.com/blogs/devops/amazon-q-developer-end-of-support-announcement/). - **Analysis (INFERENCE)** SWFT treats a narrow target state, segmented work queue, managed build, executable checks, human acceptance, and tool portability as the transferable factory design. Sources: [Upgrade your Java applications with Amazon Q Code Transformation](https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/); [Amazon Q Developer end-of-support announcement](https://aws.amazon.com/blogs/devops/amazon-q-developer-end-of-support-announcement/). ## Sources - **First-party report (SELF-REPORT)** [Amazon Q Developer end-of-support announcement](https://aws.amazon.com/blogs/devops/amazon-q-developer-end-of-support-announcement/) — AWS DevOps & Developer Productivity Blog; published 2026-04-30; accessed 2026-09-01. AWS's current transition notice: the IDE plugins and code-transformation feature end support on April 30, 2027, with modernization work directed to AWS Transform. - **First-party report (SELF-REPORT)** [Amazon Q Developer just reached a $260 million dollar milestone](https://aws.amazon.com/blogs/devops/amazon-q-developer-just-reached-a-260-million-dollar-milestone/) — AWS DevOps & Developer Productivity Blog; published 2024-08-01; accessed 2026-09-01. Amazon's self-reported migration scale, estimated developer time avoided, and annual infrastructure savings from Java modernization. - **First-party report (SELF-REPORT)** [Upgrade your Java applications with Amazon Q Code Transformation](https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/) — AWS News Blog; published 2023-11-28; accessed 2026-09-01. AWS's product account of the analyze, plan, transform, build, test, summarize, and developer-review loop for Java upgrades. ## Read next - [Spotify Honk: adding an agent to a software factory that already worked](/companies/spotify-honk) - [Stripe Minions: how developer infrastructure became an AI software factory](/companies/stripe-minions) - [Software factory metrics that matter](/software-factory-metrics)