Leaving Lectora? Bring the content, rebuild the actions.
Text, media and most questions come across from the publish or the .awt. Actions don't, and the report lists each one.
Last reviewed
No mainstream authoring tool imports Lectora courses, so leaving Lectora usually means a manual rebuild. Scormbusters is the exception: upload the published Lectora package or the zipped project folder with its .awt file, and it rebuilds each page as an editable lesson — text, images, video and most questions with their answer keys — then exports SCORM 1.2, SCORM 2004, cmi5 or xAPI.
In our test corpus that was every word and 63% of questions. Lectora actions and variables are rebuilt by hand; the import report lists them, and the questions it could not rebuild.
- No other mainstream authoring tool imports Lectora courses; moving tools usually means a manual rebuild.
- Scormbusters reads Lectora published HTML and Lectora .awt project files (the XML format of Lectora Inspire 12 onward).
- A .awt project keeps question answer keys in plain text; its images and video come across when the whole project folder is zipped.
- Measured on 9 real Lectora packages (Lectora Inspire 11.3 to Lectora 22): every word and picture came across, and 63% of quiz questions; the import report lists the questions it could not rebuild.
- Lectora actions and variables are not converted; the import report lists each one for rebuilding.
- Exports: SCORM 1.2, SCORM 2004, cmi5 and xAPI.
Your options
- Stay in Lectora and use its responsive features for new work. Right if you keep the license and the courses still meet your needs.
- Rebuild in another tool — Storyline, Rise, Captivate or others — by hand, or with a conversion vendor.
- Import into Scormbusters. The content comes across automatically; you rebuild only interactions. Works from the published output when the project is lost.
How Scormbusters reads Lectora
A Lectora publish is recognized by its runtime, whatever standard it was published to. Its pages are scripts that build every object when the page loads, so Scormbusters reads the objects those scripts describe — as data, without running them — rather than the near-empty HTML.
A .awt project from Lectora Inspire 12 onward is XML: chapters, sections and pages, each object’s text and position, and questions with their correct answers. Pages become lessons in reading order. The .awt holds no media itself, which is why the whole project folder should be zipped and uploaded.
What we measured
The importer is re-run on every release against 9 real Lectora packages from public repositories, published from Lectora Inspire 11.3, 16, 17 and 18, Lectora Publisher 18 and Lectora 22 as SCORM, xAPI and cmi5. Every word and picture came across; 63% of questions did; actions, buttons and form fields did not, and each one is counted in the report. The import scorecard has the per-tool figures.
Frequently asked questions
Can I import a Lectora course into Storyline or Rise?
No. Articulate's tools do not read Lectora titles or published output, so moving a Lectora course to them means rebuilding it. If the course began as PowerPoint, the deck is a starting point.
What Lectora files does Scormbusters read?
Published Lectora output — SCORM, AICC, xAPI or plain HTML — and Lectora .awt project files in the XML format Lectora Inspire 12 and later save. Zip the whole project folder so images and video come with the .awt.
Do Lectora questions and answers come across?
Most do, not all. Across the 9 real Lectora packages in our test corpus (Lectora Inspire 11.3 to Lectora 22), 63% of questions came across as multiple-choice, multi-select, fill-in-the-blank or sequence questions, read from the grading data a Lectora publish ships with its tests or from the .awt project. The rest, such as drag-and-drop questions and questions whose answer key the publish does not carry, are listed in the import report, so check the keys before you publish.
What about Lectora actions and variables?
They do not come across. Lectora builds much of a page with actions at runtime; Scormbusters imports the content those pages show and lists the actions for you to rebuild with native branching.
Will the result look like the Lectora page?
No: each page becomes a lesson of real text, images and questions in reading order, which reflows on a phone and works with a screen reader. A fixed-position Lectora layout is what usually stops a course meeting WCAG 2.1 AA.
Bring one stuck course. See what comes back.
Upload the published zip and play it rebuilt as an editable course, with the list of anything to rebuild by hand. No account, no card; the private link lasts seven days.