Lifecycle of a Data Migration
While good communication between ourselves and the client, and the automated nature of a migration reduce risk and increase reliability, time spent on planning early on in the project can be invaluable. Scoping is the planning stage and helps to spot potential problems down the road.
Mapping the data in the legacy system to the new system can present many challenges. SME’s (Subject Matter Experts) from the clients side will be essential in working through the legacy data sources for the relevant records and fields
By this stage it should be known what data is needed from the legacy system. Through communications between ourselves and the SME’s the relevant information can be extracted from the legacy source data with Select statements and the help of DM REVOLVE.
Once the extraction has been completed it is time to set up any transformations that the data may need. This will usually be changing legacy fields for example months of the year, from January, February etc to Jan, Feb, or perhaps street names from Street, Road, to St, Rd.
By now you have extracted all of the data from the legacy system, cleaned it and transformed it into the format needed. It’s time to load it up on to the target system. This is done in a simulated testing environment and will be done over and over again as the project progresses and new data objects are completed.
As the various data objects are loaded onto the target system they will need to be validated. This is done by the data owner and needs to be a thorough process, catching any missing, incorrect or excess records. Whatever data is signed off on at this stage will be used in the final data set on the Big Day.
Check and Cleanse
If a data object doesn’t pass validation it will need to be checked over again. It will be sent back to whichever stage is needed to fix the problem and stepped through the whole process again until it is validated and is signed off. A data object that has failed validation can go through this process several times before passing.