Moving your xAPI Data from one vendor’s LRS to another

There are many xAPI implementations that have been invested in over the last few years that for one reason or another are now in need of an update.

Common reasons include:

  • An open source LRS offering no longer being supported

  • A change in the funding available to support LRSs

  • A shift in the enterprise data strategy to LRS federation — and the accompanying need to find better and more flexible licensing terms

But what do you do about all of that data that you’ve collected? Migrating xAPI can be tricky. And, generally speaking, data migration is always expensive (and a hassle).

Fear not, the Yet Analytics team has you covered.

We’ve built a software capability called LRSPipe which can be used to forward xAPI from one LRS to another — no matter who the LRS vendors are. So now, you can migrate your data and change vendors far more easily.

You can find LRSPipe on our Github page — it’s open source and distributed under the Apache 2.0 license. While you are there, you can launch your own free SQL LRS and move your data into it from your old LRS (which isn’t a bad idea as a backup, anyway).

As always, if you have questions or need someone to do the heavy lifting for you, just reach out.

Previous
Previous

Centriph, the Authoring Platform for xAPI Profiles: the Beta is now open to the public

Next
Next

Estimating the Cost of xAPI: Using Data Simulation to Budget Your Implementation