Data Migration Plan – Stuck in LMS Limbo? Escape With Our 8-Step Strategy

Table of Contents

Are you putting up with an outdated, unsupported, not-fit-for-purpose learning management system (LMS) simply because the perceived effort of migrating the historical learning data to a new LMS feels overwhelming?

You’re not alone. Concerns about LMS data migration is a key factor that traps organisations into existing LMS platforms unnecessarily. In reality, LMS data migration isn’t as hard as it appears. It’s like all change management exercises – it needs to be broken into small steps. Like moving houses, it can also represent an opportunity to take stock of your training data and clean up!

On the flip side, not changing your LMS when better opportunities present itself may mean that the ‘cost of doing nothing’ (sticking with your existing LMS) may actually be far larger than any ‘cost of migration’. By sticking with an outdated LMS, you may be incurring:

  • Higher subscription costs (particularly if you are stuck on a stored user subscription, rather than an active user model)
  • Higher labour costs in managing training (particularly if your existing LMS cannot easily generate reports or automate enrolments)
  • Higher labour costs in managing users (particularly if your existing LMS cannot integrate with your user-data platform, like an HRIS or Microsoft 365)
  • Higher business costs from ineffective training (particularly if you are reliant on generic training modules from a library and unable to create your own customised, relevant training modules)

So in this article, let’s look at a solid data migration strategy to manage your LMS migration and free up your options to move to a new modern, fit-for-purpose LMS instead. It’s likely less effort than you think and the monetary rewards from completing the migration may be significant.

Step 1 – Clarify what data needs to be migrated

Not everything needs to be migrated from your existing LMS to your new one…

Pause and contemplate that for a moment.

Data Migration

Not everything needs to be migrated from your existing LMS to your new one… Pause and contemplate that for a moment. This one thought alone can dramatically reduce the effort of LMS migration. Yet too many organisations start with an assumption that ‘everything needs to be migrated’. The correct thought is ‘We need to extract all data out of our old LMS’ but that doesn’t mean ‘We need to migrate all data out of our old LMS’.

It may be OK to simply store some data in a CSV from your old LMS, but not actually move that data into your new LMS. For example, your users may have completed a module five years ago. That module may not be completely irrelevant to your organisation now and no new enrolments may have occurred in several years. This module and its training data does not need to be migrated. It just needs to be extracted and stored. If you need to look up this old record, you can do so. If you need to migrate this old record, you could do so at a later date once that becomes necessary.

LMS migration is a terrific opportunity to take stock, particularly if you are in an LMS which allows learners to find and complete random training modules of their own. That data can often be simply stored for future user if ever needed. Your focus needs to be on what training content remains in use and needs migration and what learning data needs to be accessible within the new LMS (typically compliance / licence data, or training data from the last 12 months). Let’s define this as scoping your migration to relevant training modules and data.

Step 2 – Clarify what data needs to be migrated by day one

Not all relevant training data needs to be migrated by day one.

Let’s define day one as the day you cut over from the old LMS to the new LMS for all (or the majority) of learners. Day one doesn’t require every single piece of content or data to be migrated. It only requires that you have migrated training content and data that is actually required by learners on day one – typically compliance and induction training. 

All those modules on leadership or productivity can actually wait a few days or weeks. It’s OK if someone can’t access a module on Microsoft Teams for a few weeks. What is needed on day one is the essential training – the content or data which is required for learners to do their jobs, such as completing induction training or finding license data. 

Everything else can be migrated after day one – perhaps as soon as day two, but for some relevant training modules and data it may even be week two or month two! 

Let’s define this as scoping your day one migration to essential training modules and data (the relevant training modules and data needed on day one). 

Step 3 – Migrate users first via spreadsheet or integration

Now we have significantly reduced the size of the migration. From all data to relevant data. But then further identifying which relevant data is essential for day one. 

So now you have two migrations: 

  • Essential data for day one 
  • All other relevant data from day two until you are done (on a scheduled plan) 

With that in mind, we can now set out the order of migration. You will need to start by migrating users – since you need users in place to record any historical training data. 

Ideally, you would migrate you users by: 

  • Extracting a CSV from the old LMS and uploading it into the new LMS, OR 
  • Establishing a user data integration into the new LMS from your user storage portal (your HR or Payroll platform, or your Single-Sign-On environment like Microsoft 365) 

Either way, migrating user data is relatively quick. This is also a good time to cleanse your learner data – fixing labels and data, importing new data from an integration and so on. 

Step 4 – Migrate and update content at the same time

After users are migrated, you may well need a second user migration at the time of cut over, but for now we have enough. We can now migrate your training content. 

This means (re)creating the training modules in your new LMS as they exist in your old LMS. However, this is another opportunity to take stock and improve your content. Typically, for each module in your old LMS, we need the migration process following five categories. 

Creating a simple spreadsheet listing all your modules and which category they fall into, and then assigning responsibilities for each module, is a great way to manage this step.  

Here are the categories: 

Use existing SCORM from the old LMS

If the module is SCORM and can be extracted from the LMS as SCORM (or you have the SCORM file), then reload the same SCORM into your new LMS. This is essentially an exact duplication of your existing content. 

Use a new library module from the new LMS

If the module cannot be extracted as SCORM from the old LMS BUT the new LMS has a library of ready-made content, then check if there is a similar module in that library. This is a ‘like for like’ swap and is a popular outcome for compliance training. 

Build a new module in the new LMS now

If the module cannot be extracted as SCORM from the old LMS AND there is no matching module available in the new LMS library AND this module is essential for day one, then consider if you want to recreate the module in the new LMS. Depending on your LMS, this may be easier than you think (and it’s a chance to improve and update your training content)!  

  • In Tribal Habits, for example, there is an easy to use online training creator, which involves a simple drag-and-drop interface – no harder than creating PowerPoint slides, but fully interactive instead. There is also a low-cost content conversion service to transform an old SCORM into a new module for you. 
  • Of course, if your new LMS doesn’t have excellent training content creation tools, then you will need to build new training in an external elearning authoring tool, pay an instructional designer to create a new SCORM module for you or buy a SCORM module from a third-party library. All the more reason to ensure your LMS is also capable of content creation itself. 
Build a new module in the new LMS later

If the module cannot be extracted as SCORM from the old LMS AND there is no matching module available in the new LMS library BUT this module is not essential for day one, then consider if you want to recreate the module in the new LMS at a later date. This allows you to stagger the creation of new modules over the first few weeks or months.

  • If creating many modules in weeks sounds daunting, it doesn’t need to be. Certainly, in older, complex elearning authoring tools, this would be difficult. But with modern drag-and-drop training creation platforms, creating training modules takes hours and days, not weeks and months. 
Do not migrate the module at all

The final option is the old content that will not be migrated or recreated at all. This might be old training modules no longer in use or elective modules which are no longer required. You may still want to store the training history for these modules, but you don’t need to create them in the new LMS for the migration.

As an example, we have helped organisations migrate from an existing LMS within a week, including all of the above steps. This is because they were able to match existing modules with those in our library (which requires just a few minutes) and use our online training creation tool to quickly recreate a couple of essential modules. All other modules were delayed until after day one. 

Step 5 – Migrate essential training data for day one

Once you have migrated the essential modules (the content required for day one) and your users, the next step is to migrate the historical training data for those essential modules and those users.

Once you have migrated the essential modules (the content required for day one) and your users, the next step is to migrate the historical training data for those essential modules and those users. 

This typically means downloading a CSV from your old LMS of the training data and uploading that training data into the new LMS for the matching modules.  

A tip is only to migrate two types of enrolments: 

  • Completed enrolments from the old LMS should be migrated as completed enrolments in the new LMS, so that users do not have to repeat training they have already completed. 
  • All other enrolments – new, in progress – are migrated as new enrolments in the new LMS. This reduces the complexity of the migration (and it’s also usually difficult to migrate a partially complete enrolment between LMS platforms). A tip here is to give notice to users in the old LMS of the cut over date and that only enrolments completed by that date will be migrated as complete. You can then watch the flurry of activity from learners who are partially completed! 

In a platform like Tribal Habits, you can upload a single CSV with all your old training enrolment data, matched to the relevant modules in Tribal Habits. Each row is a single enrolment to be migrated. We can accept the old completion date, plus existing expiry or certification date, so that the migration is almost a duplicate of your existing data. Our team is also very experienced at this data migration process and can provide template spreadsheets with formulas to accelerate the mapping of data between the two LMS. 

Step 6 – Launch with a pilot group before day one

Now it’s time to launch with a pilot group.

This is a final test of your new LMS. It allows you to check that the migrated data is accurate and that learners can access/navigate the new LMS. You can then adjust your communications for subsequent users. 

Step 7 – Cutover on day one with essential training data for all users

Now you can cutover from the old LMS to the new LMS for remaining users. 

You might need a final ‘interim’ migration to pick up any enrolment data updated in the old LMS between the first migration and your cutover date (so maybe 1-2 weeks of data). At this point, all new learning is happening in the new LMS. 

Step 8 – Migrate the remaining relevant content and training data over

Now you can plan out the remaining migration of other relevant training modules and training data, over the next few weeks and months. 

Successfully managing LMS data migration 

So there we have it – an 8-step process to manage your LMS data migration.

In practice, we have seen many organisations complete steps 1-6 within a few weeks (even faster when really required!). The critical decisions are in steps 1 and 2 – defining the scope of essential training content and data for day one.  

Like a house renovation, you don’t need to complete the entire renovation at once! You can focus on the key rooms you use every day and then update the remaining rooms as you go. This staged approach to LMS data migration can help you turn what appears to be a huge amount of work, into a manageable project over a few weeks…and allow you to get the benefits of a new LMS sooner rather than later. 


What should a data migration plan include?

A well-defined LMS data migration plan should address several key areas:

Scoping: Identify the essential training content and data required for users on day one of the new LMS launch. This helps prioritise migration efforts and reduces the overall workload.

Data Selection: Determine what data needs to be migrated (e.g., user information, course completion history) and what can be archived or excluded.

Migration Tools & Methods: Outline the methods for migrating data (e.g., CSV uploads, integrations) and any tools required to facilitate the process.

User Migration Strategy: Define the approach for migrating user data, including potential integration with existing user directories like HRIS or SSO platforms.

Content Migration Strategy: Determine how training content will be migrated, considering options like SCORM uploads, recreating content in the new LMS, or leveraging pre-built modules from the new LMS library.

Testing & Cutover: Establish a plan for testing the migrated data and the new LMS with a pilot group before launching to all users. Define the process for transitioning from the old LMS to the new one (cutover) and potentially address any interim data migration needs between the initial migration and cutover.

Post-Migration Activities: Outline any additional data migration for non-essential content or historical records after the initial launch.

What are the 4 types of data migration?

There isn’t a universally agreed-upon categorisation of data migration types, but here are four common approaches that can be applied to LMS migration:

Full migration: This involves transferring all data from the old LMS to the new one. While comprehensive, it can be time-consuming and may not always be necessary.

Partial migration: This focuses on migrating essential data for day-one functionality, such as user profiles, core training modules, and completion history. Non-essential content or historical data can be migrated later or archived.

Content-focused migration: This prioritises migrating training content (e.g., SCORM packages, modules) while potentially leaving user data behind or migrating it through separate means (e.g., integration with existing user directories).

Staged migration: This breaks down the migration into phases, prioritising essential data for launch and then migrating remaining content and historical records over time.

What is data migration strategy?

A data migration strategy defines the overall framework for moving data from one system (old LMS) to another (new LMS). It encompasses the planning process, including defining the scope, selecting tools and methods, establishing a timeline, and assigning resources. An effective strategy considers factors like data volume, complexity, downtime tolerance, and budget constraints.

How do I document a migration plan?

There’s no single format for a data migration plan, but it should be clear, concise, and easy to follow. Here are some suggestions:

  • Use a step-by-step approach, outlining each stage of the process.
  • Include tables or diagrams to visualise data flows and migration processes.
  • Define roles and responsibilities for each stage of the migration.
  • Specify timelines and milestones for completion of different tasks.
  • Include a communication plan for keeping stakeholders informed throughout the process.
How long does LMS data migration typically take?

The timeframe for LMS data migration can vary significantly depending on several factors:

Complexity of data: The amount and type of data you need to migrate will impact the overall time. A simple migration with basic user information and course completions might be completed faster than one involving complex learning paths and customized content.

Migration approach: Full migration will take longer than a staged approach focusing on essential data first.

Available resources: The size and experience of your migration team will influence the speed of the process. Expertise in LMS migration and data management can expedite the project.

Toolset and integrations: Utilising automation tools and established integrations between your old and new LMS can streamline the migration process.

While there’s no one-size-fits-all answer, the 8-step process outlined in this blog post can often be completed within a few weeks, especially when focusing on essential data for day-one functionality.

What are the biggest challenges of LMS data migration?

Here are some common challenges to consider:

Data cleansing: Your existing LMS data may contain inaccuracies, inconsistencies, or outdated information. Addressing these issues before migration ensures data integrity in the new system.

Content conversion: Converting legacy training content to a format compatible with the new LMS can be time-consuming, especially for complex modules or those not built with SCORM standards.

Downtime considerations: Depending on the migration approach, there may be some downtime for users while transitioning from the old LMS to the new one. Planning and communication can help minimize disruption.

Project management: Coordinating various tasks, resources, and stakeholders throughout the migration process requires strong project management skills to keep things on track.

What are the benefits of LMS data migration?

Investing in LMS data migration can unlock several advantages:

Improved User Experience: A modern LMS can offer a more user-friendly interface, enhanced features, and better accessibility for learners.

Enhanced Functionality: New LMS platforms may offer features like advanced reporting, automated workflows, and improved content management capabilities.

Reduced Costs: Transitioning from outdated or expensive LMS platforms can lead to cost savings in the long run.

Increased Scalability: A modern LMS can accommodate your organization’s future growth and evolving training needs.

Improved Compliance Management: New LMS features can streamline compliance tracking and reporting for regulated industries.


Shopping cart


No products in the cart.

Continue Shopping