If you use an LRS as a simple copy of your data that you might as well have stored it in your LMS as you are sacrificing a good part of the benefits of the LRS. That is, by storing only the completion and score of a Scorm content by changing the export settings of your authoring tool.
The LRS is as capable of capturing the informality of “learning in the flow of work” as it is of cross-referencing learning data with related data to measure the impact of learning on other everyday actions.
Publishers have specialized in the creation of solutions for visualizing the data stored in an LRS called Learning Analytics. These solutions are often paid for, unlike the LRS that you can find in open source on the web.
The low cost of entry, due to the fact that there are open source LRS solutions, is an additional advantage to prototype its implementation in your organization.
You will then be able to control where your LRS data is stored because you will host it yourself.
Last but not least, storing all your learning data in an LRS significantly reduces your dependence on an LMS provider.
Indeed, we know how difficult it is to migrate data from an LMS A to an LMS B when you change supplier.
First of all, you have to export the historical data. Then you have to check your content library (Scorm / multi-Sco compatibility… and which vary from one editor to another). Finally, you have to transform these data and reimport them into the new LMS.
With an LRS, data migration is greatly simplified.
You automatically export all the data from your current LMS that you copy to your LRS (like a backup system) in addition to your other Learning streams. If you have to change LMS provider, you only have to “reconnect” your new LMS to your existing LRS. No more data migration problems.
The solution is far from miraculous, but it is still worth exploring.
These are the benefits of the LRS, having a structured, standardized database that is easily readable by several systems.