Is your organization ready for a new LMS?

What the LMS readiness checker covers

The checker follows an LMS project from context to launch: learners → content → SCORM → records → identity → integrations → launch. Every result comes from your answers, with no benchmarks or AI-generated conclusions.

• Learner & Organization DataHow well you know who the LMS will serve and where their data comes from.
• Course & Content LibraryHow prepared your courses and source files are. A large library is not a problem on its own.
• SCORM / xAPI ReadinessHow ready your SCORM and xAPI packages are to move. Answer No if you don't use them and this area is excluded.
• Historical Learning RecordsDecide what must migrate and what can stay archived. Answer No if no history moves and this area is excluded.
• Certificates & CredentialsHow well existing credentials can carry over. Answer No if none need to be retained and this area is excluded.
• Identity & SSOHow learners will sign in and who owns it. SSO questions are excluded when SSO is not needed.
• IntegrationsHow clear your integration needs are. Choose None and this area is excluded.
• Administration & OwnershipWho owns the project, the data and the decisions.
• Migration & Launch PreparationHow ready you are to test, launch and switch over.

Readiness bands

• 0–39 · Early Preparation: Many implementation requirements are not yet identified. This is common early in an LMS project.
• 40–59 · Planning in Progress: Core planning has started, but important data, content or ownership dependencies remain open.
• 60–79 · Mostly Prepared: Most implementation areas are prepared, with some dependencies still to confirm.
• 80–100 · Implementation Ready: Based on the information provided, most implementation dependencies appear to be identified and prepared. This does not guarantee compatibility or project success.

How do I know if my organization is ready for an LMS?

You are ready when you know who the LMS will serve and where their data comes from, which courses will launch and where their files are, which records and certificates must carry over, how learners will sign in, which systems must connect, and who owns each of those decisions.

What should be prepared before an LMS implementation?

Prepare a learner data source, a course inventory, original course and SCORM files, a decision on historical records, certificate data with issue and expiry dates, the SSO provider and owner, an integration list with owners, a named implementation owner and a launch testing plan.

What data is needed for an LMS migration?

Typically learner profiles with attributes such as department, role, location and manager; course and enrollment data; completions with dates and scores; certificates with issue and expiry dates; and any attendance or training hours you must retain.

What happens to SCORM content when changing LMS?

SCORM packages can usually move between systems, but older packages, unknown versions, missing source files and external dependencies can change how they track completion. Locate the original ZIP files, record each package's standard, and test a representative sample in the new LMS.

How do you prepare SCORM content for migration?

Inventory which courses depend on SCORM or xAPI, collect the original packages and authoring source files, note how each reports completion and pass / fail, check for hosted media or external links, and test older packages before the migration.

Should historical learning records be migrated?

Migrate the records you need for compliance, recertification or reporting, and archive the rest. Decide which completions, dates, scores, attempts and certification history must move, confirm they can be exported, and clean duplicate or inactive learners first.

How should we prepare SSO for a new LMS?

Decide whether SSO is required at launch, confirm the identity provider and protocol, assign an IT owner, confirm login domains and the unique user identifier, and decide how external learners will sign in.

What should we consider for LMS integrations?

List the systems to connect, what data moves and in which direction, whether API access and documentation are available, who owns each integration, and which integrations are launch-critical versus later-phase.

The LMS Readiness Checker is a self-assessment based on the information you provide. It does not test SCORM packages, data, SSO or integrations, and it does not guarantee compatibility, migration success or duration.