The time has come—you’re ready to move your customer education or learning and development program to a new learning management system (LMS) vendor and leave your legacy LMS behind.
Key Takeaways
- An LMS migration moves three types of data: content, users, and enrollments. Migrate active users and completed enrollments, and back up every record first.
- Start an LMS migration about 12 months before your current contract ends.
- An LMS migration checklist covers six phases: preparation, key dates, data migration and validation, a pilot, learner communication, and post-launch support.
- The vendor runs the import and platform configuration; your team audits content, exports packages and completion records, and completes the intake forms.
- Plan for about a day of downtime at cutover, and set a cutoff for in-progress enrollments so learners finish before the final data pull.
When choosing a new LMS, you want to make sure you understand what the LMS partner will do, and what your team will be required to do as part of the process.
Whether you’re in the early planning stages or actively preparing for the switch, read on for an LMS migration checklist, the questions to ask vendors, and the pitfalls to avoid.
What is an LMS Migration?
An LMS migration is the process of moving a customer, partner, or employee learning program from one learning management system to another. It covers three types of data: learning content, user records, and enrollment history. It also covers the decisions around that data: what to move, rebuild, or retire, when to cut over, and how learners make the switch.
When’s the Right Time to Migrate Your LMS?
There are three signs it’s time to switch LMS platforms.
In our webinar on migrating LMS platforms, Intellum welcomed Justus Mueller, a Senior Program Manager at blockchain data platform Chainalysis.
For Mueller, implementing a new LMS is more than just picking a new vendor; it’s rightsizing your entire program. “Migration is never just a technical lift,” he explained. “It's an opportunity to rethink how you do things and how you operate.”
1. Too many manual workarounds.
As your program grows, so does its complexity. Processes that once took hours now take weeks. Systems that once felt nimble now feel cumbersome. While some degree of technical debt is unavoidable, too much means you’re wasting time on tools instead of teaching.
If work feels “unnecessarily complicated,” as Mueller put it, then it’s time to reassess your current setup. “Over time, people leave, people come; practices change a little bit. It just compounds and gets worse and worse.”
2. Your LMS is no longer a partnership.
If you’ve worked with vendors in the past, you know the feeling well. The vendor rolls out the red carpet for the first 90 days, or even the first year, only for emails to slow, pleasantries to cease, and support to dry up. What felt like a transformational tool now feels transactional.
Mueller put it perfectly. “The LMS you're working with feels more like a subscription and less like a partnership.” If your vendor no longer seeks to improve your program or deepen their relationship with your team, take their energy at face value; it may be time to move on.
3. The program has outgrown the platform
You might love your vendor and their solution, but if the LMS capabilities can’t support your current growth trajectory, a change may be in order.
In this scenario, it’s at least worth having a conversation with your vendor. Perhaps an add-on or integration could unlock additional growth. If you’re a big enough client, or you’ve worked with them for a while, they might be able to prioritize features on their roadmap or custom-build new capabilities.
Don’t let your love of an existing tool hamper your growth, however. If your needs cannot be met within a reasonable timeframe—weeks, not months—pivoting to a new platform may be the fastest, most effective way to accelerate your program.
The “right time” for an LMS migration depends heavily on your program, its goals, and your broader business strategy. If you’re bringing on a massive new enterprise account, for instance, now might not be the right time to shake up their customer onboarding process.
How Long an LMS Migration Takes
Start the conversation a full year in advance, so you can gain alignment, pick your preferred alternative, and have an implementation plan in place once it’s time to switch. Chainalysis started 8 to 10 months before its previous contract ended and spent about two months on requirements and vendor selection.
Most LMS contracts are multi-year agreements. If you’re entering the final year of a contract, don’t wait until renewal time to start your search—otherwise, you’ll be left scrambling.
| Time before contract ends | Milestone |
|---|---|
| 12 months | Start the search and align stakeholders |
| 10 months | Requirements set, vendor chosen (Chainalysis took about 2 months) |
| 8 months | Contract signed, kickoff with the new vendor’s implementation team |
| 2 months | Pilot with a small user group |
| 1 week | Cutoff for in-progress enrollments; final data pull |
| 1 week | Cutover: about a day of downtime while the platforms switch |
| 1 week | Go-live, with buffer before the old contract ends |
Mueller shared, “We spent roughly two months figuring out, ‘Okay, what exactly do we need in this new LMS system? What LMS system should we go with?’ And then after that was obviously the migration implementation. But it gave us enough time. You don’t want to leave that too late.”
How to Choose an LMS Vendor for Your Migration
Choose a vendor in three steps: build your requirements list, ask each shortlisted vendor how it handles migration, and keep your current vendor in the running.
Build your requirements list.
For Mueller, it’s crucial to have a clear list of requirements. Differentiate your must-haves from your nice-to-haves and your optional requirements. Cross-reference each requirement against LMS vendors in the field, and shortlist the few solutions that bubble to the top of the list.
Define your must-haves: e.g., custom branding, user segmentation, automated notifications, integrations, or multilingual support.
“In the end, there’s so many things to think about, all these companies you’re talking to, and they have good salespeople,” recalled Mueller. “It’s [hard to] not just immediately fall in love with the first platform you look at to make your life easier and go, ‘Yeah, let’s just go with this one and move on.’”
Here are some internal questions Mueller recommends when evaluating LMS vendors:
- Which are our must-have features that, if missing, would disqualify a vendor?
- What integrations connect to our current LMS? Will those migrate, or can they consolidate?
- Is this vendor offering a true partnership, or just help with initial implementation?
Ask how the vendor handles migration.
Once you’ve aligned on a shortlist of potential LMS vendors, it’s time to get that list down from a handful to one.
Here are five questions to ask a potential vendor about their migration process:
- Do you migrate the full course with metadata, or only the content asset?
If the provider migrates only the content asset itself, be aware that you’ll need to manually input the supporting course properties after the fact.
- Are completed enrollments migrated with status, date, and expiration?
Determine if your new platform will migrate over the completion date, completion status, and expiration date.
The ability to migrate data points from your LMS is key, as some platforms can automate the re-enrollment process based on course expiration dates, like we do here at Intellum.
- Can we migrate custom fields and detailed user properties?
Whether it’s standard or custom data, the more user profile details you can move over to the new platform, the better. Ask your potential LMS vendor if you’re able to migrate all the properties you previously used to define a user profile to the new platform.
Here at Intellum, we can accommodate more than 20 standard fields, plus additional custom fields, when migrating content over to our platform.
- What hands-on migration assistance is included?
Your chosen provider should be proficient in both migration best practices and LMS implementation to improve the structure and organization of the educational experience.
- Are there additional costs for LMS migration support?
Learn what the migration services include ahead of time. This keeps you from receiving an unexpected bill when you need assistance down the line.
Pro tip: Need help figuring out what to put on your RFP? Don't start from scratch. Download our free RFP template for 200 must-ask questions.
Keep your current vendor on the shortlist.
Sometimes, it’s equally important to know when not to migrate to a new vendor. Unless you are dead set on switching vendors, keep your existing LMS vendor as a potential option on your shortlist. You might find there’s a path forward you didn’t even realize.
What to Migrate, Rebuild, or Retire
Plan your LMS data migration around three data types separately: content, users and enrollments.
| Data | Migrate | Rebuild or retire | Back up |
|---|---|---|---|
| Content | Current, high-engagement assets in supported formats | Outdated, duplicated or low-engagement assets | Everything |
| Users | Active users | Inactive users | All records |
| Enrollments | Completed, with date, status and expiration | In-progress (set a completion cutoff) | All records |
- Audit and inventory your content. Build a list of all training assets (e.g., eLearning, videos, PDFs, quizzes) and assess relevance, engagement, and compliance. Prioritize compliance training and certification content so requirements don’t lapse during the switch. Tag content for migration, revision, or retirement, and categorize it by initiative or audience. To track each decision asset by asset, download the content and data inventory worksheet. It also covers user and enrollment records.
- Decide what to rebuild. Determine which elements (courses, certifications, learning paths) should be rebuilt from scratch, especially if they’re outdated, duplicative, or not aligned with your current strategy.
- Focus on learning content only. You may have used your previous LMS more like a content management system by storing general marketing and sales enablement materials alongside learning content. Make sure your customer education content focuses on learning activities only (e.g., certification, courses, eLearning, help content, etc.) in the new platform, rather than general marketing or sales information.
- Build a course and curricula catalog. Document course objectives, intended audiences, prerequisites, and format types (e.g., SCORM, xAPI, videos, instructor-led), and which version of each is current.
- Evaluate content compatibility. Confirm which file formats (SCORM 1.2, xAPI, MP4, etc.) will work in the new LMS, and flag anything that will need conversion or rework. If your content library is built in SCORM, see what to expect when migrating SCORM content to Intellum.
- Anticipate any branding changes. Your team also needs to consider whether you’ll add or change your branding while moving to a new LMS platform. Only a subset of LMS platforms support custom branding, so you’ll want to verify this is possible if it’s a key requirement.
Who Does What During an LMS Migration?
An LMS migration is shared work. The vendor runs the technical import and platform configuration; your team supplies the files, the data, and the decisions about what moves. Knowing the split before you sign tells you how much of your team’s time the migration will need, and where delays usually come from.
At Intellum, the work of migrating content and enrollment data is divided like this:
| Intellum’s services team | Your team |
|---|---|
| Provides an intake form template and a secure SFTP environment for your files | Audits your library and decides what to migrate, refresh, or archive |
| Imports your content files and legacy enrollment data | Exports SCORM packages and completion records from your current LMS |
| Runs the bulk jobs that create each activity record and link it to its package | Completes the intake form, adding metadata and mapping each package to its activity |
| Configures the platform | Uploads your packages to the SFTP environment |
| Bulk-imports in-progress enrollments, if you supply the data and need them carried over | Sets the cutover date and asks learners to finish in-progress activities before it |
Whichever vendor you choose, ask for this split in writing during evaluation, along with what’s included in the price. Intellum’s implementation services handle the file import, data migration, and platform configuration during implementation.
LMS Migration Checklist
An LMS migration checklist covers six phases: preparing before you migrate, setting key dates, migrating and validating data, running a pilot, communicating the change, and supporting the platform after launch.
Download the LMS migration checklist to print it, add your own dates, and check off each step.
Before you migrate.
- Conduct a pre-migration planning session. Form a migration team with stakeholders from Education, IT, Support, and Ops. Clarify roles, goals, and assumptions to avoid blind spots later.
- Document user groups and enrollment rules. Map how users are segmented today and how they access content. Include permissions, enrollment triggers, and group-level assignments.
- Catalog all system communications. List automated messages and notifications your current LMS sends (e.g., reminders, expirations, completion emails). Identify gaps or frustrations to improve in your next system.
- Define success metrics. Common goals for a successful migration include improved learner experience, increased content adoption, streamlined administration, and reduced support inquiries. If your program supports a business goal, add the metric the business already tracks for it, such as product adoption, renewal rate, or time to proficiency, and record its value before the switch so you can compare after.
- Anticipate any branding changes. Communicate brand needs as quickly as possible, as they can significantly delay the migration process.
Set key dates.
- Set a cutoff for completing “in-progress” enrollments. Determine a date by which learners should complete ongoing courses to prevent data loss during migration.
- Schedule the migration window. Plan for a period with minimal user activity to reduce impact. Expect about a day of downtime at cutover; anything that changes after the final data pull, such as a learner finishing a course, has to be pulled and updated again.
- Plan internal testing and pilot review dates. Allocate time for thorough testing before full deployment.
- Establish the anticipated go-live date. Communicate this clearly to all stakeholders to align expectations.
Migrate and validate the data.
- Validate data post-migration. Conduct checks to confirm all data has been accurately transferred and is functioning as expected.
Run a pilot.
- Select a pilot user group. Choose internal teams or trusted customers to test the new LMS.
- Test course delivery, enrollments, and user experience. Use surveys or interviews to gather feedback on usability, functionality, and flow.
- Make adjustments before a full rollout. Implement changes based on pilot feedback to enhance the user experience.
Communicate the change.
When sharing your rollout plans, focus on what’s changing, why, and when. Reassure your customers that you’ll communicate more information or instructions when it’s needed. Be sure to share up-to-date timelines with your customers, and prepare existing users if you expect any downtime in access to the learning environment.
- Notify learners about the new platform and why you’re switching. Provide clear reasons and benefits to encourage buy-in.
- Share expected timelines, known downtimes, and FAQs. Keep users informed to manage expectations.
- Provide links to support materials and onboarding instructions. Offer resources to help users navigate the new system.
- Establish a feedback channel. Allow users to report issues and suggest improvements during the transition.
After launch.
- Train administrators and support staff. Cover the tasks each role will handle in the new platform, such as enrolling users, running reports, and answering learner questions, before go-live.
- Monitor system performance post-migration. Keep an eye on system stability and user engagement metrics.
- Plan for ongoing support and improvement. Establish a process for continuous improvement based on user feedback and performance data.
Plan Your LMS Migration With Intellum
If you’re planning a switch, book a demo to walk through how Intellum’s services team would handle your migration. If you’re still building your shortlist, use our LMS RFP template to put the same questions to every vendor.
FAQs
What goes in an LMS migration project plan?
An LMS migration project plan sets the dates that control the move: a cutoff for in-progress enrollments, the migration window, internal testing and pilot review, and go-live. It also assigns who exports data, who imports and configures it, and when learners are told. Chainalysis began planning 8 to 10 months before its previous contract ended.
What data is included in an LMS data migration?
An LMS data migration covers three types of data: learning content, user records, and enrollment history. Most teams migrate active users and completed enrollments with their completion date, status, and expiration date, and back up every record from the old platform first, including inactive users and in-progress enrollments they choose not to import.
What do LMS migration services include?
LMS migration services cover the technical side of the move. At Intellum, the services team imports content files and enrollment data, creates activity records, and configures the platform, while your team exports data, decides what to migrate, and supplies metadata. Ask every vendor whether hands-on migration help is included in the price.
How do you migrate content between LMS platforms?
To migrate content between LMS platforms, audit every asset and tag it to migrate, revise, or retire based on relevance and engagement. Confirm the new platform supports each format, such as SCORM 1.2, xAPI, or MP4, and flag anything that needs conversion. Low-engagement content is often better rebuilt than moved as it is.




