Federal Shared Services

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

M3 Playbook > Phase 4: Migration
4.16 Conduct Mock Conversions

4.15 Design and Develop Reports

4.17 Test Systems and Processes

Objective:

Conduct mock data conversions to test transfer of data.

Phase 4 Guidance Legend - Customer, Provider, Shared

Activities

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)

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

Outputs

• Data Conversion Plan
• Mock Conversion Report
• Conversion Defect Log

Stakeholders

• 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