Migrating a course when student progress cannot come with it
Plan a fair transition for enrolments, completion records and access windows when the new system starts fresh.

You have uploaded every lesson to the new course platform. The videos play, the checkout works, and the launch date is in your calendar. Then you notice the awkward part: your old system knows that Priya completed lesson 8, Sam has 30 days left, and Alex bought lifetime access. The new system starts each person at the beginning. A course migration is therefore not just a file move. It is a decision about what you can prove, what you can honour and how much manual work you are willing to do.
Start with the promises, not the platform
Write down what each enrolment was promised at the point of sale. “Lifetime access”, “access until 30 June” and “access to the 2025 cohort” are not interchangeable. Neither are “completion certificate included” and “watch the lessons at your own pace”. Your migration plan should preserve the promise, even when the new software cannot preserve the old progress record.
| Record | Question to answer | Practical treatment |
|---|---|---|
| Enrolment | Did this person pay, and for which course? | Keep the original product name, purchase date and email address. |
| Access term | When should access end, if it ends at all? | Record the date, or label it as lifetime or cohort-based. |
| Progress | What has the learner completed or submitted? | Preserve the old record separately if it cannot be imported. |
| Outcome | Was a certificate, review or other result promised? | Create a route for the learner to request confirmation. |
This distinction prevents a common mistake: using a fresh account as evidence that a learner is a fresh customer. A new course dashboard may show zero completed lessons while your own sales and support records show that the person has already finished the course.
Make a migration register
Create one row per enrolment, not one row per person. Someone who bought two courses has two access arrangements, and someone who bought a course twice may need a decision about which record governs. At minimum, include the learner’s name, email, course, original purchase date, access promise, old completion status, new account status and any action still needed.
- 1Export the old course data before cancelling, downgrading or closing the old account. Download the lesson files and any available completion, quiz, certificate and access reports.
- 2Save a separate copy of the sales and enrolment information. Do not rely on the course dashboard alone: it may show activity without showing the original commercial terms.
- 3Match records using email address first, then investigate duplicates, changed addresses and shared household accounts.
- 4Mark each learner as ready, needs access correction, needs progress confirmation or needs a personal reply.
- 5Keep the register until every promised access window has ended, or for as long as you need to answer reasonable questions about completion.
Choose what “progress” needs to mean
There are at least three useful outcomes. First, the learner can continue from roughly the right place. Second, you can verify that they completed the course. Third, the new dashboard shows every historical tick and quiz result. These are increasingly difficult to reproduce. Decide which outcome your promise requires before you spend hours trying to achieve the third.
For a self-paced course, access may matter more than a perfect visual history. Send the learner a short note explaining that the new course starts with a clean progress display, while your register records their previous position. If they want to continue, ask them to tell you the lesson they last completed and correct the record where appropriate.
For a course with assessment, accreditation or a completion certificate, use a stricter process. Keep the original evidence, note the date of completion and define who can approve a correction. A screenshot from a learner may help, but it is not the same as an export from the old system. Say what evidence you accept rather than deciding case by case in silence.
Set access windows deliberately
Access is easier to mishandle than files because it combines a date, a product and a person. For each enrolment, calculate the promised end date from the original terms. If access was for 90 days, the end date is tied to the agreed start or purchase rule, not to the day you upload the new course. If access was lifetime, do not attach an expiry merely because the new platform asks for one.
Use a transition rule that you can explain in one sentence. For example: existing learners keep the access period they bought, and any learner whose new account shows the wrong end date can contact you for correction. Avoid making everyone buy again or asking learners to prove a purchase that you already have in your records.
If you are rebuilding the course in store.fan, check that the offer and access arrangement match the promise you are carrying over. Store.fan supports [online courses](/features/online-courses), while your migration register remains the source of truth for historical progress that cannot be displayed in the new system.
Communicate before the reset is visible
Send the transition message before learners log in and see an empty progress bar. Keep it factual. Include the date of the move, the new sign-in route, what happens to access, whether old completion records appear, and how to report an error. Give one deadline for corrections if you need to manage the workload, but do not use a deadline to erase an access promise.
- “Your enrolment is moving to a new course area on [date].”
- “Your previous lesson ticks may not appear in the new dashboard.”
- “Your access end date remains [date], or your access remains ongoing where lifetime access was promised.”
- “If your course, email address or access date is wrong, reply with the details and we will check the migration register.”
After launch, check a small but representative set: a recent buyer, an older buyer, a learner with limited access, a lifetime buyer, someone with recorded completion and someone with an unusual email address. This is not proof that every record is correct, but it can expose a mapping error before the first support message does.
Build the correction process into the new home
A transition is not finished when the videos upload. It is finished when a learner can find the right course, retain the access they were promised and get a useful answer when the history looks wrong. Keep the old export in a controlled location, record each correction and update the learner when it is done.
If you are moving your wider customer records as well, a storefront such as store.fan can give you one place for the offer and customer relationship. Its paid plans start with a 14-day trial, and its Pro plan adds email marketing. You still need to check the plan and workflow against your own records: a storefront does not remove the work of deciding which historical facts you are prepared to stand behind.
Not if re-enrolment would make them pay again or lose a promised access period. Create or invite the new account using the original enrolment record, then correct any access mismatch manually.
Tell learners before the move. Preserve the old export, record the best available completion evidence and offer to confirm or correct their position. Do not present a clean new dashboard as proof that they completed nothing.
Keep them for as long as you need to administer the access promises and answer completion questions. The exact period depends on your course terms, business records and legal obligations, so set a retention rule you can follow consistently.
Plan your course transition, then build the new home on store.fan.
Start your trialTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



