STEP 02 / 06
Step 02: Design and Preparation - Top
Define the migration scope and data mapping, then design a repeatable runbook.
01
Why read this step first
Define the migration scope and data mapping, then design a repeatable runbook.
This step makes the scope, dependencies, controls, and evidence explicit so later work can be reviewed and repeated.
Completion state
Stakeholders have agreed on the data scope, mapping, transformation and exception rules, and runbook.
Key outputs
- →Migration data-scope definition
- →Data profiling report
- →Data mapping specification
- →Data cleansing specification
- →Data archive design
- →Migration runbook
02
Sequence of work
- 01
Identify migration data scope
Define, execute, review, and preserve evidence for this activity.
- 02
Profile source data
Define, execute, review, and preserve evidence for this activity.
- 03
Define data mapping
Define, execute, review, and preserve evidence for this activity.
- 04
Define cleansing rules
Define, execute, review, and preserve evidence for this activity.
- 05
Create the migration runbook
Define, execute, review, and preserve evidence for this activity.
- 06
Design the data archive
Define, execute, review, and preserve evidence for this activity.
03
Before moving on
Stakeholders have agreed on the data scope, mapping, transformation and exception rules, and runbook.