# What must survive when learning content moves between platforms?

By Sean Everett · October 6, 2026

Preserve the learner journey, tracking meaning and distribution controls alongside the content files, then test the new delivery arrangement.

Topics: Learning platforms · Content migration · Product operations

## Inventory the learning experience as well as the files

A course can combine several objects, assignments, prerequisites and completion rules. Record those relationships before counting packages. Decide which identifiers, learner history and reporting meanings must continue, and which changes are intentional.

1EdTech’s Common Cartridge standard covers exchange of learning resources, assessments and links. Thin Common Cartridge instead distributes a collection of links to content that can remain with its publisher. That difference changes what a migration actually transfers.

For each content family, identify whether the destination receives a copy or depends on a remote source. Separately establish the rights to move, modify and distribute it. A technically importable package is not evidence of permission to reuse its contents.

## Test the behavior around playback

Open representative material as a learner and follow it through start, interruption, return and completion. Check navigation, media, assessment results and the record visible to an administrator. Include the browsers and access conditions learners actually use.

Moodle’s SCORM documentation shows why this matters: package settings affect navigation, attempts, grading, progress storage and external delivery. The same content file can therefore produce a different experience when its surrounding configuration changes.

Compare the meaning of recorded outcomes, not just whether a score appears. Identify where a destination cannot preserve an old behavior. Agree on an explicit replacement and explain its reporting implications before moving the rest of that content family.

## Prove update and access behavior after migration

For remotely supplied content, test an update at its source and observe what changes in the destination. For copied content, assign responsibility for distributing revisions. Check how access ends when a learner, customer or content license is no longer eligible.

Restoring course structure also needs review. Moodle’s restoration guidance describes choices about included activities, configuration and dates, with different date behavior for user records and course activities. Treat a successful import as the start of acceptance testing rather than its conclusion.

Keep a small set of repeatable checks for each delivery pattern. Include support ownership when a problem crosses the content supplier, hosting service and learning platform. A migration is ready when learners and administrators can complete the required work with understood controls and a workable support path.

## Related reading

- [1EdTech: Common Cartridge and linked learning content](https://www.1edtech.org/standards/cc)
- [Moodle: SCORM delivery and tracking settings](https://docs.moodle.org/503/en/SCORM_settings)
- [Moodle: Course restoration and configuration](https://docs.moodle.org/503/en/Course_restore)
- [Planning a legacy-platform transition](https://evergences.com/insights/legacy-platform-modernization-roadmap/)

Source: https://evergences.com/insights/learning-content-portability-controls/