Migrate Existing Web Tests
Automated migration is unavailable. You can manually save Web Tests and request explicit Runs; compare their results and evidence with the original suite before replacing it.
Start with the business-critical journeys rather than translating every script line by line. Map each source suite to a Project, group related scenarios into Test Groups, and rewrite each scenario as ordered actions and observable assertions.
Preserve the source suite until QA.army results and evidence have been reviewed against the same targets. Do not claim migration parity before that review.