This guide explains how to export a deployed content package for hosting on a non‑Skillcast LMS, provided you have the required permissions. If you need Skillcast to prepare the package for you, please contact your Customer Success Manager.
If you need instructions for remote content packages, please refer to the dedicated article. You can also read about the differences between deployed and remote content in the E-learning standards and features article.
Before you begin
Locate the module you want to export. Follow the steps in the Finding a module article.
Ensure you have permission to export deployed content packages.
Accessing the export screen
Open the module.
Select the Export a content package link on the right-hand side of the page.
Review the settings at the top of the export screen.
Use the History of exported content packages table to check previous exports, their settings, and who exported them.
General Settings
Setting | Description |
Package type | Choose the LMS‑compatible package type: SCORM 2004 4th Edition, 3rd Edition, 2nd Edition, SCORM 1.2, SCORM 1.2 for Moodle, xAPI or Untracked content package. |
Skin | Must match the skin used when the module was published. Verify on the Publish module screen. |
Module Version | Select the correct tracked module version. |
User Domain | Choose the staff domain used for tracking. Must match previous exports to avoid duplicate subscription usage. |
Export type | Download to your machine or upload to File Exchange. Choose the receiving domain if using FE. |
Author | Enter your name or Skillcast. |
Duration | Enter approximate module completion time. Calculate as: total words / 150. |
Version number | Start with 1.0. Increase for subsequent updates (e.g. 1.1, 1.2, 2.0). |
Show advanced settings | Enable to reveal advanced options. |
Advanced Settings
Setting | Description |
Always report best score | Records the highest score instead of the last score. |
Track assessment questions as SCORM interactions | Records question‑level data, varying by SCORM version. |
Add module debugging to package | Includes a debugging panel to support error capture. |
Do not add cache param for CSS/JS resources | Prevents caching issues by removing cache controls. |
Do not export media files | Excludes media files and loads them from Skillcast servers. Useful for testing, not final packages. |
Do not set Failed completion status (SCORM 2004) | Prevents LMS status from being set to failed. |
Escape special characters in suspend data | Avoids LMS errors caused by unsupported characters. |
Force window close after LMS Finish | Ensures module closes correctly when the user selects Close module. |
Hide LMS frames | Removes LMS framing for older platforms. |
Open module in a new window | Launches the module outside LMS frames and maintains SCORM API access. |
Set lesson status to completed (no assessment) | For modules without assessments. Sets status to completed instead of passed. |
Show warning if LMS commit fails | Displays a warning when LMS tracking does not save. |
Specify primary objective in manifest | Provides detailed SCORM content information. |
Specify roll‑up rules in manifest | Enables SCORM‑driven completion behaviour. |
Start new tracking attempt after completion | Required for Saba LMS to log completed records correctly. |
Store tracking data locally | Uses custom tracking logic instead of traditional SCORM tracking. |
Track interactions in English only (SCORM 2004) | Forces question text to English regardless of learner language. |
Track scores as SCORM objectives | Tracks assessment attempt scores using page title or number. |
Use frameset to force scrolling | Fixes content cut‑off issues by adding scrollable frames. |
Use GetLastError to check LMS performance | Captures detailed LMS error data. |
Use minimal metadata in manifest | Reduces manifest size for LMS systems with limited SCORM support. |
Use post message for utilisation tracking | Required for utilisation tracking across domains. |
Conclusion
After exporting your content package with the required settings, ensure your Customer Success Manager performs final checks before assigning it to employees. For further assistance, contact your Customer Success Manager by selecting Send us a message via the help icon on your portal, or by emailing [email protected].