Portability

Switching LMS Without Losing Your Courses: SCORM, Common Cartridge & Moodle

EduGears AI Team··9 min read
Course packages flowing between different learning platforms through open format gateways

Every conversation about switching learning platforms eventually hits the same wall: “but our courses are in there.” The content took years to build; nobody is retyping it. Whether a migration is a weekend project or a lost quarter comes down to file formats — which ones your old platform can produce, and what your new platform does with them.

Lock-in is a format problem

Platforms rarely lock you in with contracts; they lock you in with proprietary content models. The antidote is a small set of open interchange formats that most serious systems speak. Master what each one carries and migrations stop being scary:

The three formats that matter

FormatWhat it isWhat it preserves well
SCORM (1.2 / 2004)Zipped, self-running web content with a runtime APISelf-contained lessons and legacy courseware; completion and score tracking
Common Cartridge 1.3IMS standard for course structure interchangeCourse outline, pages, files, links, and assessments as structured content
Moodle backup (.mbz)Moodle's native full-course backupThe richest fidelity when either end of the move is Moodle

EduGears AI LMS speaks all three, in both directions: import SCORM packages, Moodle course backups, and Canvas Common Cartridges; export SCORM 1.2, SCORM 2004, Common Cartridge 1.3, and Moodle .mbz — plus question sets as QTI 2.1 or Moodle XML.

Imports should become editable

The lazy way to “support” imports is to play the package in an iframe and call it done. That preserves pixels, not courseware — you can't fix a typo, refresh a reading, or reuse a quiz question. EduGears AI rebuilds imported structure as native, editable activities: modules, lessons, and pages land as first-class content; PowerPoint becomes slides; Word becomes pages, study guides, or worksheets. (SCORM packages can also run as-is in the built-in player when that's what you want.)

Quizzes are handled deliberately differently, and it's worth knowing why before you migrate. Each quiz in the package arrives as authoring material — questions you can read, edit, and decide about — rather than as something a learner can walk into. You review them, keep the ones worth keeping with Save to Bank…, and then choose what that bank becomes: an ungraded practice set shared to learners, or a graded quiz you build from it. Nothing that arrives in an import publishes itself.

That's a deliberate trade. An import that auto-publishes gets you a demo faster; an import that waits for review means no learner ever meets a question you haven't read — including the ones the source course quietly retired years ago.

The harder half of a good import is fidelity to what learners actually saw, not to what the export file happens to contain. A real Moodle course usually carries superseded copies of activities that trainers keep for reference and hide from students — import those blindly and a course whose students see seven quizzes suddenly offers twelve. So hidden activities are left out; the loose notes Moodle prints between activities are merged into one readable page per section instead of shattering a lesson into scraps; and interactive content the backup doesn't actually carry is skipped rather than rendered to learners as a broken placeholder.

Every one of those decisions is named by title — on the import preview when you previewed, and in the completion email when the package was large enough to import in the background. A migration that reports “imported cleanly” while silently dropping a dozen items is worse than one that hands you a list — because the list is the only way you find out before a student does.

Packages up to 100 MB are previewed and committed in one sitting. Bigger ones — up to 2 GB — upload to a background pipeline and email you when the course is ready, which is what a media-heavy export from an older platform usually needs.

Grounding is a question, not a side effect: the import asks outright whether to ground the course in Curriculum Intelligence, with no answer pre-selected. Say yes and your material feeds that course's knowledge base, so the tutor, assistant and generators work from your real curriculum. Say no and nothing is embedded.

Question banks move too: QTI

Course-level formats carry the course. Question banks are their own kind of asset — often the most laboriously built thing an academy owns — and they deserve their own exit. That exit is QTI 2.1, the IMS standard for interchange of questions and assessments.

EduGears AI exports quizzes and question banks as QTI 2.1 XML, and Moodle and Canvas import that file straight into their own native question banks — as real, editable questions in the destination platform, not as a frozen package that merely plays. Moodle XML is available too when you want the shortest possible route into a Moodle question bank. Imports work in the same direction: existing QTI banks come in as first-class questions you can edit, group, and reuse.

It's worth checking a platform's question-bank story separately from its course story. Plenty of systems will export a course and quietly leave a decade of item-writing behind.

The fourth door: LTI 1.3

Formats move content; LTI moves functionality. EduGears AI LMS is an LTI 1.3 platform in its own right: it can host external tools with OAuth2 security, return grades through Assignment & Grade Services, and sync rosters through Names & Roles. Migration doesn't have to be all-or-nothing — the specialist tools your instructors rely on can come along.

Judge a platform by its exits

The fair test of any vendor's portability story is the export menu, because that's the door you'd leave through. Ours is deliberately wide open: whole courses out as SCORM, Common Cartridge, or Moodle .mbz at any time, question banks out as QTI 2.1 or Moodle XML, no penalty, no support ticket. We'd rather earn renewals with the product than with a locked door.

Will my quizzes survive the trip?

Their questions do — as authoring material rather than as something published behind your back. Each imported quiz arrives for you to review; keep its questions with Save to Bank…, then share that bank with learners as an ungraded practice set or build a graded quiz from it. Nothing an import brings in reaches a learner until you decide it should. On the way out, gradable quiz fidelity is format-dependent — Moodle .mbz carries them natively, SCORM reports scores, and Common Cartridge exports assessments per the standard — which is exactly why we support multiple exits.

We're on Moodle today. What's the path?

Export your course as a Moodle backup (.mbz), upload it to EduGears AI, and review the rebuilt course. Moodle-first organizations get the highest-fidelity route in both directions.

What about content built in Canvas?

Export it as a Canvas Common Cartridge and import — structure, pages, and assessments land as editable content.

See your academy on EduGears AI LMS

Book a demo and we'll show you a live tenant branded as your academy — your name, your colors, your domain.

Book a demo

Related posts