In a large migration, the migration workstream uses the wave plans and migration metadata supplied by the portfolio workstream in order to migrate workloads to the AWS Cloud. The migration workstream is responsible for submitting any change requests, migrating the application, coordinating application testing with the application owners, performing cutover, and monitoring the application through the hypercare period. In the first stage, initializing a large migration, you create the runbooks that the migration workstream uses to migrate the applications and servers. In the second stage, implementing a large migration, the migration workstream plans sprints and uses the migration runbooks in order to migrate and cutover the applications. For more information about core and supporting workstreams, see Workstreams in a large migration in the Foundation playbook for AWS large migrations.
This migration playbook outlines the tasks of the migration workstream, which spans both stages of a large migration, initialization and implementation:
In stage 1, initialize, you draft, test, and refine the runbooks, and then you automate manual tasks for each migration pattern.
In stage 2, implement, you perform the migration with the predefined runbooks built in stage 1.
