How to import SCORM into SchoolMaker

To import SCORM into SchoolMaker, enable SCORM lessons in your school settings, create a lesson with the SCORM type and upload the ZIP exported by your authoring tool. You can also import several packages into a program at once. Before giving clients access, test the module as a member to check saved progress, scores and completion.

This guide walks through that process and the decisions that matter when you already have training materials to reuse. For the supported formats and the wider course experience, see SCORM support in SchoolMaker.

1. Prepare a SCORM package for your course

A SCORM package brings together your module’s content and the instructions it uses to communicate with a learning platform. Your authoring tool creates the module; SchoolMaker delivers it to your members. Editing the original activities or slides still happens in the authoring tool.

For example, you might have a product-training module built in Rise 360. Keep that project in Rise, export its LMS package, and upload that package to a lesson in your SchoolMaker program. You can then build the surrounding course without rebuilding the module’s screens.

SchoolMaker supports SCORM 1.2 and SCORM 2004 packages. Use an LMS export in one of those formats, rather than a web-only export, a PDF, or the authoring project file. Keep the generated ZIP intact. The package needs its manifest and launch content so SchoolMaker can identify and play it.

In Rise 360, the official export instructions explain how to choose LMS publishing, select a standard and set the tracking rule. Captivate users can follow Adobe’s packaging instructions. Those settings decide what the module reports as complete or passed.

Start with one representative package. Pick a module with a quiz if your course depends on passing scores, or one with several screens if resuming matters. A successful upload is only the first check; the important result is a member finishing the intended activity and SchoolMaker recording it correctly.

2. Enable SCORM lessons in SchoolMaker

As your school’s owner or an admin, open Settings, then General. In the Lessons section, enable SCORM lessons. SCORM is off by default, so schools that do not use these files do not have to work around an extra lesson type.

If the SCORM option is missing, check the school setting and your editing access before republishing your package. Do not assume that a missing upload control means the file is incompatible. The control is hidden while the feature is disabled.

Turning SCORM off later does not stop members from playing modules already attached to SCORM lessons. It does hide new SCORM lesson creation, batch import and SCORM package export. If you change an existing lesson to another type while SCORM is off, you cannot switch it back until SCORM is enabled again.

3. Import SCORM into a lesson or a program

Upload one package to a lesson

Open the program and create or edit the lesson where the module belongs. Choose the SCORM lesson type and upload your ZIP. SchoolMaker processes the package in the background, then makes the player and preview available when it is ready.

Choose the SCORM lesson type and upload the ZIP from your authoring tool. This real local screenshot uses fictional demonstration content.

Check the processing status before testing. If the import fails, read the error and confirm that you uploaded an LMS package in a supported format. The ZIP upload limit is 2 GB per package; the original archive and its extracted files count toward your school’s storage.

A module can sit alongside your other course lesson formats. You do not need to turn every part of the program into SCORM. Use the format for the authored activity, and keep other material in the lesson type that suits it.

Import several packages together

In the program, choose Import SCORM packages. Select up to 50 ZIPs, then choose an existing section or New section. Each package becomes a separate SCORM lesson. Once processed, the lesson takes the module’s title unless you have already renamed it.

Import several packages together, with one new lesson for each ZIP in the section you choose.

Batch import saves repetitive setup, but it does not decide your teaching order. Review the resulting section, lesson names and access rules before opening it to members. Importing course files also does not bring across completion history from another learning platform.

4. Test the module as a member

The editor preview lets you check that the module opens and its content displays. It does not save member progress. To check the learning experience, use a member with access to the program who has not already completed this lesson, then complete a short acceptance test.

1. Open it: confirm the expected first screen, navigation, audio and video work.
2. Leave halfway: answer a question or move through a few screens, leave the lesson, then return. Check that the module restores the position and answers it is designed to save.
3. Try an unsuccessful attempt: if a passing score is required, submit an answer set below that threshold and check that the lesson is not marked complete.
4. Finish successfully: meet the completion or passing rule and check that SchoolMaker validates the lesson’s completion step.
5. Repeat on a phone: try the same module on a device your clients use. Its layout and controls depend on how the package was authored.

This local demonstration attempt met the passing rule and automatically completed the SchoolMaker lesson step. Test your own package with a member account.

SchoolMaker saves runtime information such as position, answers, score and session time. Reaching the final screen is not enough on its own: the package must report the completion, progress or score information required by its tracking rule.

When the package defines a required passing score, that requirement matters. A member may reach the last screen and still need to pass the assessment. Once a completion step has been validated, a later failed attempt does not take that completion away.

5. Build the course around the SCORM module

SCORM is useful when you want to keep an existing interactive module. SchoolMaker is useful when that module belongs inside a broader offer: a structured program, discussions with other members, and help from you when someone gets stuck.

For example, an authored module might teach how to run a discovery call. Follow it with a practical assignment, use your course community for members to discuss what happened, and offer a coaching session to work through a difficult case.

You can combine the SCORM completion step with SchoolMaker’s existing progression rules. Check the whole path as a member: finishing the module should produce the progression you intended before the member moves on. Check access as well as the player, especially when the same school contains several offers.

6. Replace a package without losing track of members

To update a module, edit its source in your authoring tool, generate a new package and upload it to the SCORM lesson. SchoolMaker keeps the previous ready package available while processing the replacement. A failed upload does not replace a working module.

A successful replacement resets members’ saved positions for that package, while preserving their completed steps. That distinction matters during an active course. Someone who already completed the lesson keeps that completion; someone midway through the module may need to start it again.

Before replacing content, decide whether the update is urgent enough to interrupt people’s saved progress. Test the replacement first and tell active members what to expect if they will need to revisit the module. Keep the original authoring project as well as your published ZIP.

7. Download the original SCORM packages

When content export is enabled, the owner can open the program’s SCORM packages export page and download the uploaded packages individually. Choose Prepare the zip to build a single archive containing the program’s packages, then download it when processing finishes.

This retrieves the original packages. It does not convert native SchoolMaker videos, quizzes, community discussions or practical steps into a new SCORM course. It also does not export an authoring-tool project or transfer members’ saved attempts into another LMS.

Compatibility limits and common checks

SchoolMaker plays the first launchable learning object in a multi-SCO package. Full SCORM 2004 sequencing and navigation between several SCOs are not implemented. If your training relies on that structure, test a representative package before deciding this is the right fit.

If a ZIP is rejected, check the export format, manifest, size and storage first. If playback works but completion does not, check the package’s reporting rule and required score. If progress appears not to save, repeat the test as a member rather than in the editor preview.

For difficult cases, Rustici’s SCORM Cloud testing guide explains how to launch and inspect a package outside your LMS. Comparing the same file in another player can help you narrow down the problem; it is not a guarantee that every LMS will handle it identically.

Check the SchoolMaker SCORM feature page for the compatibility summary and current SchoolMaker plans when deciding how to host your course. For your first import, the useful finish line is one module tested from opening to completion with a member account.