Bring your Storyline, Captivate and Rise courses with you.

What opens

• Articulate Storyline: project files (.story) and published packages (SCORM 1.2, SCORM 2004, xAPI, cmi5 or web folders).
• Adobe Captivate: Classic projects (.cptx), modern projects (.cpt) and published packages from 11.x and 12.x.
• Articulate Rise: published packages (SCORM 1.2, SCORM 2004, xAPI or web export, up to 4 GB with up to 2 GB of files inside). Each lesson becomes a scrolling page of blocks and a quiz lesson becomes graded questions with a results page. Branching scenarios, Storyline blocks and code blocks are kept as Rise data and listed in the report. A course in several languages opens in its default language. See importing a Rise course.
• PowerPoint: slides, formatted text, pictures, shapes, speaker notes and simple transitions.

You do not need the original tool installed. Everything is read on your computer and nothing is uploaded.

What comes across

Slides, text and shapes, images, audio and video, variables, states, layers, timelines, cue points, triggers, Storyline action groups, Captivate shared actions, and questions with their scoring. Anything that cannot come across is named, located and explained in the report.

Slides stay slides

Some tools “import” a course by pouring its text and pictures into a new page layout, then hand you a list of the interactions to rebuild. Xogogy keeps your course as you built it: the same slides, layers and states, with the triggers still wired and the variables still counting, playing in its own player. You fix what you came to fix, not the whole course.

What the report tells you

• Where every answer key came from. Each question is marked declared (read from the source), inferred (recovered from the scoring conditions) or unresolved. Unresolved questions are listed under “Please check”. A key is never guessed.
• Anything that did not map one to one, with where it is (the slide and object, when it has one) and a plain “What to do” line.
• Nothing thrown away. Properties the editor does not model travel with the course.

A real report

An excerpt of the report the command line wrote when importing a small published Storyline package we built for testing.

# Import report: story-published-mini.zip

Imported from storyline (publishedPackage)

## Needs your attention

Unmapped construct (interactions) - A trigger starts on a Storyline event that
Xogogy cannot use yet. It is kept but does nothing when the course plays.
  Where: slide "Knowledge Check"

## Please check

Nothing to report.

## Good to know

Approximate import (states) - An object's built-in states (such as hover and
down) were kept from the original course, but how they look is not shown yet.
  Where: slide "Welcome & Concepts" > object "btn_details"

## By slide

### Slide 1 - Welcome & Concepts: 1 finding
  What to do: No action needed unless the object must change its look when
  learners point at or click it.

### Slide 2 - Knowledge Check: 1 finding
  What to do: Recreate this trigger with a supported event in Triggers if the
  slide still needs it.

## Counts

Slides 2 - Sections 1 - Layers 1 - Objects 6 - Triggers 2 - Variables 3
Questions 1 - Quizzes 1 - Assets 4 - Omissions 2

A one-way door, stated plainly

Xogogy reads .story, .cptx and .cpt files but does not write them. You move forward into an open format, and your course stays yours.

Have a course that will not open? Send it our way and we will look.