Coming from SCORM
Migrate SCORM courseware: 1.2 and 2004, imported and playable
SCORM is what authoring tools and older systems produce when a course leaves them — zipped, self-running web content with a runtime API. Both versions import here, and a package can run as-is in a built-in player when that is what you want.
Where a SCORM package comes from
There is no single export menu here, because SCORM is not one platform. It is what your authoring tool publishes, and what an older system hands back when you ask for the courseware.
- 1
Publish or export the course from your authoring tool as SCORM — 1.2 and SCORM 2004 are both read.
- 2
You end up with a single .zip per course: the same file you would have uploaded to your old LMS.
- 3
Upload that .zip here from Courses → Import course → Import a course package.
One file per course, up to 2 GB. Legacy courseware is often mostly video, and a media-heavy package does not have to be trimmed before it will upload.
What a SCORM package carries across
SCORM's strength is self-contained lessons and legacy courseware, with completion and score tracking built into the runtime. A package can play as-is in the built-in player, or its structure can land as editable content.
Comes across
- Self-contained lessons and legacy courseware, playable as-is in the built-in player
- Completion and score tracking, which is what the SCORM runtime was built to report
- Course structure — one section per unit in the package, with a Learning Materials activity for each
- Images and links inside the pages that come across
Named and skipped
SCORM preserves pixels well and courseware structure less well, so not everything a package contains can be turned into editable content.
- Interactive content that needs its original engine, rather than being rendered to learners as a broken placeholder
- Question types that cannot be marked without the platform they were written for
- Anything else that cannot be resolved — listed by title rather than dropped in silence
You get the full list on the preview when you previewed, and in the completion email when the import ran in the background. And if a package is best left exactly as it is, that is a legitimate answer too: it runs in the built-in player instead of being rebuilt.
Two paths, by package size
Up to 100 MB the import is previewed and committed while you watch: you see the module → lesson → activity tree that would be created, item by item, and nothing is written to your courses until you commit. A package as large as 2 GB goes to the background pipeline instead — the upload runs with a progress bar, there is no on-screen preview because the reading happens after you have closed the tab, and you are emailed when the course is ready.
Grounded in your curriculum — only if you say so
Reading the package and building the course out of it use no AI at all. Grounding is asked outright, as a question in the import itself — ground this course in Curriculum Intelligence? — with no answer pre-selected. Say yes and the imported material becomes that course's knowledge base, so the tutor answers from your content and the generators write in your curriculum's language from day one. Say no and nothing is embedded; the course still imports, and you can ground it later.
An imported quiz is authoring material
Each quiz in the package arrives as questions you can read, edit and decide about — not as something a learner can walk into. Review them, keep the ones worth keeping with Save to Bank…, then choose what that bank becomes: an ungraded practice set shared to learners, or a graded quiz built from it. Nothing an import brings in reaches a learner until someone has looked at it.
What is already here when the course lands
The import is the boring half. This is the half that decides whether the move was worth making — platform features rather than a shopping list of add-ons to licence separately.
26 AI tools, built in
Course generation from a syllabus, quizzes, rubric-based grading, slides, study guides and worksheets — all grounded in your own materials.
Cog, on every page
An Ask Cog bubble that already knows the course, lesson or quiz in front of you: the tutor for learners, the assistant for instructors. It does not surface quiz or answer-key material before or during an attempt, so it is safe to leave on during assessment — and it is switched on for every tenant.
Live video sessions
Scheduled from a course, a classroom or the calendar, and joined in the browser — with no separate account and no third-party video subscription.
Certificates that verify themselves
QR codes, a public verification page in your branding, Open Badges 3.0 credentials, validity windows and recertification.
Your brand, your domain
White-label branding resolved before anyone signs in — down to the notification emails and the certificate page — with role-based dashboards and one learner's whole record on a single page.
An LTI 1.3 platform of its own
The specialist tools you already licence launch here too, with OAuth2 security, grade passback through Assignment & Grade Services and roster sync through Names & Roles.
And the way back out
Judge a platform by its exits. Whole courses export as SCORM 1.2, SCORM 2004, Common Cartridge 1.3 or Moodle .mbz; question sets export as QTI 2.1 or Moodle XML. No penalty and no support ticket — the door you came in through stays unlocked.
SCORM import questions
- Which SCORM versions are read?
- SCORM 1.2 and SCORM 2004. Both import, and both play in the built-in player — useful when the content predates whatever system you are running today and nobody still has the source project.
- Does a SCORM package stay a black box?
- Only if you want it to. A package can run as-is in the built-in player, which is the right answer for legacy courseware nobody is going to edit. Where the package's structure can be read, it lands as native, editable content instead — modules, lessons and pages you can rewrite, extend or regenerate with the built-in AI tools.
- How big can a SCORM package be?
- Up to 2 GB. Up to 100 MB the import is previewed and committed while you watch; above that it goes to a background pipeline, the upload runs with a progress bar, and you are emailed when the course is ready. Legacy SCORM courseware is usually mostly video, so the second path is the common one.
- Can we export SCORM again afterwards?
- Yes — whole courses export as SCORM 1.2 or SCORM 2004, as well as Common Cartridge 1.3 and Moodle .mbz. Question sets export as QTI 2.1 or Moodle XML, at any time, with no penalty and no support ticket.
Coming from somewhere else?
Read further before you export anything
Try it with a real course
Export one course from where it lives today and import it. The skip list will tell you more about a migration than any sales call can — ask us to set you up on the free evaluation tenant. No card, no commitment.