Launch with Existing Courses and Learning Assets - Article
Summary
Existing learning material can shorten the path to a useful launch, but moving files is only part of a migration. You also need to decide what remains valuable, how it will be maintained and how people will enter and complete the new training offers.
Use a representative migration to establish the working pattern before moving the full portfolio. Keep course packages, source assets, audience records and historical learning evidence as separate workstreams, with clear owners and acceptance checks.
Use this article to:
- Inventory existing learning and choose what to import, reuse, rebuild or retire
- Distinguish editable native Courses from externally authored packages and reference assets
- Plan account and training-history migration without confusing them with content import
- Prove the delivery and evidence journey with representative material
- Scale a verified migration pattern in controlled batches
Preserve the useful learning, not every old file
Begin with the business need the material still serves. An existing package may be technically importable but no longer accurate. A presentation may be current but rely on a facilitator’s explanation. A manual may be valuable reference material without being a suitable standalone course. Treat these as different starting points.
Create a content inventory that identifies the audience, outcome, current owner, language, format, rights, source files, review date, current usage and intended destination. Mark required launch items separately from material that can follow. Ask the content owner to confirm accuracy before your team spends time migrating obsolete content.
| Disposition | Use it when | Practical next step |
|---|---|---|
| Import and retain | The course is current, legally usable and behaves appropriately in its existing format | Test a representative package and its tracking, then prepare the Eurekos delivery offer |
| Reuse selected assets | Videos, images, documents or interactions remain useful but the old course structure does not | Organize the approved assets and build a focused new Course around the intended task |
| Rebuild for a better experience | The material is valuable but difficult to navigate, maintain, translate or use on relevant devices | Recover editable sources where available and redesign a representative lesson before estimating the full effort |
| Retain as reference | Detailed manuals, SOPs or product documentation support work beyond the training itself | Choose an appropriate file or Resource Library route with clear access and maintenance ownership |
| Retire or defer | The item is obsolete, duplicated, unowned or irrelevant to the first launch | Record the decision and preserve any required historical evidence through its separate retention process |
A migration is a useful opportunity to improve descriptions, titles and audience relevance. It does not require recreating everything. Keep well-designed learning that already works, and focus redesign effort on material whose current form creates a real learner or maintenance problem.
Choose the right destination for each format
The format affects what can be edited and how learning evidence is produced. An import does not automatically transform one authoring model into another.
| Material | Suitable route | Boundary to preserve |
|---|---|---|
| Eurekos native Course package | Import the .eur package through Courses and review the resulting native structure and assets | Verify dependencies, ownership, settings and the delivery offer; importing the Course does not enroll the audience |
| SCORM or supported xAPI package | Use the appropriate package import through Courses and test its launch and tracking | The package remains externally authored content; its internal design is maintained in its source authoring tool |
| Video files | Upload approved recordings to the native video service, then configure relevant language and navigation support | A native video and a third-party embedded video have different tracking and maintenance relationships |
| Documents, images and presentations | Reuse approved assets in a native Course or provide them as reference material | A presentation is not automatically a complete self-paced learning experience |
| H5P content or reusable questions | Use the supported H5P creation or import route for the material | Validate supported object types, scoring and accessibility; spreadsheet question import is a specific route rather than a generic conversion of every assessment |
| Detailed continuing documentation | Consider the optional Resource Library where its audience and permission model suits the service | Activation and commercial conditions must be agreed; reference access and structured course completion serve different purposes |
For the detailed package procedure, use Import and Update SCORM and xAPI Courses. Native assets and content design are covered in Introduction to Content Creation and Authoring, with video guidance in Upload, Organize, and Reuse Videos and Playlists and Add Video Subtitles, Transcripts, Cue Points, and Slides. Introduction to the Resource Library explains the optional reference-document service and its relationship to training.
Secure the sources, rights and maintenance owner
Confirm that your organization may reuse the material for the intended audiences and purposes. Check third-party images, embedded services, stock media, licensed packages and any content supplied by a previous provider. A file being available to download does not establish the right to republish or adapt it.
Keep the editable source alongside the maintained package where you own it. Record who can rebuild an externally authored course, which tool or vendor is required and how updates are approved. If only a compiled package remains, account for the resulting maintenance limitation instead of assuming a platform administrator can edit its internal screens.
Check dates, terminology, product versions and policy references. Decide who will maintain links and externally hosted material after the migration. Reusing an authoritative external video may be appropriate, but its availability and ownership remain with the external service or author.
Prove a representative migration end to end
Select a small set that represents your difficult cases, not just the shortest package. Useful examples include a course with scored questions, a long package with resume behavior, a second language, a native Course with shared assets and a recording with subtitles. Include the device and browser combinations important to your audience.
- Confirm the source owner, rights, expected learning outcome and expected completion evidence
- Import or upload the representative material using the correct content route; allow background processing to finish before judging a temporary placeholder
- Review the created Course or asset settings, ownership, language and any relevant readiness controls
- Create a representative Training Activity and connect the imported content to the intended modules and completion design
- Apply the required enrollment, schedule, commercial and certification conditions; prepare the participant-facing description
- Test launch, navigation, resume, assessment and completion as a representative participant
- Inspect the corresponding progress and reporting evidence as the operating role, then record the accepted migration pattern
Package standards do not guarantee identical behavior across every authoring tool. Verify what the package actually reports, particularly completion and passed/failed outcomes. A successful first screen or a completed import message is not evidence that assessment, resume and reporting work correctly.
Keep content, users and historical evidence separate
Importing a Course does not by itself migrate previous learners, registrations, scores or certificates. Prepare these as separate data sets with their own matching strategy and acceptance criteria. Agree the stable identity and ownership rules before importing people or linking SSO.
Classify historical records by business purpose. Some may be required to demonstrate an earned credential, some support continuity for a learner, and others are only useful for trend analysis. Decide which records must live in Eurekos, which can remain in a controlled historical archive and how your team will answer questions about the transition.
Do not promise that every old activity, score or certificate maps directly to a current object. Agree the supported migration scope, identifiers, date handling, status meaning and any required implementation work with the relevant data and technical owners. Test representative records before accepting a full history load. Use Import and Update Users in Bulk for account import; historical training data needs its own agreed process.
Build the new offer around the imported content
A copied course title is rarely enough for discovery. Prepare a useful Training Activity description: who it is for, the task or capability it supports, prerequisites, expected effort, delivery language and what the learner receives on completion. Explain schedules, assessment or certificate conditions where they matter.
Decide whether the original portfolio structure should remain. A long package may work as one Course module; a broader program may benefit from a Learning Path that combines existing content with an Event or Assignment. Keep the distinction between a reusable Course and the delivered Training Activity clear, especially when several customer groups share the same content.
Test the offer from the intended entry route. An existing customer may receive a direct assignment, while a new customer may discover the activity in the Storefront and complete checkout. The same content import can support both, but the registration and support processes still require separate verification.
Scale in batches with reconciliation
After the representative migration is accepted, group the remaining work into batches with clear owners and a recoverable source inventory. Record the old identifier, new Course or activity identifier, language, imported version, review outcome and unresolved issues. This mapping is useful for support and for replacing old links.
Agree a cutover rule for changes in the old system. If content and user records continue to change during migration, identify the final update, the source of truth and the reconciliation owner. Avoid asking two teams to maintain the same field indefinitely without a clear rule.
Keep a small verification sample from each batch, including any unusual format or exception. If a repeated issue appears, correct the pattern before processing the next batch. Retain source files and migration decisions under your organization’s retention and access policies.
Verify the migration outcome
| Scenario or check | Expected result or evidence |
|---|---|
| Content and rights | The correct maintained version, owner, language and usage rights are recorded |
| Participant use | Launch, navigation, resume and relevant device behavior match the intended learning experience |
| Evidence | Assessment, completion and certificate results appear under the intended participant and activity |
| Data continuity | Representative imported identities and agreed historical records reconcile with their source records |
| Discovery and enrollment | The intended audience can find or receive the offer and complete the applicable access or purchasing route |
| Operation | The team can identify the source, maintain the item and investigate a discrepancy using the old-to-new mapping |
Troubleshooting
| Problem | What to check |
|---|---|
| A course imported but is not ready for participants | Check background processing, asset placeholders, Course settings, readiness and the separate Training Activity configuration |
| A package launches but completion is missing | Review what the package reports, the configured statistics behavior and the activity’s evidence requirements |
| An imported file cannot be edited as native pages | Confirm its format; a compiled SCORM/xAPI package is not automatically converted into Eurekos native page objects |
| A person’s historical evidence appears under the wrong record | Stop scaling that data load and reconcile the source identifiers and account-matching process |
| Old links lead to the wrong or retired offer | Use the migration mapping to identify the intended current destination and update controlled references |
FAQ
-
Does importing a Course also enroll our learners?
No. Content import creates or updates the learning asset. Prepare the Training Activity and the intended enrollment route separately, then verify the participant’s access and evidence.
-
Can a SCORM package be edited as ordinary Eurekos native pages after import?
A SCORM package remains externally authored content. Maintain its internal screens in the source authoring tool and re-import an approved update through the supported process. Rebuild selected material natively when that better serves your maintenance or learning goals.
-
Should we migrate every course before launching?
Prioritize a coherent first portfolio and the records needed for the launch audience. Use representative migration tests and controlled batches. Retain a clear plan for deferred content and historical evidence so a phased launch does not create gaps in support or required records.
-
How should we estimate migration effort?
Measure representative items through import, review, corrections, delivery setup and participant verification. Include source recovery, rights, translations, account and history work where relevant. Multiplying upload time alone understates the work.