Date Migration Validation

Dry Runs
Dry Run 1
  • Includes limited number of cases and data for limited case sections
  • Verification of migration approach and framework
  • 3 weeks of execution and 2 weeks of remediation & resolution
Dry Run 2
  • Includes data for all case sections
  • Verification of added functions – revisions and attachments
  • 3 weeks of execution and 2 weeks of remediation & resolution
  • Full migration with all cases
  • Validation of complete data migration requirements
  • Validation of complete case revisions and attachment requirements
  • Dry Run UAT Test Scripts
  • 3 weeks of execution and 2 weeks of remediation & resolution
System Test

Formal Testing using approved system test scripts (after completion of iterative dry runs) of the solution to ensure the migration objectives are achieved. All System Test evidences will be recorded during this phase

Automated Validation (SQL Minus Query)

This is a SQL minus query-based validation approach which covers 100% in-scope cases and fields as per data migration business rules.

Custom and Standard Reports Comparison

To validate the accuracy of the migration, comparison of E2B/Paper reports will be carried out, or custom comparison reports will be created, to provide details about match status of migrated fields.

Balancing Checks

To validate the number of records being migrated from source to target.

SME Reviews

At each development and dry run iteration, dedicated manual reviews by business and functional SMEs to ensure the migrated data is satisfying regulatory compliance requirements based on customer business practices

SME reviews to be conducted after

  • Each development dry run
  • System test – each dry run and formal execution
  • User acceptance test – dry run and formal execution
User Acceptance Test

Testing of the migrated data and solution by business users to ensure business/ compliance requirements are satisfied

Report Comparison:

Classification of representative cases will be finalized. A sample for each class will be created using random sampling method. Customer business team will decide the sample size for each class.

New/FU case processing:

New case processing and follow up case processing on migrated case will be performed to uncover any impact of migration on case processing or report scheduling.

Any additional acceptance test scenarios to be determined in discussion with the business

Defect Analysis and Resolution

All defects identified during the project will be logged in a defect log.

The defect log will be actively monitored by the Project Manager and track leads to ensure all logged defects are analyzed and tracked to closure.

A weekly review of open defects will be conducted by stakeholders.

Vitrana uses cookies to to analyse our traffic and to personalise the content. We also disclose information about your use of our site with our analytics partners. Additional details are available in our cookie policy.

Accept Cookies