Legacy code assessment usually produces a PDF heat-map and a vague recommendation to "upgrade Java." AWS Transform does something different — it deploys an agentic loop that reads your entire codebase, builds a dependency graph, generates architecture diagrams, and outputs a phased migration plan with named next-step transformations.

I ran it against a real Spring Boot 2.5.14 + Java 8 + JBoss monolith. The agent produced 33 files in 61 minutes: full technical debt report with 8 findings prioritised by upgrade impact, sequence diagrams reasoned from source code, and a 6-phase migration sequence that respects leaf-first dependency order.

This session covers what agentic assessment gets you that manual tooling doesn't — and how assessment that actually names the next transformation changes the migration math. If you're managing legacy services, this is the assessment framework that feeds a real pipeline instead of sitting as a report.