# Stage2: Implementing a large migration
<a name="stage-two-implementation"></a>

In stage 1, you developed migration runbooks for each migration pattern. In stage 2, you use these runbooks to migrate servers and then improve the runbooks in order to accelerate the velocity of the migration. Building and updating runbooks is not a one-off task. You might need to do that throughout your large migration journey. For example, you might need to create new runbooks if the scope increases and you identify new migration patterns, or you might need to improve the existing runbooks if the migration velocity is below the target and introducing more automation would reduce the number of manual tasks and accelerate the migration.

**Note**  
The wave plan developed in the portfolio workstream determines the activities in the migration workstream. Before starting stage 2, verify that you have validated your wave plan. For instructions and more information about the wave plan, see [Portfolio playbook for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-portfolio-playbook/). 

Stage 2 consists of the following tasks and steps:
+ [Task 1: Performing sprint planning for scheduled waves](task-one-sprint-planning.md)
  + [Step 1: Review the backlog for the scheduled waves](task-one-sprint-planning.md#step-one-review-backlog)
  + [Step 2: Assign tasks and establish due dates](task-one-sprint-planning.md#step-two-assign-tasks)
+ [Task 2: Performing pre-migration and migration tasks](task-two-migration-tasks.md)
+ [Task 3: Performing cutover tasks](task-three-cutover-tasks.md)
+ [Task 4: Reviewing and improving the migration runbooks](task-four-runbook-improvement.md)
  + [Step 1: Review the completed waves and identify gaps in the current migration runbook](task-four-runbook-improvement.md#step-one-review-waves)
  + [Step 2: Update the migration runbooks and complete testing](task-four-runbook-improvement.md#step-two-update-runbooks-testing)