Nucleus OS Docs
    Create

    SCORM export

    Export any Nucleus OS course as a SCORM 1.2 or SCORM 2004 package for another LMS, and what to expect from tracking.

    Many teams run Nucleus OS alongside an existing LMS, especially during a migration or when a client requires their own platform. Any course can be exported as a standard SCORM package.

    Supported standards

    StandardUse when
    SCORM 1.2The target LMS is older or you are unsure. It is the most widely supported version.
    SCORM 2004 (4th edition)The target LMS supports it and you need richer sequencing or separate completion and success status.
    xAPIYou want detailed activity statements sent to a Learning Record Store. See SCORM, xAPI, and LTI.

    Export a course

    Publish the version you want to export

    Export uses the latest published version, so finish review gates first.

    Choose the format

    Pick SCORM 1.2 or SCORM 2004, the completion criterion (all lessons viewed, or assessment passed), and the passing score reported to the LMS.

    Download and upload

    Download the .zip package and upload it to your LMS as a new SCORM course.

    Test in the LMS

    Launch the course as a test user and check that progress, score, and completion are reported as expected.

    What travels in the package

    • Lessons, interactive cards, and media
    • Quizzes and assessments, with scoring reported to the LMS
    • Your branding and visual style

    AI features in exported packages

    Some capabilities depend on the live platform: the AI tutor, adaptive paths, voice role-play, and concept-level mastery analytics. For those, launch the course from Nucleus OS through LTI 1.3 instead of exporting a static package.

    Updating exported courses

    SCORM packages are snapshots. When the course changes in Nucleus OS, export a new package and replace it in the LMS. Most LMSs let you replace the package while keeping existing learner records.

    Importing SCORM

    You can also bring existing SCORM 1.2 and 2004 packages into Nucleus OS so legacy content sits in the same paths, enrollment rules, and reports as new content.

    On this page