Migrating Articulate Rise courses

A switch to a new authoring tool often fails not because of the new software, but because of the existing content. What happens to the Articulate Rise courses that you’ve already spent so much time, budget, and subject-matter coordination on? Do you really have to recreate all the text, media, interactions, and quiz questions in the new system?

No. Existing Articulate Rise courses can be imported into Knowledgeworker Create as exported SCORM packages and made available there as editable courses. This preserves the content work you’ve already done, and makes the transition to a new authoring environment much easier.

Articulate Rise courses can be migrated into the Knowledgeworker Create authoring tool using exported SCORM packages. The learning content inside these packages is migrated on a technical level and made available as editable courses in the new authoring environment. This means that you don’t have to manually recreate existing eLearning courses when switching authoring tools.

To perform the migration, all you need is the SCORM packages exported from Articulate Rise. Direct access to your Articulate environment is not required for the migration process described here.

Companies looking for an alternative to Articulate Rise can therefore factor their existing course library into their decision right from the start. The question is no longer just: Which authoring tool will be a better fit going forward? What’s just as important is: How can existing Articulate content be imported and made ready to use immediately?

A manual rebuild ties up resources. Text has to be copied, images and videos have to be re-embedded, page structures have to be recreated, and interactive elements have to be rebuilt. With a larger course library, this effort quickly snowballs.

Migration allows you to transfer existing eLearning courses instead of creating new ones. This doesn’t just save time. It also helps you avoid unnecessary manual work on content that’s already been reviewed, translated, or approved.

This is particularly valuable for courses that are updated regularly. After migration, the content isn’t stored as a static legacy collection, but can be maintained and further developed inside Knowledgeworker Create.

This is also relevant for regulated companies. Content that has already been reviewed doesn’t have to be re-entered. This reduces the need for additional coordination cycles and facilitates a controlled transition to a new authoring environment.

Companies that want to switch authoring tools and import their existing courses shouldn’t view the existing content as an obstacle. Their existing course library can become part of the migration project.

It’s not just plain text that can be transferred during the migration. You can also take standard content, media, interaction, and knowledge elements from Articulate Rise and convert them into corresponding elements in Knowledgeworker Create.

After the migration, the imported content will be available in Knowledgeworker Create as editable courses. Certain specific Rise elements may require individual adaptation or post-processing work. These cases are identified during the migration process and can then be reviewed on a case-by-case basis.

The Articulate Rise migration process is straightforward for your team: You provide the exported courses, and we handle the technical import behind the scenes. The migrated content is then immediately made available in Knowledgeworker Create for further editing.

Yes. The SCORM packages exported from Articulate Rise form the technical foundation of the migration. The content is transferred to Knowledgeworker Create where it’s then made available as editable course content. This allows existing Rise courses to be maintained and further developed directly in Knowledgeworker Create going forward.

Migration is particularly interesting when dealing with large or business-critical course catalogs. The larger the existing library, the greater the impact a structured migration process has on the effort required and future maintenance.

Typical starting points include:

• A larger existing Articulate Rise course library
• Numerous language versions or international course offerings
• Learning materials that need to be updated regularly
• Courses that have been approved from a technical or regulatory standpoint
• Recurring review and approval processes
• Multiple authors or international content teams
• A strategic shift in authoring platform
• New requirements for hosting or data sovereignty

In these cases, migration can ensure that switching tools is both economically viable and organizationally straightforward.

A project in the pharmaceutical and life sciences industry demonstrates how an Articulate Rise migration works in practice.

An international pharmaceutical company had more than 70 existing Articulate Rise eLearning courses in its catalog. Much of the content had already been approved from a technical and regulatory standpoint. However, new requirements were emerging regarding infrastructure, data protection, and data sovereignty.

Instead of manually rebuilding the entire course library from scratch, the company provided chemmedia with exported SCORM packages. Texts and course structures were transferred over, as were accordions, tabs, flashcards, images, videos, graphics, and questions and quiz content—including the associated logic.

After the migration, the eLearning courses were made available as editable courses in Knowledgeworker Create. Over 70 courses were migrated within a few weeks. Texts that had already been approved didn’t need to be recreated manually.

The technical migration is an important part of the transition. Equally important is the question of how your content production process will be organized going forward.

So don’t just test the standard features of the new authoring tool. For professional eLearning teams, future production processes are also crucial:

• How do multiple authors collaborate on courses?
• How do reviews and technical approvals work?
• How can language versions be created and maintained?
• How can recurring content be managed centrally?
• How can changes be made traceable?
• What roles and permissions do authors, reviewers, and specialist departments need?
• How can large course portfolios be updated efficiently over the long term?

You should also use the transition as an opportunity to take stock. Which courses will still be required? What content can be archived? Where are there duplicates or outdated versions?

This provides a clean starting point for further work in Knowledgeworker Create. There, your teams can update existing courses, create new learning content, and continue to develop their content production over the long term.

When choosing an Articulate Rise alternative, it’s worth considering both your future production processes and the authoring tool’s features.

To migrate your Articulate Rise courses, you need to provide them to us as exported SCORM packages. Simply submit the files using the designated upload interface. We’ll handle the technical migration process.

If necessary, you can remove outdated courses or duplicates before the handover. No extensive technical preparation or structuring of your course library is required.

The migrated content will then be made available in Knowledgeworker Create for further editing.