Data Healthcheck
Legacy systems data often contain integrity issues, with inconsistencies and deficiencies that if not corrected will introduce errors and failures during migration, causing rejection of the upload files or creating anomalies in the new system after upload. These problems in turn, can add a significant workload for the testing team as the cause of the problems need to be identified and corrected as they are discovered, and this adds considerable effort and delay to the project, and normally results in a new trial load to be scheduled.
The Data Healthcheck identifies quality problems at the
outset of the project and avoids lengthy and expensive
trouble-shooting and failure later in the project. In so
doing, it helps manage and minimise risk to project delays.
Tara highlights some of the Lorenzo data checks
The Data Healthcheck is a process undertaken by Avoca staff
that analyses the migrating data after extraction from the
source system and before any data transformation or cleaning
takes place. The Healthcheck establishes that the data is
suitably complete for the intended migration and runs through
a comprehensive set of tests to identify many common
integrity issues. Typically the report is 20-30 pages for
each migrating dataset and includes the tests performed, the
results, embedded files with relevant records from the source
data, and recommended actions.
Where the Healthcheck report identifies issues that result in
amendments to source data, extraction routines or
documentation then a second Healthcheck run will be
performed. After this second run an authority to proceed
document is produced which will include an impact assessment
of any outstanding issues that remain after the second run.
The Data Healthcheck should be performed well in advance of
the go live date being set as issues identified can often
require changes to the extraction routines which may take
several weeks to implement.
)