Export and Transfer Courses Between Platforms - Article
Summary
Course export supports reuse, translation, external delivery, and controlled distribution between platforms. The available routes serve different purposes: some transfer editable Course content, some create a standalone delivery package, and others continue to rely on content hosted in Eurekos.
Choose the route according to what the destination needs to do with the Course. An export does not constitute a complete backup of participant records, enrollments, permissions, reporting history, or every external dependency.
Use this article to:
- Choose an export or distribution route that matches the intended destination.
- Decide whether media and other dependencies should travel with the Course.
- Distinguish a complete package, lightweight SCORM launch, Marketplace download, translation file, and QR-code enrollment.
- Validate access, progress, completion, ownership, and maintenance after transfer.
Understand the transfer boundary
A Course contains authored learning content. Its delivery can also depend on Training Activities, participant enrollments, access rules, certificates, automation, Organizations, external services, and other platform records.
Course export concentrates on transferring or presenting the learning content. It does not automatically reproduce the complete operating environment in which that Course was originally delivered.
Before exporting, establish:
- Which Course, language, and version should be transferred.
- Whether the destination needs editable content or only a playable package.
- Whether the destination should receive its own media files or continue using media hosted elsewhere.
- Whether the destination must operate independently of the source platform.
- Who owns the transferred edition and future updates.
- Whether the organization has the right to redistribute included content, media, and third-party material.
Technical export availability does not itself grant permission to redistribute licensed content.
Choose the appropriate route
| Route | Appropriate purpose | What to understand |
|---|---|---|
| Native Eurekos export | Transfer supported native Course content to another Eurekos platform. | The destination receives a Course edition that can be imported and maintained there. Assets, ownership, references, and available features must still be reviewed. |
| SCORM or xAPI export of a native Course | Deliver Eurekos-authored learning through a compatible external LMS. | The result is intended for package-based delivery. Test media, navigation, progress, completion, and destination reporting. |
| Export of an imported SCORM or xAPI Course | Retrieve the package that was originally uploaded to Eurekos. | The available export follows the imported package type. It does not recreate the supplier’s editable authoring source. |
| Lightweight SCORM export, where configured | Let another LMS launch a Course that remains hosted and maintained in Eurekos. | The package is a launch route rather than a self-contained Course copy. Identity, access, source availability, and supported reporting remain dependencies. |
| QR-code smart link | Give people an activity-specific enrollment route from another LMS, customer portal, partner site, email, webpage, or physical QR code. | The link can use a configured identity provider and enrollment limit. It does not transfer the Course or automatically return progress and completion data to the originating system. |
| XLIFF | Exchange supported Course text with a translation provider or translation tool. | XLIFF transfers translatable text, not a complete playable Course or its complete media and layout. |
| Marketplace, where available | Distribute governed Course editions between connected Eurekos platforms. | Availability, approval, destination access, copyright, and onward use depend on the Marketplace governance model. |
Choose one primary route for each destination. Combining files or entry routes without a controlled process can create uncertainty about the Course version, media source, ownership, enrollment, and reporting behavior.
Prepare a controlled Course edition
Export an identifiable and reviewed Course edition rather than whichever version happens to be open.
Before starting the export:
- Confirm the Course title, language, owner, and intended destination.
- Review its current version and any unpublished changes.
- Check shared assets, embedded services, external links, prerequisites, adaptive rules, and specialized learning objects.
- Confirm whether included material may legally be transferred to the intended platform and audience.
- Decide whether future changes will be made in the source Course, the destination Course, or both.
- Record the reason for the export and the person responsible for validating the result.
If the source Course is actively used, follow the version and revision practices described in Update Courses Safely: Revisions, Versions, and Shared Assets.
Export a Course
Available export choices depend on the Course type, platform configuration, and enabled functionality.
- Open Courses.
- Identify the exact Course and language to export.
- Open the available Export action for that Course.
- Select the required native Eurekos, SCORM, or xAPI format.
- If the export offers a video choice, decide whether video files should be included.
- Start the export and allow processing to finish.
- Retain the resulting file together with its Course identity, language, version, export date, format, destination, and responsible owner.
- Import it into a controlled destination and complete validation before live delivery.
Some exports are processed asynchronously. Wait for the completion notification instead of repeatedly starting the same export.
Native Eurekos and Marketplace exports can be subject to a configured size limit. If the interface reports a maximum, treat that value as the limit for the specific platform and route. An import-processing threshold is not necessarily the same as the export limit.
Decide whether videos should be included
When supported native content is exported to SCORM or xAPI, the export can offer a choice to include or exclude video files.
| Choice | Result | When to use it |
|---|---|---|
| Include video files | The package contains the video files and therefore requires more processing time and storage. | Use when the destination must deliver the videos without depending on the original Eurekos platform. |
| Exclude video files | The package retains links to videos hosted on the source platform. | Use when smaller packages and centrally hosted videos are preferred, and the source platform will remain available to the destination audience. |
Excluding videos does not automatically make every other asset self-contained. Test downloads, images, H5P content, embedded services, and other dependencies separately.
When a package retains video links, keep the source videos available for as long as the exported Course depends on them. Confirm that the destination audience is permitted to access the source media.
Use a lightweight SCORM export as a hosted launch route
Where lightweight SCORM export is configured, the Course export can generate a small SCORM package that launches the Course hosted in Eurekos. The package can be installed in another SCORM-compatible LMS, while Eurekos remains the content host.
This approach is useful when:
- The external LMS must present or launch the Course.
- Course content should remain maintained centrally in Eurekos.
- Re-exporting a complete package after every content change would be undesirable.
- The intended audience can authenticate with and access the Eurekos platform.
A lightweight package is not an offline or independent Course copy. Its continued operation depends on the Eurekos Course, platform, identity configuration, and access model remaining available.
When the learner launches the package:
- A signed-in learner with the required access can enter the Course.
- A learner who is not signed in can be sent through the configured Eurekos authentication route.
- A signed-in learner without access can be directed to an available Activity Description or receive an access error, depending on the applicable configuration.
- SSO can simplify authentication and may support account creation where that has been configured separately.
The SCORM package does not itself configure SSO or create users. Those outcomes depend on the platform’s identity and user-creation configuration. See Users Managed Through SSO and Integrations.
Test the complete journey from the external LMS with representative learners. Confirm authentication, Course access, resumption, completion, and the evidence returned to the destination LMS.
Do not confuse lightweight SCORM with excluding videos from a complete package. A lightweight package launches the hosted Course, while a complete package without videos still transfers the supported Course structure and retains selected media links.
Use QR-code enrollment as a link-based distribution route
QR enrollment provides an activity-specific smart link through which people can authenticate and enroll in a particular Training Activity. Despite its name, the route does not have to be presented as a QR code. The same URL can be placed in a customer portal, partner site, intranet, third-party LMS, email, webpage, or other system capable of hosting a link.
This can be a useful alternative when the originating system needs to direct people into training but does not require a SCORM package or completion data returned automatically.
An authorized administrator can create multiple smart links for one Training Activity. Each link can represent a particular customer, audience, campaign, or commercial agreement and can have:
- A descriptive title.
- An enrollment limit or no limit.
- Active or inactive status.
- A selected SAML or OpenID Connect identity provider, where configured.
The enrollment limit controls how many participants can enroll through that particular link. Separate links can therefore support different customer allocations or agreements while directing participants to the same Training Activity.
When someone follows the link:
- A signed-in user continues through the activity-specific enrollment route.
- A signed-out user is directed through the applicable sign-in or registration process.
- If the link specifies an identity provider, the configured SAML or OpenID Connect route is used.
- The user account can be created during authentication where automatic account creation has been configured for that identity provider.
- Eurekos records the resulting enrollment, participation, progress, and completion through the Training Activity.
A third-party LMS or portal can record that a user selected the link if it provides its own click tracking. However, displaying a smart link does not send enrollment, progress, or completion information back to that system. A recorded click is also not evidence that the person authenticated, enrolled, or completed the training. Returning learning data requires a separate supported integration or interoperability route.
This distinguishes QR enrollment from lightweight SCORM:
- Use QR enrollment when another system should provide controlled entry to a specific Training Activity.
- Use lightweight SCORM when an external LMS requires a SCORM package that launches centrally hosted Eurekos content and supports the applicable SCORM exchange.
Distribute each smart link only to its intended audience. Test authentication, automatic account creation, enrollment limits, capacity, and the signed-in and signed-out journeys before release. Deactivate links when the associated campaign or customer agreement ends.
See Enroll and Register Participants for the complete enrollment and smart-link guidance.
Distribute Courses through Marketplace
Marketplace, where configured, is a shared and governed Course library connecting approved Eurekos platforms. It supports controlled reuse across affiliates, regions, brands, customers, or other connected environments. It is separate from the learner-facing Storefront.
The source platform submits a Course to Marketplace with the required metadata. The applicable governance process determines whether it is approved and which connected platforms can access it.
On an authorized recipient platform:
- Open Courses.
- Select the Marketplace tab.
- Use search, sorting, and filters to locate the required Course.
- Review the displayed version, language, update date, source affiliate, contact person, and copyright information where provided.
- Open the Course to review its description.
- Select Download.
- Validate the downloaded Course locally before making it available for delivery.
The downloaded edition should be reviewed for ownership, dependencies, metadata, media, learning rules, language, and intended audience.
Treat a Marketplace download as a governed Course edition. Do not assume that the destination Course remains automatically synchronized with later changes to its Marketplace source. Establish how updated editions will be reviewed, distributed, and applied.
Use XLIFF for translation rather than delivery
XLIFF transfers supported translatable text from a controlled Course edition. It is appropriate when a translator or translation service needs to work with Course text outside Eurekos.
It is not:
- A playable Course package.
- A complete transfer of layout and media.
- A substitute for SCORM, xAPI, or native Eurekos export.
- A complete backup of the Course.
After the translated XLIFF file is imported, review the Course in the target language. Text expansion, navigation labels, images containing text, videos, subtitles, H5P, and externally embedded content can require separate localization work.
See Translate and Localize Courses and Learning Assets for the complete translation workflow.
Review dependencies before transfer
| Dependency | Risk after transfer | What to do |
|---|---|---|
| SCORM embedded inside a native Course exported as SCORM | Nested SCORM is not supported, including when SCORM is included through the relevant H5P element. | Redesign the delivery or provide the components separately through supported routes. |
| Page prerequisite or adaptive rule referencing content outside the exported Course | The destination might not resolve the reference, and the intended restriction or adaptive behavior can be lost. | Include or rebuild the required relationship and test the actual participant path. |
| Shared or externally hosted media | The transferred Course can remain dependent on another platform, account, or service. | Confirm ownership, continued hosting, access, licensing, and a maintenance owner. |
| H5P libraries or specialized tools | The destination might not support the required content type, library version, or integration. | Test a representative Course before transferring a larger portfolio. |
| Author, co-author, and Organization context | The destination uses its own administrative ownership and scope. | Assign appropriate destination owners, collaborators, and organizational context. |
| Training Activities, enrollment, certificates, and automation | These delivery processes are not automatically reproduced by transferring the Course. | Rebuild the intended delivery configuration in the destination where required. |
| Learner statistics and completion records | Course transfer does not migrate the complete historical learning record. | Use an approved data-migration or evidence-retention process when historical records must move. |
Missing prerequisites can leave an imported page available when it was previously restricted. Treat this as an access and learning-design risk, not merely a broken reference.
Apply an appropriate transfer pattern
| Need | Recommended approach | Main verification |
|---|---|---|
| Move an editable Course to another Eurekos platform | Native Eurekos export and import. | Confirm assets, ownership, page behavior, language, and destination features. |
| Distribute an approved Course across connected Eurekos platforms | Marketplace submission, approval, download, and local validation. | Confirm the approved edition, permitted destination, copyright, and update process. |
| Deliver a standalone package through a partner LMS | Complete SCORM or xAPI export with an explicit media decision. | Test navigation, media, resumption, completion, and reporting in the partner LMS. |
| Let another LMS launch centrally maintained Eurekos content | Lightweight SCORM export, where configured. | Test identity, access, hosting, completion, and the evidence returned to the external LMS. |
| Send Course text to a translation provider | XLIFF from the controlled source edition. | Review the complete target-language Course after import. |
| Give a customer, partner portal, or third-party LMS audience controlled entry to a particular Training Activity without SCORM reporting | Create a customer- or audience-specific QR-code smart link with the appropriate enrollment limit and identity provider. Present its URL directly or as a QR code. | Test authentication, automatic account creation where configured, enrollment, capacity, link limits, and deactivation. Confirm that the originating system is not expected to receive completion data automatically. |
Verify the destination
Test with representative users and the same conditions expected in live delivery.
| Scenario or check | Expected result or evidence |
|---|---|
| A learner launches from the destination platform. | The launch and any required authentication are understandable and successful. |
| A user without the required account or Course access tries to launch. | The intended authentication, registration, enrollment, description, or access-denied journey appears. |
| The learner opens videos, files, and external resources. | Every required resource works under the intended destination access conditions. |
| A restricted or adaptive page is reached. | Its original learning requirement is preserved or has been intentionally rebuilt. |
| The learner exits and resumes. | Navigation, state, and progress behave as designed. |
| The learner completes or passes. | The required destination and source evidence is recorded correctly. |
| The Course is opened on representative devices. | Layout, interaction, media, and navigation remain usable. |
| Source hosting is expected to change or end. | No required resource still relies on that source, or a maintained hosting arrangement exists. |
| A newer source edition is released. | The owner can identify whether and how the destination should be updated. |
| A participant opens a customer-specific smart link from another LMS, portal, or website. | The intended identity provider is used, the correct account is created or recognized, and the participant is enrolled in the intended Training Activity without exceeding the link’s enrollment limit. |
| The originating system records that the smart link was selected. | The click is treated only as evidence of navigation. Enrollment, participation, and completion are verified in Eurekos unless a separate integration returns those outcomes. |
Keep the export file, source identity, destination, validation outcome, and maintenance owner together. This makes later support possible without guessing which Course edition or hosting arrangement is in use.
Troubleshooting
| Problem | What to check |
|---|---|
| The required export option is not available. | Confirm the Course type, your permissions, enabled export functionality, and platform configuration. An imported package and a native Course can offer different export choices. |
| The export is blocked by a size limit. | Review the limit reported for that platform and route, together with the listed large files or interactions. Reduce or redesign the package rather than assuming an unrelated import threshold applies. |
| The export is still processing. | Wait for the completion notification. Avoid starting repeated exports of the same Course while an asynchronous operation is still running. |
| A video is missing or unavailable after transfer. | Confirm whether the export included the video file or retained a link to the source platform. Check source hosting, audience access, and licensing. |
| A prerequisite or adaptive rule no longer works. | Check whether the rule referenced content outside the exported Course. Rebuild the relationship and retest the affected participant paths. |
| The lightweight SCORM package opens a Eurekos login page. | The package launches hosted Eurekos content. Confirm the intended authentication route, SSO configuration, user account, and Course access. |
| The learner signs in but cannot open the lightweight Course. | Confirm the user’s Course access and the configured destination for authenticated users without access. A lightweight package does not by itself grant enrollment or Course permission. |
| The expected enrollment limit or selected SSO handler is missing from the SCORM export. | These controls belong to activity-level QR-code smart links, not to the lightweight SCORM Course export. Create or review the appropriate customer- or audience-specific link from the relevant Training Activity. |
| The external LMS records that the smart link was clicked but does not show Course completion. | This is expected for an ordinary QR-enrollment smart link. The external system can track its own link interaction, while Eurekos records authentication, enrollment, progress, and completion. Use a separately supported integration or interoperability route if learning results must be returned. |
| A participant cannot enroll through a smart link. | Confirm that the link is active, its enrollment limit has not been reached, the Training Activity has capacity, and the participant can complete the configured authentication or registration route. |
| A participant is sent through the wrong authentication route. | Confirm which SAML or OpenID Connect handler is assigned to the smart link and whether the customer should use a different customer-specific link. |
| A smart link has been distributed beyond its intended audience. | Deactivate the link, review resulting enrollments, and create a replacement link if required. A link-specific enrollment limit controls capacity but does not prove that every user belongs to the intended audience. |
| A Course is not visible in Marketplace. | Confirm that Marketplace is enabled, the Course edition has completed the applicable submission and approval process, and the recipient platform is permitted to access it. |
| A Marketplace download does not contain a later source change. | Confirm which edition was approved and downloaded. Treat future source updates as separately governed editions unless the configured process explicitly states otherwise. |
| Completion or progress is not recorded as expected. | Verify the selected package standard, destination LMS settings, resume behavior, completion rules, and reporting mapping with a representative learner. |
| The destination needs historical enrollments or learner evidence. | Course export does not provide a complete participant-data migration. Use the separately approved migration and evidence-retention process. |
FAQ
-
Is exporting a Course the same as backing up the platform?
No. A Course export transfers supported learning content in the chosen format. It is not a full backup of users, signups, transactions, activity configuration, certificates, integrations, or every related asset and permission.
-
What changes when videos are excluded from a SCORM or xAPI export?
The exported content can retain links to videos hosted on the source platform instead of containing those files. This reduces package size but preserves a hosting dependency. Test access from the destination and confirm the source will remain available.
-
Can I export a native Course containing nested SCORM content as a portable SCORM package?
Do not rely on nested SCORM content for that transfer. The documented export guidance does not support nested SCORM. Review the Course structure and choose a supported delivery or transfer design before promising portability.
-
What should I verify after importing a transferred Course?
Check ownership and permissions, page structure, media and external links, assessment results, prerequisites, adaptive behavior, languages, and learner progress. Missing dependencies can change access behavior. Validate the destination Course before connecting it to a live delivery.
-
Is QR enrollment the same as lightweight SCORM?
No. QR enrollment provides a link to the enrollment process for a specific Training Activity. Lightweight SCORM provides an external LMS with a SCORM package that launches a Course hosted in Eurekos.
-
Can a QR-enrollment link be placed in another LMS or customer portal?
Yes. The smart link can be presented as an ordinary URL in any system capable of hosting a link, including a third-party LMS, customer portal, partner site, intranet, email, or webpage. Converting the URL into a scannable QR code is optional.
-
Does a QR-enrollment link return completion data to the originating system?
No. The originating system may record that its link was selected, but the link does not automatically return enrollment, progress, or completion data. Eurekos records those outcomes. Use SCORM, xAPI, or another supported integration when learning results must be returned to the originating system.
-
Can separate smart links be created for different customers or audiences?
Yes. Multiple links can direct people to the same Training Activity. Each link can have its own title, enrollment limit, active status, and configured SAML or OpenID Connect identity provider. This can support different customers, campaigns, populations, or commercial agreements.
-
Does the smart-link limit count clicks or enrollments?
It controls enrollment through that link, not the number of times the URL is opened. A click does not prove that the person authenticated or completed enrollment.
-
Can a smart link create a new user account?
The link does not create an account by itself. A new account can be created when the connected registration or SSO process permits automatic user creation. The participant can then continue into the intended enrollment process.
-
Does a Course downloaded from Marketplace remain synchronized with its source?
Treat the downloaded Course as a governed edition. When the source changes, the updated edition must follow the applicable Marketplace review and distribution process before the destination applies it.