Skip to main content

M3 Framework Introduction M3 Framework Overview M3 Phase 0 - Assessment M3 Phase 1 - Readiness M3 Phase 2 - Selection M3 Phase 3 - Engagement M3 Phase 4 - Migration M3 Phase 5 - Operations M3 Resources
M3 Playbook > Phase 4: Migration
4.16 Conduct Mock Conversions
4.15 Design and Develop Reports
4.17 Test Systems and Processes
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Conduct mock data conversions to test transfer of data.

Phase 4 GuidanceLegend - Customer, Provider, Shared
1. Define and test conversion scenarios (S)
2. Design build and unit test data conversion including extracting, transforming, and loading procedures (S)
3. Design, build, and unit test validation/reconciliation reports (S)
4. Test manual conversion and document results (P)
5. Run mock conversion and document results (P)
6. Clean up data issues uncovered during mock conversions (S)
7. Repeat subsequent mock conversions and update scripts as necessary, cleansing more data each time until program team is satisfied with data accuracy (S)

• Requirements Traceability Matrix (RTM)
• Technical Strategy
• Data Conversion Strategy
• Data Cleansing Plan
• Data Quality Results

• Data Conversion Plan
• Mock Conversion Report
• Conversion Defect Log
• Program Manager (C, P)
• Functional Lead (C, P)
• Functional SME (C)
• Technical Lead/Solution Architect (C, P)
• Development Team (C, P)
• Network SME (C, P)
• Data Conversion Lead (C, P)
• Data SME (C, P)

Best Practice
• Conduct multiple mock conversions to mitigate complex conversion risks and include enough time in the IMS to correct anomalies and update conversion programs