Professional Documents
Culture Documents
Method outline
A successful Data Migration is defined by a set of quality
criteria
• Agreed stakeholder impact – customer, organization & third parties
2
2
Data Migration is represented as a Workstream in a
transition program
1 2 3 4
Analysis Design, Build & Component Test Integration Test Execute
3
3
Data Migration done Agile: series of incremental
migration iterations
Gap analysis
Number and duration of iterations depends on:
• Desired level of automation
Data analysis • Available IT capacity
• Available capacity for manual migration processes
• acceptabele customer timpact & impact on own organization
Migratie
strategy
Migration Tranche 1
Migration Tranche 2
Migration Tranche N
Execution
(optional)
Close out
4
4
Migration Iterations consist of a set of standard activities
Objectives, scope &
acceptance criteria
Data Analysis
Data Cleansing
Data Mapping
Migration test
Business process test
• test cycles (2) Execution
• Dress Rehearsal
(0, 1 or n tranches)
• Internal Tranche
• Live Migration
5
5
Migration activities result in standard migration
deliverables (with dependencies)
Program Production Commercial Clean Readiness
Objectives Data Migration Production Assessment
& Scope Approach Data
Ist/Soll Target Work
Gap Application Instructions
Analysis Landscape
Data
Mapping Migration Business
Data Test Plan Process
Analysis Test
(source) Dress
Component Migration
Design System Reheasal Execution
Component
Migration
Design
System/Int.
Migration Functional Technical Test
Strategy Migration Migration Design Migration Status/
Process Process Test Report Evaluation
Run Report
Book
Execution
Governance
6
6
Data Migration Strategy defines the outlines of the migration
Subjects to be addressed
Stake Holders
Acceptance Criteria
Migration Approach
• big bang vs iterations, slicing criteria,
• On-/Off-Line/Real time/Batch
• Timing – critical migration windows vs. synchronization source/target
• Load approach (database, application, service)
• Test approach (Business Process Tests)
• Manual/Automated
• Pipeline issues
• Rollback / fallback
Validation Approach (i.e. confidence checks)
7
7
Data Analysis provide insight in production data volumes,
relations and frequency distribution
Excel Pivot Table SQL Queries Data Analysis Report
8
8
Data Migration designed according to Extract Transform Load
Validate pattern
Each table contains source, timestamp and where Counts and Sums are calculated at each point where
applicable reference to transformation rules data is handed over to next stage
Conversion Engine
Source Target
Systems Systems
Validation Tool
Validation tool shares platform with Conversion Engine The control model defines where the checkpoints in the migration process
Both the engine and the validation tool are based on extraction files from are created and the metrics
Source and Target Every time data flows from one stage to the other, a report is generated to
Mapping is conducted independently from conversion engine to ensure show counts, sums and cross connections
proper validation
9
9
First Test Cycle serves as proof of concept and learning
curve, subsequent Test Cycles iron out defects
Cycle #1 Cycle #2 Cycle #3
Set-up preconditions
Execute migration
Conduct BP Testing
Wrap-up results
Fix defects
10
10
Successful Data Migration execution relies on five
deliverables
11
11
Successful Data Migration requires skills and experience
12
12