# Program choice — rewrite, one-off campaign, or continuous modernization

Use with [AWS Transform continuous modernization vs a funded rewrite](https://www.factualminds.com/blog/aws-transform-continuous-modernization-vs-rewrite/). Score one repository group. General availability was 3 August 2026. Confirm the region list before you promise a Region.

AWS Transform-managed compute runs analyses only. Remediation and a custom transformation definition need AWS Batch (Fargate) or Amazon EC2.

| Question | Answer |
| --- | --- |
| Repository group (not the whole company) | |
| Source: GitHub, GitLab, Bitbucket, or local only | |
| Program: rewrite / one-off campaign / continuous schedule | |
| If campaign: end date | |
| First analysis type (`rapid-techdebt-analysis` does not read source) | |
| Compute: local / aws-managed / Batch (Fargate) / EC2 | |
| Will this run open pull requests? If yes, compute cannot be aws-managed | |
| Who reviews the pull request? | |
| Does the repository have tests? If no, the program does not create them | |
| Is the change a behavior the repository does not contain? If yes, this is a rewrite | |

## Stop

- aws-managed plus remediation: change the compute, do not merge unreviewed diffs.
- Agentic-readiness (56 criteria, five categories) is an analysis. It is not an agent build and not a rewrite authorization.
- This sheet does not choose mainframe, VMware, or network campaigns.