Before moving a systeme.io lecture to another course, check who uses it and what depends on it. The official guide says a move resets that content’s related student progress, access rules and automations. The content also arrives inactive.
Use this guide when reorganizing courses inside the same systeme.io workspace. A move between course platforms needs a separate migration check.
Pause before moving if the course types differ or you cannot explain how current learners will keep the access they need. The official guide also says an item cannot be moved or duplicated while either operation is already in progress.
Choose the operation before touching a live lesson
Systeme.io’s course-creation guide distinguishes two actions: Duplicate makes a copy within the same course; Move transfers a module or lecture to a different course. Moves require the same course type, such as classic to classic. Duplicated and moved content is inactive in its new location.
If you want both courses to keep a version of a lesson, a move does not express that goal. Confirm a supported copying workflow before proceeding. Do not treat a duplicate as a tested backup or assume learner state is preserved.
Check three dependencies
Learners: who still needs the lesson in the original course? Keep the promised learning path available, or decide a workable replacement before making the change.
Progress: what record will you need afterward? Systeme.io documents a student and progress CSV export. Inspect which fields are included. An exported record does not establish that progress can be restored.
Rules: note the access conditions and automations tied to this content. Decide what needs rebuilding in the destination and what needs checking in the original course.
Activate only after the replacement path is ready
In the destination, review the inactive lesson’s content, links, intended access and related rules. The official activation instructions use Assets → Courses → the lecture’s three-dot menu → Activate. Activation is a publication step; it does not prove the correct learner can open the lesson.
Use an authorized test setup before changing a selling course. After activation, check whether existing Course A learners can continue through their planned path, and whether intended Course B learners can open the destination lesson. Check the resulting progress state and relevant automations too. Record unfinished checks as unverified.
Copy a before-and-after change note
Date, action and reason: [date; duplicate/move; why]
Item and location: [lecture/module; original course → destination]
Existing learner path: [what must remain available]
Before: [progress record; access conditions; related automations]
Destination reviewed: [content; links; rules; activation status]
After: [learner access in both courses; progress state; automation results]
Unverified or broken: [item; next action; owner]
Fallback: [how learners can continue if the change fails]
Example: moving a revision exercise from Course A to Course B leaves a question to solve first: how will current Course A learners finish their promised exercise? If you cannot answer that, pause the move. Once the new route works, explain any learner-facing change with a short update notice.
Official sources checked September 12, 2026. This is a documentation-based guide with original planning diagrams and an illustrative example. We have not performed a move, restored progress or tested these rules in a product account. No signup or affiliate links.