Transferring Completion History from Your LMS to Thrive

Prev Next

Customers can migrate the completions of any in Thrive by providing Thrive with a CSV of completions. In order to import the completions, both the user and the content needs to exist in Thrive.

If there is a large dataset, we will typically import into Staging first, then import into Live once the customer has reviewed the data import. This process can typically take up to 4-6 weeks due to the requirement to copy production down to staging.

When importing historical completions the record will be added to the individual's user history on their Learn page.

The historical completion will not appear on the content activity or within the activities extract. However, the completions will be used in the compliance report when assigning training to audiences, to mark any recent completions.

Customers tend to focus on importing completions for e-learning and events associated with compliance but it is possible to import a completion against all Thrive supported content types.

It is important to note that we can import the completions of content, but not the activities associated with that completion - we can’t import views, attempts, scores, etc.

If you have imported completions for users who have completed all items within a pathway, it's important to note that the pathway itself won't automatically be marked as complete unless it has its own completion record imported.

In this scenario, you must choose whether to:

  • Import completions only for the pathway, or

  • Import completions for both each individual item and the pathway for users who have completed everything.

To import the completions, we need you to supply us with a CSV which contains three columns:

  1. user_email - the user email address.

  2. content_id - the automatically generated Content ID from the URL of the content that you created in Thrive.

  3. completed - the date/time the user completed it in your other learning platform  in the format DD/MM/YYYY.

An example of the headings and data required within the CSV:


Note:

See more: Import Historical Data CSV Template