What happens to my existing courses if I am using the new course builder experience?
What changes for courses you have already built now that the new course builder is available, and how to move one across when you are ready.
Nothing changes unless you choose to move a course. Every course you have already built stays exactly where it is and keeps working exactly as it does today. When you are ready, you can try a Classic course in the new builder and migrate it, one course at a time or several at once.
What stays the same?
For courses you have already built:
- They open in the Classic builder and you edit them the same way you always have. Their cards in the dashboard carry a Classic badge, so you can tell at a glance which is which.
- Learners see the same experience they see today. The rebuilt learner view applies to courses built in the new builder, so nothing changes for people partway through one of your existing courses.
- Sharing is unchanged. Existing links keep working, along with email invitations, Slack, embedding and SCORM export.
- Collections, folders and enrolments carry on as they are.
- Reporting and insights are unchanged, and your history is intact.
- Classic itself is unchanged. Every screen type, feature and setting works as it did before.
Can I move an existing course into the new builder?
Yes. Open a Classic course and select Try in new builder. The course opens in the new builder as a trial, so you can check how it came across before anything is final. Your learners keep seeing the published version while you try it.
- Happy with it? Select Migrate to new builder. This is final, and the course stays in the new builder from then on.
- Not ready? Select Back to classic and your course is exactly as you left it.
To move several courses at once, tick them on the Courses dashboard and select Migrate to new builder in the toolbar.
Which builder do I get when I create a new course?
The new builder appears as an option alongside Classic each time you create a course, so you can try it on your next course while continuing to build everything else the way you do now. Nothing is switched over for you.
What about courses created through an integration?
If you have Coassemble embedded in your own product, nothing changes for your users by default. An integration that creates a course without specifying which builder to use gets the Classic builder, exactly as it does today. The new builder is opt in, so your application has to ask for it explicitly before your users see it.
A few things are new on the integration side, and all of them are additions rather than changes to what you already run:
- Screen embeddables. You can now work with a single screen rather than a whole course. Screen Builder puts the new builder's screen editor inside your own application, and Screen Player renders one screen for a learner. A standalone quiz embeds as a set, with scoring, retakes and results.
- SCORM hosting. You can upload an existing SCORM package and host it in Coassemble alongside authored courses, with attempt tracking and question-level results.
- Moving Classic courses. Your users can try and migrate Classic courses in the embedded builder, and you can move courses in bulk through the API.
Your existing course-level embeddables keep working exactly as they do today.
Frequently asked questions
Will my learners notice anything?
Not unless you migrate a course. A course built in Classic looks and behaves for learners exactly as it did before, including for anyone partway through it, and trying a course in the new builder doesn't change what they see. Once you migrate and publish a course, learners get the new builder's learner view, and their records stay attached to the course.
Can I duplicate a course and convert the copy?
Duplicating gives you another Classic course. To bring a course into the new builder, use Try in new builder on the course itself. If you want to keep a Classic version as well, duplicate it first, then try the copy.
Will my usage allowances be affected?
Your allowances work the same way regardless of which builder you use. Anything that consumes narration characters or image generation events counts the same in both.