---
title: "How to migrate courses from other authoring tools into Coassemble Embed"
description: "When customers already have training built in tools like Articulate, 7taps, or Chameleon Creator, you’ll often need to help them move that content into your Coassemble Embed solution. This guide explains what typically migrates smoothly, what usually needs rebuilding, and how to set expectations so the project stays on track."
canonical_url: "https://support.coassemble.com/articles/how-to-migrate-courses-from-other-authoring-tools-into-coassemble-embed-RfBoNfqjvn"
md_url: "https://support.coassemble.com/articles/how-to-migrate-courses-from-other-authoring-tools-into-coassemble-embed-RfBoNfqjvn.md"
---
# How to migrate courses from other authoring tools into Coassemble Embed

When customers already have training built in tools like Articulate, 7taps, or Chameleon Creator, you’ll often need to help them move that content into your **Coassemble Embed solution**. This guide explains what typically migrates smoothly, what usually needs rebuilding, and how to set expectations so the project stays on track.

## What migrates well

The following elements generally transfer with minimal rework:

* **Plain text content**: Headings, paragraphs, bullet lists, and basic formatting translate directly.
* **Images and video**: Standard media files can be re-uploaded into the new course. YouTube/Vimeo links usually copy across cleanly.
* **Quiz questions**: Multiple choice, true/false, and short-answer questions map well to Coassemble equivalents.
* **Course structure**: Module/lesson organization can be recreated, even if the underlying screen types differ.

## What doesn’t migrate cleanly

These items typically require redesign or a rebuild rather than a direct “copy over”:

* **Complex Articulate Storyline interactions**: Branching scenarios, advanced triggers, and animated slide elements don’t have direct equivalents. They need to be reimagined using Coassemble’s screen-based authoring.
* **Proprietary card formats (e.g., 7taps)**: Fixed card layouts rarely map cleanly to Coassemble’s more flexible screen system; content must be redistributed across different screen types.
* **Heavy template-based design (e.g., Chameleon Creator)**: Template-specific layouts often need to be rebuilt rather than copied.

## A migration approach that works

For customers migrating a significant library, this workflow reduces rework and surprises:


1. **Audit first**
   * Ask the customer to list all existing courses.
   * Rank them by usage/importance.
   * Avoid migrating low-value or unused courses.
2. **Plan to redesign, not copy**
   * Set expectations that migration is a chance to improve the learning experience.
   * A direct “port” is rarely possible; **better-but-different** is the goal.
3. **Start small (proof of concept)**
   * Migrate one course end-to-end.
   * Use it to validate the process, define a visual style, and estimate effort.
4. **Use AI to accelerate rebuilds**
   * If the customer has original sources (PDFs, slide decks, training docs), use **Coassemble’s AI course generation** to rebuild faster than manual recreation.
5. **Phase the rollout**
   * Move high-priority courses first.
   * Retire low-value courses.
   * Use the project as an opportunity to clean up and standardize the library.

## Setting expectations with customers

Misaligned expectations are the most common cause of friction. Establish these principles early:

* **It’s not a one-to-one copy**
  * If a customer expects a Storyline course to look identical inside Coassemble, they’ll be disappointed.
  * Position the outcome as **improved and modernized**, not identical.
* **Some courses should be retired**
  * Migration is the right time to ask: *“Do we still need this?”*
  * It’s normal (and beneficial) to drop outdated or low-use content.
* **Plan for review cycles**
  * Every rebuilt course needs stakeholder review.
  * Include review time in the project plan to prevent timeline drift.

## When to escalate to Coassemble

Most migrations can be handled by your team using developer documentation and AI tools. Escalate when you encounter:

* A course that won’t import
* Unusual customer requirements
* A migration at a scale that needs platform-level guidance