AWS Transform helps engineering teams assess and execute changes to infrastructure, applications, and code. Its specialized agents support migration planning, server rehosting, network conversion, mainframe modernization, .NET modernization, and custom code transformations. A shared workspace brings together job plans, conversations, artifacts, approvals, and execution history so that infrastructure engineers, application developers, and reviewers can work on the same transformation.
A typical project begins with source material such as server inventories, application repositories, network configurations, or mainframe code. Engineers describe the desired outcome through a conversational interface and refine the resulting job plan. Tasks can be revisited when assumptions change. Treat generated plans and artifacts as engineering inputs: validate discovery completeness, dependency relationships, security requirements, and operational constraints before approving deployment or cutover.
For infrastructure migration, AWS Transform supports discovery, application grouping, dependency analysis, migration wave planning, landing zone creation, network migration, and server rehosting to Amazon EC2. Supported source environments include VMware, Hyper-V, and other virtual or bare metal server environments. Network workflows can translate existing configurations, build a new network, or convert access rules into security groups for existing VPCs. Landing zone workflows can assess and extend supported existing AWS environments, including AWS Control Tower deployments, and offer an infrastructure-as-code-only mode.
Application modernization includes moving supported .NET Framework applications toward Linux-ready, cross-platform .NET. Available capabilities include generating unit tests for transformed code and converting supported Azure SDK usage to AWS SDK usage. Compatibility assessment remains important: unsupported native Win32 dependencies may require manual replacement, and repositories must contain supported .NET solutions. Generated tests provide additional coverage but do not replace regression testing against existing application behavior.
Mainframe workflows support assessment and modernization of IBM z/OS and Fujitsu GS21 workloads. For supported z/OS COBOL and PL/I reimagine workflows, business-function discovery can distinguish access at the data-field level, and requirements coverage reports help teams inspect traceability before implementation. Custom transformations let teams define organization-specific changes using natural language, documentation, and code samples. Continuous modernization can scan repositories, identify technical debt, and generate remediation pull requests for review.
Before starting a production program, confirm supported Regions, workload-specific limitations, and service quotas. Some mainframe data processing can occur outside the selected Region, so review cross-Region processing requirements before uploading regulated code or data. Plan separately for target infrastructure, replication, testing, rollback, and application acceptance. AWS Transform does not eliminate the need to verify functional equivalence, database correctness, performance, or security controls in the resulting environment.