Migration guide
Moving from SCORM Cloud to OpenSCORM
Most migrations finish in an afternoon. Here's the playbook.
The migration, step by step
Step 1: Inventory your SCORM packages
List the courses you serve from SCORM Cloud. Pull the original .zip files from your authoring tool or download from SCORM Cloud's dispatch downloads.
Step 2: Upload to OpenSCORM
Drag each zip into OpenSCORM. The course identifier is derived from the file name, so use a consistent naming convention if you care about clean URLs.
Step 3: Update launch links
Replace SCORM Cloud launch URLs with OpenSCORM URLs in your LMS (Moodle external tool, Canvas LTI, etc.) or wherever you embed them.
Step 4: Run side-by-side briefly
Verify completion records land correctly with a small test cohort before cutting over fully. We recommend a week of overlap.
Step 5: Cancel SCORM Cloud at renewal
Once cutover is clean, cancel before the next renewal date. Keep the SCORM Cloud account in read-only mode briefly if you need historical reporting access.
What stays. What changes.
Stays: your SCORM packages
Standard SCORM zips work as-is. Authoring tool output (Articulate, Captivate, dominKnow, iSpring, etc.) is portable by design.
Stays: your LMS integration model
However you launch SCORM today (Moodle SCORM activity, Canvas LTI, external URL launch), the same approach works against OpenSCORM.
Changes: launch URLs
You'll swap SCORM Cloud launch URLs for OpenSCORM URLs wherever you embed them. Find-and-replace in most cases.
Changes: your invoice
Flat monthly bill, no overage charges. Annual prepay saves 10%.
About historical completion records
Completion records from SCORM Cloud don't transfer automatically — they live in their database, not in the SCORM packages themselves. For audit continuity, export the completion data from SCORM Cloud as CSV before you cancel, and archive it alongside your OpenSCORM records going forward. We're working on an import path for common export formats — get in touch if you need this.
FAQ
How long does migration typically take?
For most customers with under 50 courses, an afternoon. The work scales with the number of launch points (LMS course shells) that reference the SCORM URLs, not the number of packages.
Will learners notice anything?
No, assuming clean cutover. The SCORM player UI is similar across platforms because the runtime is standardized. New launches go to OpenSCORM; in-progress courses can either finish in SCORM Cloud or restart, depending on how strict your tracking continuity needs are.
What about dispatches and SCORM Cloud-specific features?
OpenSCORM is a hosting and delivery platform. SCORM Cloud has features for distributing licenses to third-party LMSes (dispatches) that work differently here. If dispatches are core to your model, tell us about your use case before migrating.
Can I test before committing?
Yes. Free tier supports 1 course and 10 learners. Use it to validate the migration flow with a sample course. Or go straight to a paid month-to-month plan — no annual lock-in required to evaluate at real scale.
What if something goes wrong?
Don't cancel SCORM Cloud until your OpenSCORM cutover is verified. The two can coexist for as long as you need to run them in parallel. Roll back is just reverting the launch URLs.
Ready to start your migration?
Free tier first, or jump straight to a paid month-to-month plan.