# Asana cleared 5 years of engineering work in 2 weeks with Codex

Source: [OpenAI](https://openai.com/index/asana)  
Feed7 permalink: https://feed7.dev/p/asana-0pb84hl  
Published: 2026-08-18T07:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Asana says Codex replaced an outdated test system in two weeks for about $12K, compressing an estimated five-year migration into a focused agent-assisted project.

## Source Summary

Asana used Codex to replace an outdated testing system in **two weeks**. The company says the migration had been estimated at **five years** of engineering work and cost about **$12K**.

## Practical Implication

Builders should look for bounded, testable maintenance projects that agents can execute repeatedly, especially migrations whose manual workload has kept them indefinitely deferred.

## Agent-Ready Context

Asana used Codex to replace an outdated testing system in **two weeks**. The company says the migration had been estimated at **five years** of engineering work and cost about **$12K**.

Builders should look for bounded, testable maintenance projects that agents can execute repeatedly, especially migrations whose manual workload has kept them indefinitely deferred.

The material provides no implementation details, quality measures, staffing baseline, or calculation behind the five-year estimate, so it does not establish that similar compression transfers to other codebases.

## Connected Context

Feed7 judgment across 545 accumulated Signals:

This is the strongest supplied schedule-and-cost claim for agents tackling deferred maintenance, sharpening the case for bounded, repetitive, testable migrations. It does not establish a reusable productivity multiplier: the five-year estimate, staffing, implementation, review, and quality evidence are absent, so the result remains a company case rather than a benchmark for other codebases.

- [Stampli cuts launch hours by 68% using ChatGPT Work](https://feed7.dev/p/stampli-0lomhe7) — Stampli reports measured time savings on deadline-bound launch work, extending the targeted-capacity pattern beyond Asana’s maintenance migration while sharing similar evidence gaps.
- [Agentic SDLC at Uber — Uday Kiran Medisetty & Adam Huda, Uber](https://feed7.dev/p/agentic-sdlc-at-uber-uday-kiran-medisetty-adam-huda-uber-1ugtaxn) — Uber identifies environments, context, reusable skills, and validation capacity as prerequisites for scaling migrations, operational details absent from the Asana account.
- [Scientific computing in the age of agentic AI](https://feed7.dev/p/scientific-computing-agentic-ai-0bij8w4) — The scientific-computing case points to another legacy-software modernization use case, but lacks the concrete schedule and cost claim supplied by Asana.

## Context Map

- Layer: industry
- Domains: coding
- Topics: adoption, coding-agents

## Uncertainty

- The material provides no implementation details, quality measures, staffing baseline, or calculation behind the five-year estimate, so it does not establish that similar compression transfers to other codebases.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.