Migrating SCORM Content to Intellum: What to Expect

Key takeaways

• Intellum's LMS platform natively supports SCORM 1.2 and AICC; no conversion step is required to upload existing packages.
• Content files, catalogs, and completion summaries transfer during migration; however, question-level interaction details typically do not.
• The migration is shared: Intellum's services team runs the import and configuration; the client gathers the source data and SCORM packages and completes Intellum's intake forms.
• Migration sits within a standard implementation of roughly 14 weeks; the client's data preparation, beginning with a pre-migration audit of what to keep, drives the timeline more than Intellum's technical import.
• Existing SCORM activities keep running as uploaded after migration; new or updated content can be added by uploading a SCORM package or authoring natively in Evolve.

Migrating a SCORM library to a new platform raises key questions about content transfer and changes for the management team. This guide details what transfers, what requires rebuilding, the responsibilities for each step, and the expected timeline when migrating to Intellum. For broader migration guidance, see Your Guide to a Successful LMS Migration.

Does Intellum support SCORM content?

Yes. Intellum's LMS platform natively supports SCORM 1.2 and AICC content, so existing SCORM packages upload and run without additional plug-ins or conversion. Intellum's services team manages file import, data migration, and platform configuration during implementation, allowing teams to migrate existing programs without rebuilding.

In addition to the default formats, Intellum supports SCORM 2004, xAPI, and cmi5, though these are not enabled by default. An account admin must request enablement through their Intellum CSM before importing content in these formats. AICC, an older packaging standard, runs alongside SCORM 1.2 without additional setup.

What actually moves, and what needs to be rebuilt

During a SCORM migration, content files, catalogs, and completion summaries are transferred. Question-level interaction data, such as individual quiz answers and time-on-slide details, typically do not transfer because they are stored in a format specific to the source LMS. Content created in a source platform's native authoring tool, rather than packaged as SCORM, usually must be rebuilt from the original files.

What happens to learners partway through an activity

A SCORM migration does not ensure that learners will resume an activity at the precise point where they left off. The ability to retain bookmarks or resume data relies on how the original SCORM package records progress, particularly through fields such as suspend_data and lesson_location. These data points are defined and managed by the authoring tool and the specific content, rather than by Intellum itself. As a result, after migration, learners who had previously completed activities will have their completion status preserved in enrollment records and will not need to repeat completed content.

There’s no guarantee that learners will retain their precise bookmark when transitioned to the new platform. While importing in-progress enrollments is technically feasible, it is generally discouraged; the inability to ensure consistent resume data complicates administrative oversight and often spikes support requests during the cutover. If preserving in-progress status is a requirement, the Intellum services team can bulk-import client-supplied enrollment data to mark activities as "in progress"; though the specific lesson location still relies on the package's internal data management.

The most effective strategy is to establish a firm cutover date and notify learners well in advance. This proactive communication encourages users to complete in-progress activities prior to the migration, mitigating the impact of lost progress and minimizing the need for transitional support.

How long does a SCORM migration take

The transfer of SCORM content is integrated into the standard 14-week implementation lifecycle, with the overall duration primarily influenced by the speed of client-side readiness rather than the migration itself.

The migration workflow is structured into four distinct stages:

1. Source Package Retrieval: The client team identifies and gathers the SCORM files destined for the new platform.
2. Intake Documentation: The client completes the Intellum intake form, providing essential metadata and defining the mapping between specific SCORM packages and their corresponding activities.
3. File Transmission: The client uploads the gathered packages to the secure SFTP environment provided by Intellum.
4. Platform Configuration: Intellum executes the bulk jobs to create activity records in the LMS and establish the technical links to the uploaded files.

Technical execution in the final stage is efficient, typically requiring about four weeks for Intellum to finalize. Because the timeline is governed by the initial phases: content location, data form completion, and file uploads; expediting these preparatory steps is the most effective way to accelerate the transition.

What to audit before migration starts

A pre-migration audit determines which content in the existing library remains relevant, accurate, and necessary. Factors such as activity inventory, content age, and compliance or certification requirements guide decisions on what to migrate, update, or archive.

1. Inventory and format: Catalog each activity and record its packaging format (SCORM 1.2, AICC, SCORM 2004, or source-native), as this determines whether it can be uploaded directly or requires rework.
2. Compliance and certification: Identify activities linked to active compliance or certification requirements. These should be prioritized for migration to prevent lapses.
3. Outdated or duplicate content: Identify activities that are outdated, superseded, or duplicated, and determine whether they should be migrated.
4. As-is, refresh, or archive: For each activity, decide whether to migrate it unchanged, update it before migration, or archive it instead.publishing formats

The audit is also an opportunity to refresh outdated activities rather than migrate them as-is. For example, an organization may update compliance training with current regulations or improved interactivity before the move, either by revising the source content or rebuilding it in Evolve.For a structured approach, refer to the LMS Migration Checklist for the full pre-migration inventory process.

What changes for your team once content is live

Once SCORM content is live in Intellum, day-to-day operations change very little. Existing SCORM activities continue to run as uploaded, so content that already works does not need to be re-authored. Only new or updated content requires action after migration.

That new content can be produced two ways. A team can keep its current workflow — authoring in an existing tool, exporting to SCORM, and uploading the package; since Intellum's SCORM and AICC support is unchanged after migration. Alternatively, content authored in Evolve, Intellum's authoring tool, publishes to the platform through the Intellum integration as Evolve Native or Inline Evolve, without a SCORM export or re-upload step; Evolve can still export SCORM 1.2 packages when they are needed elsewhere.

One nuance applies to ongoing SCORM uploads: Intellum's LMS platform imports SCORM 1.2 by default and SCORM 2004 only on request, so teams working in SCORM 2004 should confirm enablement with their Intellum CSM.