STEP 02 / 06
Step 02: Design and Preparation - Details
Define the migration scope and data mapping, then design a repeatable runbook.
02
Details: Work and outputs
The work shown in the overview is made concrete through inputs, outputs, dependencies, and completion conditions.
1. Output purpose and completion
| Output | Purpose | Completion and next use |
|---|---|---|
| Migration data-scope definition | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
| Data profiling report | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
| Data mapping specification | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
| Data cleansing specification | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
| Data archive design | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
| Migration runbook | Provides reviewed evidence for the design and preparation stage. | Approved, stored, and ready for the next stage. |
2. Work, inputs, outputs, and dependencies
| Work | Summary | Input | Output | Dependency | Class |
|---|---|---|---|---|---|
| Identify migration data scope | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Prior step | Required |
| Profile source data | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Identify migration data scope | Required |
| Define data mapping | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Profile source data | Required |
| Define cleansing rules | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Define data mapping | Required |
| Create the migration runbook | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Define cleansing rules | Required |
| Design the data archive | Execute and review the activity using the approved controls. | Approved prior-stage information | Reviewed stage evidence | Create the migration runbook | Required |
3. Supporting documents and tools
Supporting documents
Use this category to support review, execution, and traceability.
Validation tools
Use this category to support review, execution, and traceability.
Management tools
Use this category to support review, execution, and traceability.
4. Change and history management
Version-control definitions, execution logs, approvals, and exceptions. Record the reason, owner, approver, timestamp, and affected scope for every material change.
5. Completion condition
Stakeholders have agreed on the data scope, mapping, transformation and exception rules, and runbook.