LMS Migration Checklist: Project Plan, Timeline & Cutover Guide

A practical LMS migration checklist for switching learning platforms while protecting learner records, course content, certifications, integrations, and reporting continuity.

Mahesh KumarFounder, TraineryHCM.com

Updated on 8 min readFact-checked by the TraineryLMS team

Summarize with AI:ChatGPTClaudePerplexityGeminiGrok

LMS Migration

This guide is designed for HR, L&D, IT, compliance, and implementation teams that need a practical LMS migration checklist and project plan. It focuses on the parts that create the most operational risk: learner history, course behavior, mid-course progress, integrations, certification evidence, reporting continuity, user communications, and decommissioning the previous LMS.

If the organization is still evaluating whether to replace the current platform, use the LMS vendor evaluation guide first. If the new LMS has already been selected and the focus is configuration rather than switching systems, use the LMS implementation checklist. This page specifically covers migration from an existing LMS to a new LMS.

LMS Migration Checklist: The 10 Items to Confirm Before Cutover

Use this checklist as the project control layer. Each item should have an owner, acceptance criteria, and evidence that it has been completed.

<div class="table-wrap"><table class="compare"><thead><tr><th>Checklist item</th><th>What to verify</th><th>Evidence before go-live</th></tr></thead><tbody> <tr><td><strong>1. Migration scope</strong></td><td>Which users, records, content, certifications, assignments, and configurations will move, remain archived, or be retired.</td><td>Approved inventory and scope document.</td></tr> <tr><td><strong>2. Data mapping</strong></td><td>Every required source field has a destination, transformation rule, or archive decision.</td><td>Signed-off field map and exception list.</td></tr> <tr><td><strong>3. In-progress learning</strong></td><td>A defined treatment for learners who have started but not completed training.</td><td>Documented rule tested on real examples.</td></tr> <tr><td><strong>4. Course compatibility</strong></td><td>Representative SCORM/xAPI packages, video, documents, assessments, and proprietary content behave correctly.</td><td>Content test results with launch, resume, score, and completion checks.</td></tr> <tr><td><strong>5. Identity and access</strong></td><td>SSO, user provisioning, departments, roles, managers, permissions, and audience rules work as intended.</td><td>Access tests across representative user roles.</td></tr> <tr><td><strong>6. Integrations</strong></td><td>HRIS, virtual classroom, CRM, data exports, notifications, and other dependencies are connected and tested.</td><td>End-to-end integration test results.</td></tr> <tr><td><strong>7. Reporting</strong></td><td>Required operational and compliance reports can be reproduced using the new data model.</td><td>Approved report comparisons and sampled evidence.</td></tr> <tr><td><strong>8. User acceptance testing</strong></td><td>Learner, manager, administrator, and compliance scenarios pass with no unresolved critical defect.</td><td>UAT sign-off and defect register.</td></tr> <tr><td><strong>9. Cutover communications</strong></td><td>Learners and managers know when access changes, what happens to active training, and where to get support.</td><td>Approved communication and support plan.</td></tr> <tr><td><strong>10. Retention and decommissioning</strong></td><td>The previous LMS remains accessible for as long as legal, compliance, audit, contractual, or operational needs require.</td><td>Retention decision and decommission approval.</td></tr> </tbody></table></div>

Should You Migrate, Replace, or Consolidate Your LMS?

These terms overlap, but the project goal is different. Clarifying the goal prevents the migration team from treating a process redesign as a simple data transfer.

<div class="table-wrap"><table class="compare"><thead><tr><th>Project type</th><th>Primary goal</th><th>Main question</th></tr></thead><tbody> <tr><td><strong>LMS migration</strong></td><td>Move an established learning operation to a new platform.</td><td>How do we preserve required records, content behavior, and operational continuity?</td></tr> <tr><td><strong>LMS replacement</strong></td><td>Replace a platform that no longer meets business or learner needs.</td><td>Which requirements should the new LMS solve rather than simply recreate?</td></tr> <tr><td><strong>LMS consolidation</strong></td><td>Combine multiple learning environments into a governed operating model.</td><td>Which learner records, catalogs, rules, and owners become the system of record?</td></tr> </tbody></table></div>

What Data Should Be Included in an LMS Migration?

The migration inventory should distinguish between information that must remain active in the new LMS, information that must remain available as historical evidence, and information that can be retired. Moving everything can carry duplicate or obsolete data forward. Moving too little can break reporting, certification history, or learner continuity.

<div class="table-wrap"><table class="compare"><thead><tr><th>Data category</th><th>Examples</th><th>Migration control</th></tr></thead><tbody> <tr><td><strong>Learner profiles</strong></td><td>Employee ID, email, role, department, manager, location, employment status.</td><td>Identify the authoritative source and resolve duplicates before import.</td></tr> <tr><td><strong>Learning history</strong></td><td>Completions, attempts, dates, scores, exemptions, acknowledgments.</td><td>Define whether all attempts or only required historical states need to move.</td></tr> <tr><td><strong>Certifications</strong></td><td>Issue dates, expiration dates, renewal status, certificate files, supporting evidence.</td><td>Reconcile active, expired, and upcoming renewal populations. See <a href="../certification-tracking-software.html">certification tracking software</a>.</td></tr> <tr><td><strong>Courses and content</strong></td><td>SCORM, xAPI, video, documents, assessments, metadata, source files.</td><td>Test representative content in the destination LMS before bulk migration.</td></tr> <tr><td><strong>Assignments and learning paths</strong></td><td>Role rules, prerequisites, due dates, cohorts, recurrence, pathways.</td><td>Rebuild rules against current roles rather than copying obsolete logic. Review <a href="../learning-paths.html">learning paths</a>.</td></tr> <tr><td><strong>Integrations and configuration</strong></td><td>SSO, HRIS, virtual classroom, notifications, APIs, permissions, reports.</td><td>Document owners, dependencies, credentials, sync direction, and failure handling.</td></tr> </tbody></table></div>

How to Switch LMS Platforms Without Losing In-Progress Learning

Mid-course progress is one of the most important migration decisions because a learner may have started a course in the old LMS without producing a final completion record. Whether that partial state can be transferred depends on the source LMS, destination LMS, content standard, package behavior, and available export/import fields. Do not assume partial progress is portable simply because final completions are.

Before cutover, identify every active enrollment that is not complete and assign a treatment rule. Common approaches include:

  • Allow completion in the old LMS before cutover: useful when the remaining learner population is small and the course must preserve its existing state.
  • Restart the course in the new LMS: appropriate when partial progress cannot be transferred reliably and restarting does not create a compliance or learner-experience problem.
  • Transfer an agreed status or credit: only when the organization has evidence supporting the decision and the new LMS can represent that state correctly.
  • Keep the old LMS available temporarily: useful when a defined group needs to finish active learning while new assignments begin in the destination platform.

The correct choice is a governance decision, not just a technical one. Compliance, L&D, and system owners should agree on the rule before the final migration extract.

LMS Migration Project Plan: Six Controlled Phases

A realistic LMS migration timeline should be estimated after the inventory is known. There is no universal duration that applies to every organization. Data quality, content volume, integrations, custom configuration, regulatory requirements, procurement dates, and business-testing availability determine the schedule.

<div class="table-wrap"><table class="compare"><thead><tr><th>Phase</th><th>Core work</th><th>Exit criterion</th></tr></thead><tbody> <tr><td><strong>1. Audit and scope</strong></td><td>Inventory records, content, integrations, reports, active enrollments, owners, and retention requirements.</td><td>Scope, owners, exclusions, risks, and acceptance criteria are approved.</td></tr> <tr><td><strong>2. Data mapping and design</strong></td><td>Map source fields, define transformations, configure roles, audiences, and destination structures.</td><td>Field map and test configuration are ready.</td></tr> <tr><td><strong>3. Content and record migration</strong></td><td>Move test batches, validate content, import records, resolve errors, and document exceptions.</td><td>Migration batches reconcile and critical content behaves correctly.</td></tr> <tr><td><strong>4. Integration and workflow testing</strong></td><td>Test HRIS, SSO, virtual classroom, notifications, assignments, permissions, and reporting.</td><td>End-to-end scenarios pass with documented evidence.</td></tr> <tr><td><strong>5. User acceptance and cutover readiness</strong></td><td>Run learner, manager, administrator, compliance, and support scenarios; prepare communications and rollback decisions.</td><td>Business owners approve go-live.</td></tr> <tr><td><strong>6. Cutover and stabilization</strong></td><td>Run the final extract, switch access, reconcile records, monitor incidents, and close migration exceptions.</td><td>Required records and workflows are accepted and the old LMS has a governed retention plan.</td></tr> </tbody></table></div> <aside class="callout"><b>Planning an LMS Replacement?</b><p>See how Trainery connects learner records, content, certifications, integrations, learning operations, and reporting in one platform.</p><p><a class="btn btn-primary" href="../book-a-demo.html" style="color:var(--on-accent)">Book a demo</a></p></aside>

How to Migrate SCORM and xAPI Content

Do not move the entire course library before testing representative packages in the destination LMS. Choose examples that cover the oldest content, the most-used content, assessments, branching, resume behavior, certificates, and any package with known custom behavior.

For each test package, verify launch, bookmarking or resume behavior, score handling, completion status, assessment behavior, mobile delivery where required, and reporting output. Proprietary content created inside the old LMS may need a different migration path than packaged content. When source files are available, rebuilding selected content can be safer than trying to preserve unsupported native behavior.

For a more technical workflow, use the SCORM and xAPI content migration guide. For xAPI implementations, also validate the destination architecture's Learning Record Store and xAPI version requirements against the applicable xAPI specification.

How to Validate an LMS Migration

Validation should prove that the new LMS supports the required workflows, not simply that files and records were imported. Create acceptance criteria before testing begins and assign an owner to every failed test.

  • Data reconciliation: compare source and destination totals for active learners, historical completions, certifications, courses, assignments, and other required records.
  • Learner testing: confirm sign-in, assignment visibility, course launch, resume behavior, scoring, completion, certificates, and required notifications.
  • Manager testing: confirm team visibility, overdue status, assignment workflows, approvals, and report access.
  • Administrator testing: confirm imports, audience rules, permissions, notifications, scheduled reports, and exception handling.
  • Integration testing: confirm HRIS changes, SSO, virtual classroom events, APIs, and downstream exports.
  • Compliance testing: reproduce required reports and trace sampled records back to the underlying evidence.

For reporting-specific controls, review Trainery's training reports and analytics. For notification workflows, review the notification engine.

What Are the Most Common LMS Migration Risks?

<div class="table-wrap"><table class="compare"><thead><tr><th>Risk</th><th>Early warning sign</th><th>Control</th></tr></thead><tbody> <tr><td><strong>Incomplete learner history</strong></td><td>Imported totals do not reconcile with the approved source population.</td><td>Use record-count, field-level, and sampled learner reconciliation.</td></tr> <tr><td><strong>Broken course behavior</strong></td><td>Courses launch but do not resume, score, or complete as expected.</td><td>Test representative packages before bulk migration.</td></tr> <tr><td><strong>Lost in-progress learning</strong></td><td>Active enrollments have no agreed destination state.</td><td>Identify affected learners and approve a treatment rule before cutover.</td></tr> <tr><td><strong>Incorrect automated assignments</strong></td><td>New hires or role changes receive the wrong training.</td><td>Test role and audience rules using controlled HRIS scenarios.</td></tr> <tr><td><strong>Reporting mismatch</strong></td><td>Required reports disagree across the old and new systems.</td><td>Approve definitions and compare the same learner population.</td></tr> <tr><td><strong>Premature decommissioning</strong></td><td>Teams need historical evidence that is no longer accessible.</td><td>Do not close the previous LMS until retention and compliance owners approve it.</td></tr> </tbody></table></div>

How Should You Plan the LMS Cutover?

The cutover plan should specify the final data-extract time, which system is the source of truth during the transition, how active learners are handled, when SSO or links change, who validates the destination data, what conditions would pause the launch, and how support issues are triaged.

A controlled cutover also needs a rollback decision. Not every issue requires reverting to the previous LMS, but the project team should agree in advance which failures are serious enough to stop or reverse the switch. Examples can include failed authentication for a critical user population, materially incomplete learner records, broken mandatory training, or reporting that cannot reproduce required evidence.

When Can You Decommission the Old LMS?

There is no universal number of days that is appropriate for every organization. The previous LMS should remain available until the organization has satisfied its record-retention, audit, contractual, operational, and dispute-resolution requirements. A regulated employer may need a different retention approach from an organization using the LMS only for optional development content.

Before decommissioning, confirm who owns the archived records, how they can be retrieved, what format they are stored in, whether attachments and certificates remain accessible, and whether the organization can reproduce required evidence without relying on the old production environment.

How Do You Measure a Successful LMS Migration?

Define success before the first export. Useful measures include:

  • required learner and training records reconciled against the approved source population;
  • critical learner, manager, administrator, integration, and reporting workflows passed;
  • no unresolved critical defect at go-live;
  • successful learner authentication and course access after cutover;
  • required reports reproduced from the new system;
  • support issues categorized and closed during stabilization; and
  • retention and decommission decisions formally approved.

A smooth launch is useful, but continuity is the more important standard. The new LMS should preserve the records and workflows the organization still needs while eliminating the workarounds that justified the replacement.

<aside class="callout"><b>Planning to Replace Your Current LMS?</b><p>See how Trainery can support learner records, content, certifications, integrations, reporting, and training operations in one connected environment.</p><p><a class="btn btn-primary" href="../book-a-demo.html" style="color:var(--on-accent)">Book a demo</a></p></aside>

Frequently Asked Questions

How long does an LMS migration take?

A straightforward LMS migration: under 200 courses, a single HRIS integration, and a learner base under 2,000: typically takes 8 to 12 weeks from audit to go-live. Complex migrations involving multiple HRIS systems, large content libraries with proprietary format issues, or regulated compliance record requirements can take 4 to 6 months. The audit phase determines the actual scope; timelines set before the audit are estimates, not commitments.

What data can be migrated when switching LMS platforms?

Common migration candidates include learner profiles, completion history, attempts, scores, certifications, course metadata, packaged learning content, assignments, learning paths, and selected configuration data. What can actually be transferred depends on the export options of the source LMS and the import model of the destination system, so every required field should be mapped and tested before cutover.

Will switching LMS platforms affect our compliance records?

This depends on your industry's regulatory requirements. For most organizations, migrated completion records with accurate timestamps and scores are acceptable as audit evidence. For heavily regulated industries: financial services, healthcare, nuclear: the original system's records may carry more legal weight than migrated records, which is why maintaining the old system in read-only mode for 12 to 18 months is recommended. Clarify with your compliance team before migration starts.

Can we migrate SCORM content to a new LMS?

Yes, SCORM packages (1.2 and 2004) are designed to be portable. However, not all packages render identically in all LMS players: differences in how players handle JavaScript, branching logic, and suspend data can create unexpected behavior. Always test a representative sample of your SCORM library in the new LMS player before committing to the full content migration.

What happens to learners who are mid-course during an LMS migration?

In-progress learning needs an explicit cutover rule because partial course state may not transfer cleanly between platforms. Depending on the source LMS, destination LMS, content package, and available data, learners may finish in the old LMS, restart in the new LMS, receive an approved transferred status, or temporarily use both systems. Test the actual migration behavior before choosing the rule.

How long does an LMS migration take?

There is no universal LMS migration duration. The timeline depends on the quality and volume of learner data, number and type of courses, integrations, custom configuration, compliance requirements, available testers, procurement dates, and how much historical information must remain accessible. Build the schedule after the migration inventory and acceptance criteria are defined.

What should an LMS migration project plan include?

An LMS migration project plan should define scope, owners, data mapping, content migration, treatment of in-progress learning, integrations, identity and access, reporting, user acceptance testing, cutover communications, rollback criteria, post-launch validation, and the retention or decommissioning plan for the previous LMS.

Should you migrate all historical LMS data?

Not necessarily. Classify historical data by business, compliance, audit, contractual, and reporting need. Records that must remain active should move into the new LMS when the destination can represent them correctly. Other records may be better retained in a governed archive. The decision should be approved by the relevant L&D, compliance, legal, records, and system owners rather than based on age alone.

See how TraineryLMS fits your team

Book a demo and we’ll walk through the workflows in this guide with your own programs in mind.