Data Migration and Mastery Score

Here is the problem that one of the clients faced. The client had 2 different LMS versions running and wanted to merge the 5.8.3 data to the one in 5.8.5.

The data migration scripts were written by a Migration Expert and the data migrated. During the Customer testing of the content, the content was getting launched and they could complete the Course but it was not being removed from the Learning Plan and cannot be seen in the Learning History.

After debugging, I found out that the Mastery Score was null. This value was not being migrated from the 5.8.3 system based on the data requirements provided by the LMS Admin. When this value was set and the Course taken again then the Course moved to the Learning History. The 5.8.5 LMS application does not warn or throw an error mentioning that this field is null. Neither is this a mandatory field.

Here are some best practices while doing the LMS data migration. You will save precious time of everyone and thousands of dollars if these are followed.

• Data is the king. Data was entered for some purpose. So, without second guessing migrate the data as it is. The LMS Admins may not know why some field is required.
• Use the Copy Entity Tool to do this. This is easy to configure and it does not increase the time or cost to copy all the columns in a given table.
• Avoid writing SQL scripts to do data migration where Copy Entity Tool can serve the same purpose. 
• Get the data migration strategy reviewed by the Plateau LMS Consultant.