LMS Migration Checklist: Switching LMS Vendors
Moving to a new learning platform is rarely a technical problem. It goes wrong when nobody decides early enough which records have to survive. What to export before you switch, what actually transfers between platforms, an eight-step checklist, and the audit drill to run before you cancel the old contract.
By the CompanyLMS team
July 2026 · 11 min read
Last updated July 2026.
An LMS migration moves your users, courses, enrollments and completion history from one learning platform to another. Plan on four to twelve weeks for a mid-market move. Export five things before you touch anything: the user list with IDs, the course catalog, current enrollments, every completion record with its date, and your issued certificates with expiry dates. Course content usually transfers if it is SCORM. Completion history, certificate expiry clocks and reporting almost never transfer automatically, and those are the ones an auditor asks about.
Most people arrive at this problem in the same way. The renewal quote came in higher than expected, or the platform never did what the demo promised, and now there is a folder of eight years of training records nobody wants to be responsible for losing. The good news is that the technical part is rarely what goes wrong. The part that goes wrong is deciding too late what has to survive the move.
What is an LMS migration?
An LMS migration is the process of moving learning data and content from one learning management system to another, including users, course files, enrollments, completion records and certificates. It is part data export, part content re-upload and part rebuilding the assignment rules and reports that made the old system useful. The data move is usually the easy half.
It is worth separating two things that get bundled together. Migrating content means getting your courses into the new platform. Migrating records means preserving the evidence that people completed those courses. Vendors talk mostly about the first because it demos well. Compliance teams care almost entirely about the second, because that is what gets requested during an audit, an OSHA inquiry or an EEOC complaint.
What data should you export before switching LMS platforms?
Pull these exports while you still have full admin access to the old system, and store them independently of both platforms. A CSV on your own file server is the version you will be glad you have in three years.
| What to export | Why it matters | The gotcha |
|---|---|---|
| User list, active and inactive | Every record downstream keys off a person. Include employee ID, email, department, location, job title, hire date and group memberships | Leavers are often filtered out of the default export, and their records are exactly the ones you may need for a retention period |
| Course catalog and source files | The SCORM, xAPI, video, PDF and instructor-led session definitions you actually own | Content licensed from a third-party library does not come with you. Check every course for a vendor watermark before assuming it is yours |
| Current enrollments and assignments | Who is mid-course right now, and what is assigned but not yet started | In-progress scores and bookmarks rarely survive. Plan a cutover date and let people finish or restart |
| Completion records with dates | The audit evidence. Name, course, completion date, score, and pass or fail | This is the export most often left until last and most often incomplete. Verify the row count against the platform's own reporting before you cancel |
| Certificates and expiry dates | Anything with a renewal clock: OSHA refreshers, HIPAA, forklift evaluations, professional licenses | Certificate PDFs and the expiry metadata are usually two separate exports, and some platforms only expose the PDF |
| Assignment rules and automations | The logic that sends the right course to the right role, location and new hire | There is no export format for this. Screenshot every rule, because rebuilding from memory is where migrations quietly lose requirements |
| Saved reports and dashboards | The reports your compliance lead and managers actually run each month | Report definitions never transfer. Write down the filters and columns for the five reports people genuinely use |
What actually transfers between LMS platforms, and what does not
This is the table worth sending to whoever signed off on the project, because expectations here are usually wrong in one direction.
| Item | Transfers? | What to expect |
|---|---|---|
| SCORM 1.2 and SCORM 2004 packages | Usually yes | Re-upload as a package. Test one course end to end before bulk loading, since completion tracking behavior varies between platforms |
| xAPI and cmi5 content | Usually yes | Confirm the new platform supports the specific version. Statements already sent to a learning record store stay where they are |
| Video, PDF and native-built courses | Files yes, structure no | Media moves easily. Anything authored inside the old platform's editor has to be rebuilt, which is often the largest single task |
| Users and group structure | Yes, by import | Straightforward CSV work. Better still, provision from your HRIS or directory so the two never drift again |
| Historical completion records | By import, if the new platform allows it | Ask this question during the sales cycle, not after. Some platforms accept a historical completions import, some only let you attach a file to a profile |
| Certificate expiry clocks | Rarely automatic | Usually rebuilt by importing completion dates and letting the new platform recalculate renewals from your recurrence rules |
| In-progress course state | No | Bookmarks, partial scores and quiz attempts stay behind. Set a cutover date and communicate it two weeks ahead |
| Assignment rules, reports, branding | No | All rebuilt by hand. Budget real time for this, because it is the work that makes the new system usable rather than just populated |
The eight-step LMS migration checklist
This sequence assumes a company between 100 and 2,000 employees moving from one cloud LMS to another. Scale the timeline, not the steps.
1. Decide what has to survive, in writing. Before anything technical, agree with whoever owns compliance which records must be preserved and for how long. Bloodborne pathogens training records carry a three-year retention requirement under 29 CFR 1910.1030(h)(2)(ii), and exposure records run to thirty years under 1910.1020. Regulated industries usually have more. Everything else is a preference, not a requirement, and treating preferences as requirements is what turns a six-week project into a six-month one.
2. Pull every export while you still have access. Do this on day one, not at the end. Contracts lapse, admin seats get removed, and vendors are not obliged to restore access after termination. Take the seven exports in the table above, verify the row counts against the platform's own reporting, and put the files somewhere neither vendor controls.
3. Clean the user data before you import it. Duplicate accounts are the single most common cause of a messy migration. Someone who changed their surname or moved from a contractor email to a staff email often exists twice, with half their history on each record. Merge in the source data, not in the new platform. Match on employee ID rather than email wherever you can.
4. Inventory content by format and by ownership. List every course with its format (SCORM 1.2, SCORM 2004, xAPI, cmi5, video, PDF, instructor-led) and whether you own it or license it. Our comparison of SCORM vs xAPI covers what changes when the format differs, and it matters here because a platform that only supports SCORM 1.2 will quietly break xAPI reporting.
5. Rebuild assignment logic first, content second. Counterintuitive but correct. The rules that route training to roles, departments, locations and new hires are what make the platform run without an administrator. Get those right on a handful of courses, test them with a fake new hire starting next Monday, then bulk load. Loading 200 courses into a system with no assignment logic just gives you a catalog nobody is enrolled in.
6. Connect your people data properly. If your HRIS or directory can provision users through SCIM or an API, set it up during the migration rather than after. It is the difference between a user list that stays accurate for years and one that starts drifting the week after go-live. Where the two systems do not speak the same language natively, a general-purpose layer that can connect apps, APIs and databases is usually cheaper than a custom sync script somebody has to maintain.
7. Run both systems in parallel for two to four weeks. Keep the old platform readable while the new one becomes the system of record. Assign one real compliance course to one real department in the new system and watch what happens: does the reminder fire, does the manager see the overdue report, does the certificate issue with the right expiry date. Fix what breaks before you move everyone.
8. Do the audit drill before you cancel the old contract. Pick an employee at random and produce their full training status as of a date last year, with dates and certificates, using only the new system and your exports. If you cannot do that in under five minutes, you are not finished. This is the test that reveals a missing export while you can still go back and pull it.
How long does an LMS migration take?
Four to twelve weeks is the honest range for most mid-market moves. Under 200 employees with fewer than 30 courses can genuinely be done in two to three weeks. Between 200 and 2,000 employees, six to eight weeks is typical, and the variable is almost never the data import. It is how much content was authored inside the old platform's editor and therefore has to be rebuilt.
Enterprise migrations with multiple portals, several languages, integrations to a talent suite and a long retention obligation run three to six months, and are usually run as a project with a named owner rather than as extra work on someone's existing job.
How much does an LMS migration cost?
The license difference is rarely the biggest number. Budget for three things: implementation or migration services if the new vendor charges them, which is common at the enterprise end and often a four or five figure one-time fee; internal time to rebuild content and assignment rules, which is the largest real cost for most companies; and an overlap period where you pay for both platforms for a month or two.
A useful rule of thumb is that rebuilding content costs more than the software. If 40 courses were authored in the old platform's editor and each takes three hours to rebuild, that is 120 hours before anyone has been trained on anything. Platforms that can generate a draft course from your existing policy or SOP documents cut that number substantially, which is worth weighting in the selection. Our LMS pricing comparison covers the license side across ten vendors, and the employee training software comparison ranks the same platforms on capability.
Common LMS migration mistakes
Cancelling the old contract before the audit drill. The export that turns out to be incomplete is always discovered after access is gone. Keep the old platform readable for at least a month past go-live.
Migrating everything. Eight years of completion records for people who left in 2019 does not need to live in the new platform. Archive it as a CSV against your retention policy and migrate only what is current or still required. Smaller migrations succeed more often.
Treating certificate expiry as data rather than logic. Importing a completion date is not the same as recreating the renewal rule that fires 60 days before it lapses. Rebuild the recurrence rules explicitly and test one that is due soon. Our guide to tracking employee certifications covers what those rules need to do.
Skipping the parallel run. Every migration looks finished until a real reminder fails to send to a real person. Two weeks of overlap costs one month of double subscription and catches almost everything.
Not asking about historical imports during the sales cycle. Whether a platform accepts a bulk import of past completions is a hard yes or no, and it changes the whole project. Add it to your LMS RFP alongside the SSO and reporting questions.
Should you migrate at all?
Sometimes the answer is no. If the complaint is that nobody completes training, a new platform will not fix it, because completion is usually an assignment and accountability problem rather than a software problem. If the complaint is price, get a renewal quote and a competing quote before committing to a project, since renewal negotiations move more often than people expect.
Migrate when the platform genuinely cannot do something you need: recurring assignment with per-employee due dates, historical reporting an auditor will accept, provisioning from your directory, or pricing you can forecast. Those are structural gaps, and no amount of process fixes them. If you are weighing specific vendors, our comparisons of the Docebo alternatives, Cornerstone alternatives and TalentLMS alternatives cover where each platform tends to hit its limit, and training tracking software covers what the record side has to do once you land.
This article is general information about learning platform migrations, not legal advice. Confirm your own record retention obligations with counsel or your compliance lead.
See CompanyLMS train your teams
Build courses, launch employee onboarding and compliance training, track skills across teams, and issue certifications, all in one corporate LMS, with completion visible on a single progress dashboard.