Import a published SCORM, AICC, cmi5 or xAPI package

It reads the package as data and rebuilds the course as ordinary lessons of editable blocks — text, headings, images, audio, video, tables and questions — not an embedded copy of the old HTML. Nothing in the package is run. Media files are copied into your library and every block is pointed at the new copy.

A .zip is identified by what is inside it, not by its name, because almost every tool publishes an ordinary SCORM package. The importer checks for each tool's signature in turn and uses the generic SCORM reader only when nothing more specific matches — otherwise a Rise or Storyline course would import as the player's scaffolding instead of the author's content.

• SCORM 1.2 and SCORM 2004 (any edition). The manifest's organization becomes modules and lessons; each lesson's launch page is followed through framesets and redirects to the page that shows the content, and that page becomes blocks. Questions written in the page's HTML — or scored by its own script — become gradable questions where the right answer can be read. A mastery score becomes the passing score.
• AICC (course structure files), cmi5 (cmi5.xml) and xAPI / Tin Can (tincan.xml): read the same way from their own course structure.
• A package published to several standards at once is read as SCORM, whose manifest carries the most structure.

SCORM 2004 sequencing and navigation rules, prerequisites between lessons and time limits are not recreated: the imported lessons are open, and the report lists the rules that were there.

These are recognized by their content and read with a dedicated reader:

• Adobe Captivate — see Import a Captivate course.
• Articulate Storyline — see Import a published Storyline course.
• Articulate Rise 360 — web and SCORM exports, including the 2025 format that loads the course from locales/. Blocks map to their nearest equivalent; knowledge checks keep their answers.
• Lectora — published HTML (SCORM, AICC, xAPI or plain), and .awt project files or a zipped project folder. Chapter and page structure is kept; tests keep their questions.
• iSpring Suite and iSpring QuizMaker — the content inside the player's data files, including quiz questions.
• Articulate Studio (Presenter, Quizmaker, Engage). Presenter '09 packages give up each slide's title, text and notes. Everything Studio compiled into Flash — Quizmaker questions, Engage interactions, Presenter slide visuals and narration — is counted in the report, not converted. See Articulate Studio end of support.
• Adapt and Evolve — the course JSON, in built or source layout.
• H5P — .h5p files and exported H5P folders, including Course Presentation and Interactive Book.
• IMS Common Cartridge (.imscc, e.g. a Canvas course export) and QTI 1.2 / 2.x question packages.
• Moodle course backups (.mbz, Moodle 1.9 to 4.x). A backup can contain learners' accounts, grades and submissions. User data is never imported — the report only counts what was there.

People zip a published folder in many ways, and the importer accepts all the common ones:

• A wrapping folder ("Compress" in Finder or Explorer puts everything inside MyCourse/) is removed, however many levels deep, so the package root is where the tool put it.
• `__MACOSX/`, .DS_Store, Thumbs.db and desktop.ini are ignored.
• Backslash paths written by some Windows tools are fixed.
• A zip inside a zip — for example an LMS download that wraps the package — is opened one level down.
• A .mbz that is really a .tar.gz (every Moodle backup since 2.6) is read as one.

The same rules apply to all of them: the upload must be 100 MB or smaller, and its contents at most 5,000 files and 500 MB uncompressed, with no single file compressed more than 100 to 1. Each person can run 10 imports in 24 hours.

• "File too large (max 100MB)". Remove video from the package and add it after import, or split the course and import the parts.
• "ZIP archive rejected: …". The archive is over one of the limits above. If it holds more than one course, import them one at a time.
• "Nothing in … could be converted into editable content, so no course was created." The package was recognized but held nothing the importer can rebuild — typically a course whose content is entirely Flash, or a manifest whose pages are missing. The message says what was found.
• "Failed to parse file". The file is damaged, is not what its extension says, or is a format the importer does not know. Re-download it from the LMS or authoring tool; try the original publish rather than a re-zipped copy.
• "Import limit reached. Try again tomorrow." The 10-per-day limit.
• The course imported but looks thin. Open the report: content that lives in Flash, in embedded pages, or on a web address outside the package is listed there. Check the package really contains the content — some LMS exports hold only a launch link.

Before paying for anything, you can run the free accessibility scan on the package: it uses the same readers and shows what the importer would see.