Limited time offer! 25% off our lifetime plans with code LMT25 at checkout. View plans →

Development

How to Plan an LMS Cutover the Way You’d Plan a Server Migration

On this page

How to Plan an LMS Cutover the Way You'd Plan a Server Migration illustration 1Source: Pexels

At some point, most companies outgrow their learning platform. Maybe SSO never worked right. Maybe the vendor got bought, and the roadmap went quiet. Maybe the renewal quote came back at double last year’s price. Or the business just needs something the current system is never going to do. Either way, every LMS contract ends one of two ways: you renew, or you move.

IT teams who inherit the move are often caught off guard by one thing. This isn’t like switching one SaaS subscription for another. It’s much closer to moving a production server. Think inventory first, then export formats, a place to test, a booked cutover slot, and an escape route. Forget any one of them, and you’ll probably end up in a well-known statistic. McKinsey once studied large IT projects and found they run 45 percent over budget on average while delivering 56 percent less value than predicted. Migrations with messy data feed that number more than most.

Why LMS moves go sideways

Open up an LMS and you won’t find one thing. You’ll find user accounts, course files, enrollments and a long tail of completion records, all only loosely tied together. People assume all of that moves in one go. It doesn’t.

Course packages travel well. Learning histories, certificate links and competence profiles don’t, because they’re built around the old system’s data model. Vendors who run these projects all the time will tell you straight away that a clean one-to-one transfer almost never happens. One of the first things they’ll ask is whether your old records need cleaning up before anything is moved.

And those records are worth more than they seem. In a regulated industry, a completion log is evidence. If you lose the record showing who finished safety training in 2023, that’s not an inconvenience. It’s a hole in your compliance file.

Step 1: Inventory the data before touching anything

Start with a list of everything that has to move. Most teams are surprised by how long it gets:

  • user data;
  • learning histories;
  • the course content itself;
  • courses and programs;
  • training locations;
  • job and competence profiles;
  • test questions.

Each item on that list needs a person responsible for it and a verdict: migrate, archive or delete.

Being picky now pays off later. Treat lms migration projects like you’d treat moving a production database: no category gets exported until it has its own written spec. Vendors who do this a lot split the job into up to ten phases. Simple datasets go through standard import scripts. Anything with linked records gets a custom one, and certificates tied to competence profiles are the textbook example.

The inventory is also a good excuse to clean up. Six years of outdated course versions? A migration is the only time getting rid of them is basically free.

Step 2: Pin down the formats that make content portable

Why is course content the easy part? One word: SCORM. The standard is maintained by the ADL Initiative, part of the US government, and it bundles a course into one archive you can carry from system to system. ADL’s own documentation calls packaging a standardized portability mechanism between various learning environment applications. If your courses follow SCORM, they should open on the new platform without being rebuilt. Check anyway. Pull one course out, drop it into a trial instance, and see if tracking still works.

Then go hunting for the stuff that was never packaged. Every older LMS has it. Pages someone built by hand in the authoring tool. A trainer’s PDF from 2019. A slide deck. A video that points to a shared drive IT shut down years ago. You can’t export any of that as a neat package, so each item needs its own call:

  • rebuild it on the new platform if people still take the course;
  • archive a copy outside the LMS if you only need it for reference;
  • drop it if nobody has opened it in two years.

Making that call during the inventory costs very little. Finding out in cutover week costs a lot more.

Activity data works differently. The newer xAPI standard records learning as actor-verb-object statements, stored in a Learning Record Store. That store can be part of the LMS or run on its own. If yours already runs on its own, moving your history could be far easier, because the records don’t live in the system you’re leaving. SCORM and xAPI aren’t the whole story either. Some content leans on AICC. Connected tools often run over LTI, test questions may sit in QTI, and anything custom probably talks through a REST API. Know which ones you have before the move.

Step 3: Build a test environment and expect correction loops

Nobody who’s done this before cuts over a database on the first import. LMS data is no different. What works, and what most vendors now do, is simple enough: run a trial migration into a test environment, write down every error, fix the mappings, and go again. Keep going until the error log is quiet. On bigger projects, you’ll go round that loop several times. That’s normal. It doesn’t mean something’s wrong.

Plan your time with that in mind. According to vendor guidance, moving basic user data and learning histories with standard scripts can take around a week. For a larger project, about three months is a realistic estimate just to get the data to the test stage. If someone promises to do the whole thing over a weekend, ask them what they’re leaving out.

Step 4: Plan the cutover like a DNS change

The cutover is straight infrastructure work, and it follows the same playbook as moving a website to a new host. We covered that logic in our guide to bulk website migration from cPanel: freeze changes on the old system, run one last delta sync, switch over, then check everything. Here’s what that means for an LMS:

  • Freeze content. During the final sync, nobody adds courses, enrollments or completions on the old platform. Otherwise you’re trying to move something that keeps moving.
  • Pick your week carefully. Not the week before a compliance deadline, not when a new group of hires starts, not in the middle of certification season. Look hard enough and the training calendar has a quiet patch.
  • Handle authentication on purpose. One broken SSO setting and the whole company is locked out at once. Try the SAML or OIDC connection with a handful of pilot users first.
  • Rebuild roles and permissions before go-live. Who’s an admin, who can teach, which manager sees which group: this rarely survives the move intact. Rebuild it by hand on the new side and ask the pilot users whether they can see too much or too little.
  • Run both systems side by side for a short while. Leave the old LMS open in read-only mode for a few weeks. If a record looks wrong on the new side, you can check the original.

Step 5: Keep a rollback you’ve actually tested

For an LMS, a rollback plan comes down to two things.

The first is keeping the old system reachable, at least in read-only mode, until the new one has made it through a full reporting cycle. The expensive mistake here is letting the old contract run out on cutover day. Then the one copy of your history you could actually trust is gone.

Second: your pre-migration export is a backup. A backup you’ve never restored is just a hope. We made the same point in our object storage backup guide. An export that finished without errors isn’t proof you can actually open it and read it.

There’s also a legal side. Training records belong to real employees, which makes them personal data, and moving personal data is processing in the legal sense. GDPR’s Article 32 asks for technical and organizational measures appropriate to the risk. For you, that means an encrypted transfer, as few people with export access as possible, and no leftover copies lying around afterward.

Step 6: Tell people what changes, and when

Users often never notice a server move. They will notice an LMS move, because the login page, the course catalog, and all their bookmarks change at once. Everyone is affected, the compliance officer and the intern who started on Monday alike. That’s why the technical plan needs a communication plan beside it:

  • Managers need the practical details early. Freeze date? Last day on the old platform? Restart date for assignments and deadlines? Send it a few weeks early so they can work around the gap.
  • Learners get a short note just before cutover. New login, where their old completions went, who to call if something’s weird. That’s enough.
  • Admins and instructors fall in between. Put their hands-on training in the parallel-run window, while they can still compare against the old system.

One trick from the hosting world works just as well here. Make one status page, or pin one announcement, and update it every time a milestone is hit. Week-one tickets drop, since most of them ask the same thing anyway: is this how it’s supposed to look?

How to Plan an LMS Cutover the Way You'd Plan a Server Migration illustration 2Source: Pexels

The pre-migration checklist

Here’s the whole runbook on one screen:

  • Data inventory done. Each category marked migrate, archive or drop, with a named owner.
  • Export formats agreed. SCORM versions confirmed, xAPI/LRS setup understood, certificate and test-question handling settled with the vendor.
  • Test migration completed. At least one full trial import, with the error log down to zero or to exceptions everyone has accepted.
  • Cutover window booked. Freeze announced, SSO tested with a pilot group, no calendar clashes.
  • Rollback in place. Old system in read-only mode, exports backed up and restore-tested, access to every copy locked down.
  • Communication sent. Managers know the freeze and access dates, learners know about the new login, admin training is set for the parallel-run window.

Common problems to expect

Some problems turn up in nearly every LMS move:

  • Certificates break. Their links rely on internal IDs from the old system. The standard import can’t fix that, so they need a script of their own.
  • Progress numbers drift. The two platforms count progress differently, so decide early which one’s logic you’ll go with.
  • Hidden dependencies appear late. That one HR integration? It’s run by a freelancer whose email address nobody can find.
  • A favorite report disappears. Some manager finds out the report they used every week doesn’t exist on the new platform.

None of this will sink the project. All of it is cheaper to find during testing than after go-live.

FAQs

  1. How long does an LMS migration actually take?

Just users and learning histories? Plan on roughly a week of technical work using standard scripts. Add custom content, certificates and a few integrations, and three months may only get the data as far as the test stage. Cutover comes on top.

  1. Do learning histories transfer one-to-one?

Hardly ever. Every vendor structures its data differently, so some fields get remapped and some get cleaned up. Aim for everything important arriving complete and checked, especially completions an auditor could ask about. A perfect copy isn’t realistic, and you don’t need one.

  1. Will our SCORM courses just work on the new platform?

Usually. Portability is the whole reason SCORM exists. But platforms have quirks, so open a few sample courses in a test instance and watch launch, progress and scores before you trust the rest.

Final takeaway

Good LMS migrations aren’t lucky. They come from a real inventory, several test runs and a rollback you’ve tried. Run it as a data project, keep the training team close, and you’ll land on the new platform with every record in place and no nervous auditors. Yes, this runbook is boring. That’s the point. A good cutover usually is.

Leave a Reply

Your email address will not be published. Required fields are marked *

Chat on WhatsApp