Data Migration Service

Why is it so important to carry out a data integrity test and data cleansing process as part of your implementation?

How Prepared are you?

When planning the implementation of a new ITM/LMS, most companies do not fully appreciate or understand the importance data quality will have on the project’s success or how difficult the migration process will be.

Often an implementation team will face what we call a ‘data shock’ – that uncomfortable feeling you experience the moment you realise that poor, incomplete, and corrupt data has derailed your implementation plan schedule.

Data quality and the data migration service is an important component of any implementation plan and must be detailed in the statement of work (SOW), but it is often overlooked.

Our solutions area

MDLman has dedicated data migration services and data migration software to help you overcome these issues by ensuring your data quality is fit for purpose and your migration goes smoothly. We help you understand:

1) The quality and completeness of the data in your legacy system
2) The mapping requirements between the legacy and target system
3) What data is required and is currently missing
4) How much time and effort is required to get the data ready for data migration service
5) The process and schedule for cleaning and enriching the data
6) How the data is transformed to match the target system’s format
7) Creation of data load files that will load successfully into the new system
8) The test and control measures needed to ensure a successful data migration service

Our data migration service is flexible – ranging from a simple advisory role, through to management and implementation of the migration process.

We offer several migration packages aimed at addressing key parts of the process and can also offer bespoke data migration services according to your specific requirement. To help us, we have developed a clever piece of software ‘MDLresolver’ – a data cleansing and transformation tool, which streamlines our entire data migration service.

Data migration service from MDLman.

MDL Assess

Helps you understand the extent of the legacy data quality issues. Using information from this service enables you to assess and scope how much work and effort will be required to resolve data issues before transformation and migration occurs. The process is simple – you give us access to some sample date file(s) from the legacy system(s) and then we conduct the Assessment to provide you with an accurate picture of the data quality and the necessary remedial work.

To find out more, please contact us

The next 3 service packages work together because this is an iterative process.

MDL Map

Provides you with an insight into what data is required for the new target system and specifically, what data you currently have in your legacy, what data is missing and importantly, what format the data needs to be for the full data migration service. Understanding this will help you identify what work is required to augment your existing data sets. This process also helps you identify what data you will archive as it is either not required or out of date and so not necessary to move to the new system.

MDLcleanse is the second stage of the data migration service.

MDL Cleanse

The next stage is to cleanse the existing and newly annotated data. Specifically, this process manages and correct the following:

Data Duplication – e.g. where the same person appears twice because they left and came back or started as a contractor and then were made permanent.

Data Error – where a person’s email does not conform to the correct email format e.g. firstname.lastname@company.com and one of the dots or the @ is missing.

Data Sense – where say the wrong year date hire date has mistakenly been entered e.g. the year date should be 2011, but was entered 1911

Data Logic – where the time zone applied to an individual does not match with the country code in the country they are located

Special Characters e.g. carriage return or as we call them ‘data gremlins’ – the ones that look as if they are from another planet or worse still can’t be seen at all.

MDL Transform

The final stage in this iterative process is to transform the data. This takes the complete and clean data set and transforms it into the format of the target system’s data templates. It is at this stage where any inconsistencies or problems are identified which may require further work in both the MDL Map and MDL Cleanse stages and hence the process is iterative.

This iterative process will ensure you have a data set that is fit for purpose ready for the load and that the data will not fail to load due to issues of quality, format, or completeness.
To find out more, please contact us

MDLload is the third stage of the data migration service.

MDL Load

Completion of the Map/Cleanse/Transform stages provides you with a data set that is ready to load into the new system. MDL Load creates the data load files and most importantly, dictates the correct order in which the data sets must be loaded in order that the target system can accept the data. Failure to follow the correct order can and will result in data and record load failures.

To find out more, please contact us

MDL Maintain

Once in production, any ITM/LMS is only as good as the data entered and that it contains. Data quality will and does deteriorate over time. This situation is often caused by the absence of field verification at point of entry and may have been exacerbated in a new system if a thorough data cleaning process was not completed prior to migration. As a result, there is a requirement to remove duplicate data, carry out address verification, fix data integrity problems where links have been broken, format problems, etc. MDL Maintain address all these problems by implementing a maintenance process to regularly check the integrity of your production data to ensure its quality and integrity. MDL Maintain ensures your ITM/LMS can operate at the optimum level, analysis can be conducted with confidence and end-user satisfaction increases because there are less trouble tickets raised because of data issues.

To find out more, please contact us