Skip to main content
U.S. flag

An official website of the United States government

Dot gov

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.

Https

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.

The Modernization and Migration Management (M3) Playbook has a new look! Explore our new features here.

M3 Playbook > Phase 3: Engagement > 3.13 Prepare Data for Mock Conversions (Data Cleansing, Data Mapping)

3.13 Prepare Data for Mock Conversions (Data Cleansing, Data Mapping)

Technology

Task Activities

  1. Shared

    Develop integrated data governance approach to include process, roles, responsibilities, and cleansing and mapping criteria

  2. Provider

    Review customer data architecture

  3. Provider

    Discuss standard data management approach with customer

  4. Shared

    Finalize an integrated approach and plan for data cleansing, mapping, extract/transfer/load, mock conversion, conversion, and data validation

  5. Shared

    Assess data quality based on Data Cleansing Plan activities from previous phase against defined criteria

  6. Shared

    Initiate legacy-to-target data mapping

  7. Shared

    Identify data errors/anomalies and prioritize resolution activities

  8. Shared

    Develop and execute Data Cleansing Scripts and perform manual correction, updating as needed

  9. Customer

    Validate results of data cleansing and readiness for conversion based on data quality criteria and metrics

  10. Shared

    Report updates in governance meetings and Status Reports/Dashboards

3.13 Best Practices

  • Begin data cleansing activities prior to migration activities and continuously throughout the implementation to assist with data readiness
  • Agree on data governance including metadata management and data quality management
  • Incorporate additional post Go-Live data cleansing and quality activities into the Data Conversion Plan strategy, schedule, and resource planning
  • Investigate provider service offerings around post Go-Live conversion support prior to finalizing cleansing metrics
  • Develop procedures, tools, and protocols to extract data and define system structure, major components, and type of conversion effort. Define system hardware and software conversion steps, identify necessary data and preparation requirements, and establish data quality assurance controls for conversion. Identify and address affected interfaces and security issues related to conversion efforts

Stakeholders

Customer

  • Program Manager
  • Business Owner
  • Functional Lead
  • Technical Lead/Solution Architect
  • Data Conversion Lead
  • Data SME

Provider

  • Program Manager
  • Business Owner
  • Functional Lead
  • Technical Lead/Solution Architect
  • Data Conversion Lead
  • Data SME

Inputs

  • Data Elements
  • Data Cleansing Plan
  • Data Quality Assessment Results
  • Existing System Data Dictionaries
  • Existing Data Governance Model
  • Data Cleansing Results
  • Existing Data Quality Assessment

Outputs

Return to top