LMS Migration Checklist: Courses, Users and Training Records

Capytech graphic titled LMS migration checklist: courses, users, records

An LMS migration checklist covers four things: getting a complete export of your courses, users and completion records from the old platform, checking your contract and UK GDPR obligations before the old supplier deletes anything, testing the move on a sample before the real one, and switching staff over with a clear date and message. The step most often missed is completion history, so ask for it early and check that the export actually opens.

This guide is for UK L&D and HR managers whose LMS contract is ending or whose platform no longer fits. Work through it in order, starting at least three months before your notice date if you can.

When to start an LMS migration project plan

Start with your current contract, before you talk to new suppliers. Find the end date, the notice period and what the agreement says about getting your data back.

Then put a simple project plan together:

  1. Name one owner for the migration, with a contact in HR, IT and data protection.
  2. Work back from the contract end date to set your cutover date, leaving time for a test migration and a period of parallel running.
  3. List every system connected to the LMS: HR system, single sign-on, reporting tools, any client or partner portals.
  4. Agree who signs off each stage, and what “done” looks like for each one.

A simple spreadsheet with a row per task, owner and date works as an LMS migration project plan template.

What to export from your old LMS

This is the heart of any LMS data migration. Ask your current supplier for a full export in standard formats (CSV or Excel for data, original zip files for courses) and ask them to confirm in writing that it is complete.

Courses and content

  • SCORM and xAPI packages. The original zip files for every course, with the version (SCORM 1.2, SCORM 2004 or xAPI) noted. If your old platform only holds courses built in its own editor, ask whether they can be exported as SCORM, because many built-in editors cannot.
  • Source files. Authoring files, videos, PDFs, images and any translations. You will need these to update a course later, and the published package alone is rarely enough.
  • Course settings. Pass marks, number of attempts, completion rules, due dates and recertification periods. These are easy to lose and change what counts as complete.
  • Certificates and templates. Certificate designs, signatories and wording, plus any email templates you want to keep.

Users and structure

  • Users. Name, email, employee number, job title, department, site, manager and status (active or left). Your HR system is usually the master record, so check the two match.
  • Groups and audiences. Teams, sites, job roles and any rules that enrol people automatically.
  • Enrolments in progress. Who is part-way through which course, and their due dates.

Records and evidence

  • Completion history. Every completion with the learner, course, date, score and pass or fail, for current and past staff.
  • Certificate history. Issued certificates with their dates and expiry dates, ideally as PDFs as well as data.
  • Audit trails and reports. Login and activity logs, assessment attempts and any reports you have shown to an auditor, regulator or client.

Once the export arrives, open every file. Check row counts against the old system’s reports, and pick ten learners at random to compare their records line by line.

Contract exit and data return clauses

Under UK GDPR, your organisation is normally the controller of your learners’ data and the LMS supplier is your processor. The Information Commission (still known as the ICO) explains that the contract between you must require the processor, at your choice, to delete or return all the personal data it has processed for you when the service ends. See the ICO guidance on what needs to be included in the contract.

In practice, that gives you a short list to check in your current agreement and data processing terms:

  • What format the data is returned in, and how long the supplier has to provide it.
  • Whether there is a charge for the export, or for help with it.
  • When access ends, and whether you can keep read-only access for a period.
  • When the supplier deletes the data, including backups, and whether they confirm deletion in writing. The same ICO page says backup data may not be deleted immediately, but it should be put beyond use and deleted as soon as possible.

Choose return first and deletion second, and do not ask for deletion until you have checked the export.

The new supplier will be your processor too, so you need a written contract with data processing terms in place before any real learner data moves. Ask where the data will be hosted, how it is backed up and which sub-processors are used.

How long to keep training records

A move is a good moment to tidy up. The ICO’s guidance on storage limitation says you must not keep personal data for longer than you need it, and that you should have a retention policy with standard periods. The same page recognises that some records must be kept to meet legal or regulatory requirements, and that you can consider keeping information you may need to defend a future legal claim.

For training records, that means agreeing with your HR and data protection leads how long you keep completions for current staff and for people who have left, then applying it before the move. Records you no longer need should not travel to the new platform. Records you do need, such as mandatory or safety training, should arrive intact with their original dates.

Moving completion records with their original dates

Users and courses usually move easily. Completion history is harder, because not every LMS can import past completions with their original dates and scores. If the new platform simply re-enrols everyone, your reports will show the whole organisation as overdue on the first morning.

You have three options:

  1. Import the history into the new LMS so each record keeps its original date, score and certificate. This gives you one place to report from.
  2. Keep an archived report, for example a locked spreadsheet and PDF certificates, stored in line with your retention policy. Cheaper, but you report from two places for a while.
  3. Carry forward current status only, so the new LMS knows who is in date and when they are next due, with the full history in the archive.

Whichever you choose, decide it before cutover and write it down, so you can explain it to an auditor later. Our post on audit-ready training covers what auditors tend to ask for.

Test migration: what to check

Never move everything in one go. Run a test migration with a sample of real data: a few departments, a mix of courses and some people who have left.

  • Upload each SCORM or xAPI package and check it launches, saves progress when closed halfway and records completion, score and pass or fail correctly.
  • Compare imported completions against the old system for your sample learners.
  • Check that single sign-on works for each user type, including contractors if they log in differently.
  • Test automatic enrolment rules, due dates and reminder emails with a test user before any real reminders go out.
  • Run the reports your managers and auditors actually use, and compare the numbers.

If older courses fail in the new platform, it is often a packaging issue that can be fixed by republishing. If the content itself is out of date, this is a good time to rebuild it. Our guide on turning PowerPoint and PDF training into SCORM explains the options.

Parallel running and cutover

A short period of parallel running lowers the risk. Typically, the new LMS goes live for new enrolments while learners finish anything already in progress on the old one, then a final export of those last completions is loaded before the old platform is switched off.

For the cutover itself:

  1. Set a cutover date and freeze changes to courses and users on the old platform a few days before it.
  2. Take the final export, load it and repeat your record checks.
  3. Switch single sign-on and any links on your intranet to the new platform.
  4. Keep a named person on hand for the first week to deal with login and enrolment problems.
  5. Confirm the old supplier has returned everything, then ask for deletion and written confirmation.

Communicating the LMS change to staff

Most problems on go-live are people who cannot find the new platform or think their completed training has disappeared. Tell staff before, during and after:

  • Two to four weeks before: what is changing, the date, and that their training records are coming with them.
  • The day before: the new link, how to log in and who to contact.
  • Go-live day: a short welcome message from the new platform, and a note to managers on where to find their team reports.
  • A month later: a reminder of anything now due, and a quick survey on what is not working.

How Capytech handles LMS migration

The Capytech LMS runs on your own domain with your branding, single sign-on with Microsoft or Google, and courses that work in the browser on any phone, tablet or desktop. It is hosted in the UK on AWS (London) with daily UK backups and a 99.5% availability service level, and it runs SCORM 1.2, SCORM 2004 and xAPI content. A standard branded LMS can go live in days.

We agree with you how your users and courses move across. Past completion records can be brought across with their original dates as part of a quoted migration, or kept as an archived report, and we agree which before work starts. If some of your courses are out of date, FastTrack can rebuild them from your own documents, and our custom e-learning service covers bespoke programmes. See the Capytech LMS for the full platform.

Frequently asked questions

What is LMS migration?

LMS migration is moving your learning content, users and training records from one learning management system to another. It usually covers SCORM or xAPI courses, user accounts and groups, completion and certificate history, and the reports and integrations around them.

How long does an LMS migration take?

It depends on how much data you have, how clean it is and how quickly your old supplier provides the export. Plan for a test migration, a period of parallel running and time to fix issues, and work back from your contract end date. Starting at least three months before your notice date gives you room to handle surprises.

Can I keep my completion records when I change LMS?

Yes, if you plan for it. Ask your current supplier for a full export of completions, scores and certificates with their original dates before you give notice, and check that it opens. Some platforms can import that history directly, and others keep it as an archived report.

What should be in an LMS migration checklist?

At minimum: contract end date and notice, a full data export, data return and deletion terms, a retention decision for old records, a test migration, parallel running, a cutover plan and staff communications. Each item needs an owner and a date.

Do LMS course migration services rebuild courses?

Some do and some only move the files. Moving a SCORM package is usually a re-upload and a test, while courses built in an old platform’s own editor may need to be rebuilt. Ask suppliers to say which courses they will move as they are and which need rework.

A branded LMS your people will actually use

The Capytech LMS and TMS gives you your own branded academy, a training calendar and reporting, hosted in the UK and run by our team.