Browse Articles
Select a Product
null Support Directory
Browse all null articles. (Last Updated )
No articles found.
Search Results
No articles found.
Rise 360: Using the LMS Package Legacy Exporter
Article Last Updated Jul 1, 2026
This article applies to:
To improve reliability and pave the way for future improvements, we’ve modernized the backend architecture for all LMS exports in Rise 360.
Our latest Rise package export distributor is now selected by default when you publish to LMS. We've also added a temporary Legacy export setting, available only until August 7, 2026. Keep reading to find out what's changed and why you might need the temporary setting.
The latest update doesn't change how LMS Export packages perform for learners, but it does change the package's internal architecture. That may affect how your LMS handles the data. While we don't anticipate the update causing issues for most users, those who modify their exported package files and/or deploy to custom LMS systems may encounter compatibility issues.
The Legacy export setting allows you to maintain training continuity for your learners while you troubleshoot and diagnose compatibility issues with content exported to your LMS using the latest export package. The setting disables the default Rise package generator for the current export only.
Temporarily Switch to the Legacy Exporter
If you encounter issues with the default exporter, you can temporarily switch to the legacy export setting to keep your training up and running while you diagnose the issue.
- In your training, open the Publish menu and select LMS.
- Within LMS Export, select Legacy export from the dropdown menu.
- Continue with the LMS publishing procedure as usual.
Note: This is a one-time setting and must be selected each time you export your training to LMS.
This export option will be removed from Rise 360 on August 7, 2026. Training published with legacy export packages will remain active after the option is removed. To diagnose and fix compatibility issues permanently, start with our standard LMS troubleshooting steps. See the FAQs for more information.
FAQs
Should I enable the Legacy Exporter if I'm not seeing issues?
No. If your exported packages are working as expected, you don't need to use this setting.
I want to overwrite a package generated by one export package model with the other. Will my learners notice anything different?
Learners who have already completed your training won't see any difference, and their completion data will be retained. However, any learners whose training is in progress will have that progress reset if you overwrite the package in your LMS. When switching between models, you must enable Reset progress after updates. This setting is enabled automatically when exporting a package with Legacy export.
I use a custom LMS configuration. Should I use this?
Possibly. We recommend that you try the default exporter first. While the recent update changed the internal file structure of Rise LMS export packages, we still anticipate that it will provide the most consistent results for most users.
When using the default export package, note that backend architecture files have been moved, renamed, or removed. If your LMS or integration references specific file paths and you run into issues, reach out to us for further assistance.
Can I still use standard LMS troubleshooting steps?
Yes. Whether you're using the default or Legacy exporter, standard LMS troubleshooting steps still apply.
Share Feedback or Contact Support
If you do need to enable the Legacy export setting, please let us know by starting a case. We want to continue to improve reliability for the default Rise LMS exporter. When you reach out, please include the following:
- Are you using a custom LMS? If not, which LMS are you using?
- What didn't work as expected—was the issue administrative, learner-facing, or both?
- Did enabling the Legacy export setting resolve your issue?
If the Legacy Exporter didn't resolve your issue, or you need additional help, follow the steps to enable LMS Debug mode and create debug logs. Include those logs with your case, and we'll take a closer look.