Running parallel migration waves on AWS Transform with team isolation

This article explains how to run parallel migration waves on AWS Transform by establishing team isolation boundaries that allow multiple teams to execute migrations concurrently without interference.

• Three isolation models available: within a job, shared workspace with separate jobs, or separate workspaces per team
• Connectors and ATWorkspace tags enforce team boundaries and determine which resources each team can access
• Within-a-job model suits 2-3 small teams sharing a single view; requires high team discipline
• Shared workspace model fits 3-6 medium teams with shared infrastructure using explicit job naming conventions
• Separate workspaces provide complete isolation for large programs with strict compliance or separate account requirements
• Establish prerequisites: activate AWS Transform, configure connectors, set workspace access, map servers to teams, and align on isolation model before execution
• Validate isolation by reviewing job worklogs and artifacts to confirm only expected teams operate within each boundary

Choosing the right isolation model upfront and maintaining clear team boundaries through naming conventions and resource tagging enables large migration factories to accelerate timelines through parallel execution.