Publishing Mighty-Enhanced Rise Courses to Reach 360
If Mighty customizations disappear when you publish directly to Reach 360, use this simple manual upload workflow instead.
If your Mighty-enhanced Rise course looks right in the editor but loses its Mighty functionality after publishing to Reach 360, don’t worry. The fix is simple: skip the direct Reach 360 publish path and upload the exported course package manually.
Reach 360 is a handy option when you need quick delivery without the overhead of a full LMS. But for courses that use Mighty, there’s one publishing detail worth knowing before you send the link to learners.
The issue: direct Reach 360 publishing can leave Mighty behind#
In Rise 360, the standard Reach 360 workflow is simple and straightforward:
- Open your Rise course.
- Select Publish.
- Choose Reach 360.
- Answer the same LMS-style questions you’d see when publishing for LMS.
- Submit the course.
Rise then sends the course straight into Reach 360, places it under the Courses tab, sets up the thumbnail, and gets it ready for delivery.
That native workflow is great for standard Rise courses. The catch is that when you publish a Mighty-enhanced course this way, the Mighty functionality may not come through in the Reach 360 version.
That’s a native publishing-path limitation, not something you caused by building the course incorrectly. The workaround is to export the course first, then import it into Reach 360 yourself.
The workaround: publish your course, then import it into Reach 360#
Instead of selecting Reach 360 directly from the Rise publish menu, use the LMS or web publishing route first. That gives you a downloadable package you can manually upload to Reach 360.
Here’s the full workflow.
1. Finish and review your Rise course
Before publishing, make sure the course is in the state you actually want learners to see.
This matters a little more with Mighty-enhanced courses because you may be relying on custom presentation details like:
- A modified Begin button
- Heavier or more customized text styling
- Mighty Transition blocks
- Autoplay video behavior
Give those moments a quick pass in Rise before you package the course. If you’re under a stakeholder deadline, this is the point where a 60-second review can save you from re-uploading later.
2. Choose the right publish option in Rise
From your Rise course, go to Publish.
Instead of choosing Reach 360, choose one of the export-based options:
- Select LMS if you need tracking and reporting options.
- Select Web if that better matches your delivery needs and you don’t need LMS-style reporting.
The key is that you want Rise to generate a downloadable package rather than sending the course directly into Reach 360.
If you choose LMS, Rise will ask the usual reporting questions. Answer those based on how you want completion or tracking handled. The exact settings depend on your course requirements, but the important part for this workflow is that you end up with the exported package.
3. Download the published ZIP file
Once Rise finishes publishing, you’ll receive a ZIP file.
Leave that ZIP intact. You do not need to unzip it or edit the files inside. Reach 360 can import the package as-is.
This is the small but important difference from the direct publish workflow: instead of Rise handing the course off to Reach 360 automatically, you’re keeping control of the exported course package and uploading it yourself.
4. Open Reach 360 and use Import course
Now head into Reach 360.
From your course area, look for the Import course option. Select it, then choose the ZIP file from your downloads.
Reach 360 will upload the package and process the content. Once the upload completes successfully, the course will appear in Reach 360.
One thing you may notice: the course is marked as Imported instead of appearing as a native Rise course.
That’s expected. It’s just a result of bringing the ZIP into Reach 360 manually rather than using the direct Rise-to-Reach publishing path. The important part is that the course can still be opened and delivered from Reach 360.
5. View the imported course and check your Mighty elements
After Reach 360 finishes processing, open the course and use View course to confirm everything is behaving as expected.
That final review is worth doing every time. You’re checking the exact things your learners and stakeholders will notice: the opening experience, branded styling, motion, and any custom behaviors you added with Mighty.
Why this matters for L&D teams using Reach 360#
Reach 360 is useful when you need lightweight course delivery. Maybe you have a smaller learner audience, a quick enablement rollout, or a project that doesn’t need the full machinery of a more robust LMS. You can publish, assign, and move on.
But if your Rise course uses Mighty to meet brand requirements or create a more intentional learner experience, you don’t want those enhancements disappearing at the last mile. A custom opening button, transition treatment, or autoplay media moment might seem small individually, but together they can be the difference between “standard Rise” and a course that feels intentionally designed.
The manual import workflow gives you a reliable way to keep that design work intact while still using Reach 360 as your delivery platform.
A few practical notes before you publish#
Direct publish is still fine for standard Rise courses
If your course doesn’t use Mighty functionality, the built-in Publish > Reach 360 flow may be exactly what you need. It’s fast, clean, and purpose-built for getting Rise courses into Reach 360.
This workaround is specifically for courses where you need Mighty enhancements to come through.
Imported courses may look different in Reach 360’s course list
Because the course is uploaded manually, Reach 360 marks it as Imported. That doesn’t mean the course failed or that learners can’t access it. It simply reflects how the course entered Reach 360.
If your team has internal naming or governance conventions, you may want to note this so admins understand why the item is labeled differently from a directly published Rise course.
Test the learner-facing course, not just the upload
A successful upload is good. A successful learner experience is better.
After importing, open the course and move through the moments where Mighty is doing work. If something is central to the experience, don’t assume it survived the trip—verify it.
The short version#
For Mighty-enhanced Rise courses headed to Reach 360, don’t publish directly to Reach 360 from Rise. Publish to LMS or Web first, download the ZIP, then use Import course in Reach 360.
Try this workflow the next time you need quick Reach 360 delivery without giving up the custom Rise touches you built with Mighty.