Overview

Data Migrations are often overlooked in the case of SF Learning implementations. In my experience data migration efforts drive many configuration decisions and should be front and center during any implementation.

Too often SF Learning is implemented based on existing processes in a legacy LMS. After the system is up and running the data migration effort begins. As during any data migration effort, data clean-up is inevitable. Most organizations strive towards some sort of annual data archiving and audit process, but often fall short resulting with a system full of irrelevant data.

Despite having the same owner (SAP) the two systems are vastly different and interpret similar concepts differently. Data migration from SAP LSO to SAP SF Learning is not a one-to-one proposition. Values have to be interpreted and transformed.

Data Clean-Up

Every training organization has data that should not be migrated. This could include test courses and users, abandoned training, or legacy data. While migrating to a new LMS it is a great opportunity to do some spring cleaning.

Keep in mind that data cleansing could lead to a leaner implementation as abandoned values will not have to be configured into the system.  Reporting also greatly benefits from consistent data.

Note:
It is imperative that you know your company’s data retention policies as that might influence your decisions.

Historical Data

Historical data is a pain point of any migration as continuity is always a concern.

These are the following questions we have to be able to answer during a migration:

• How will existing learners be able to continue their on-going assignments?
• How will learners be able to see their training history?
• What kind of reporting can you expect on courses completed in a legacy LMS?

The answers may vary based on business needs and should be weighed carefully.

Legacy Course Completions

While considering migrating legacy course completions the following points should be discussed:

• During migration some completion data might be lost or transformed due to the differences in the system design.  Treating SF Learning as the permanent archive of historical records might not satisfy legal requirements.
• Cost of archiving legacy data with appropriate access vs migrating legacy completion data.
• Specific data that is available to satisfy reporting and re-training needs .