How to Move Your Courses to a New Platform Without Losing Students

A practical plan for moving courses to a new platform: what transfers, what you rebuild, how to keep students' access, and how to test before you switch.

By the Hopper team

Coach checking course access during migration

You can move your courses to a new platform without losing students or revenue if you treat it as a staged project, not a weekend export. Take inventory first. Build the new home next to the old one. Run both side by side for a few weeks, and only then close the old doors.

I know the feeling that comes with this decision. Your courses, your community and your checkout are the place where people trust you. Moving them feels like moving a household. This guide walks you through the whole move, step by step, in the order that protects your members.

TL;DR

  • List every asset first: lessons, files, members, orders, subscriptions, community posts, automations, domains. For each one, decide whether it moves, gets rebuilt or gets retired.
  • Names and emails usually import. Progress, certificates, subscriptions, discussions and email consent should never be assumed to move with them.
  • Build and test the new platform while the old one keeps running. Overlap the two for roughly a month, then retire the old one.
  • Redirect old links, rebuild automations by hand and tell members early about new logins.
  • Hopper offers free done-with-you migration and onboarding on both plans, if you want help doing it.

Table of Contents

Start with an inventory, not an export

The most common mistake is clicking "export" before you know what you are trying to keep. Open a spreadsheet and list every category of data your business holds. A migration checklist from Edtechkit frames it well: for each category, including course content, files, learner accounts, progress, certificates, orders, subscriptions, community, email consent, automations, domains and staff records, write down what moves, what you should not assume will move, and what proof will show it worked.

A simple version of that sheet has four columns:

AssetMoves, rebuilds or retires?Who does itHow I will check it worked
Video and audio lessonsRe-upload (keep your original files)You or your migration helperPlay every lesson on phone and desktop
QuizzesUsually rebuildYouTake each quiz as a test member
Member listImport via CSVYou or helperCompare counts to the old list
Subscriptions and paymentsPlan carefully, see belowYouTest a purchase and a renewal
Community postsArchive or rebuildYouScreenshot or export top threads
Email sequences and tagsRebuild by handYouSend each to your own inbox
Domain and old URLsRedirectYouClick every old link

This sheet becomes your project plan. It also becomes your safety net, because nothing gets switched off until every row has a check mark.

What usually transfers, and what you rebuild

Expect a split. According to a guide on migrating course platforms, user accounts and basic content often export through CSV files, while quiz formats and discussion history may need rebuilding or archiving. Progress data can sometimes be re-imported through an API or CSV. Another guide on education data adds that completion status, quiz data, detailed analytics and discussion history often do not transfer cleanly and may need manual handling.

Course data that transfers and needs rebuilding

In practice, here is how I would sort things.

Usually moves

  • Member names and emails. A CSV is the standard route.
  • Your raw media. You should always hold the original video, audio, PDFs and slide decks on your own drive. If you only have them inside your old platform, download them now.
  • Order and transaction history. Export your student rosters and transaction history before you cancel anything, and keep the records for tax and refund purposes, as the same guide advises.

Often needs rebuilding

  • Quizzes and certificates. Formats differ from platform to platform.
  • Automations, tags and email sequences. Per DDIY's migration article, most of these do not export and have to be rebuilt by hand on the new platform. Write down the logic in plain words ("when someone buys X, they get Y after two days") before you touch the old system.
  • Community history. Some platforms export members and posts, others export only a member list. Whichever you use, export what you can and screenshot the threads that carry your best teaching.

Consider retiring

A move is a rare chance to prune. Not every lesson from three years ago deserves a place in your new home. Start with the content your members actually use: the lessons that get opened, discussed and finished. Rebuild those first and carefully, and let the rest wait or go.

A three-phase plan you can follow

One step-by-step guide from course.coach splits a migration into three phases of about one to two weeks, one week and one week. That is a reasonable pace for a solo coach with a single programme. If you run several programmes, stretch each phase. Here is the plan I would use.

Phase 1: Build the new home

  1. Set up your branding, domain plan and navigation.
  2. Recreate your course structure and upload your lessons, quizzes and downloads.
  3. Connect payment processing and set up your products at the same prices.
  4. Build the sales or landing page and the welcome emails.
  5. Invite two or three friendly members to walk through it and tell you what is confusing.

If you are overwhelmed by the tech, this is where help matters most. Hopper's free migration and onboarding exists for precisely this phase.

Phase 2: Move people

  1. Export your member list and import it into the new platform.
  2. Send a migration email that explains why you are moving, what improves for them, the new login link, and a clear deadline.
  3. Warn people in advance that they may need to set a new password. One migration guide specifically recommends giving students that heads-up.
  4. Hold a short live walkthrough or record a two-minute video showing where everything lives.

The course.coach plan suggests a deadline of two to three weeks. I would tie yours to something natural, such as the end of a cohort or a billing cycle.

Phase 3: Close the old doors

  1. Redirect old URLs and update every link in your emails, bios and social profiles.
  2. Route all new sales to the new platform.
  3. Cancel the old platform only after the overlap period and your final checks.
  4. Archive a full backup of everything: content, rosters, transaction records.

Keep students' access intact during the transition

Students care about one thing: can I still get to what I paid for? Answer that before anything else.

Run both platforms side by side

The safest pattern is a parallel run. Existing students stay on the old platform while new sales route to the new one. The guide cited above recommends running both for 30 to 45 days. That costs you one extra month of subscription fees, and it removes the panic from the move.

Handle subscriptions with care

Recurring payments are the highest-risk item. CourseProfit Lab's checklist lists recurring billing, learner entitlements, progress history, email consent, domain changes and public redirects as the riskiest parts of a move. A practical approach is to leave existing subscriptions running on the old platform while you grant access manually on the new one, as the same listicler guide describes. Then move members onto new billing at a natural renewal point.

Some platforms cannot carry subscriptions across at all, which means members have to re-subscribe. Check how your current platform and payment processor handle this, and read your payment processor's own documentation about moving customer payment data before you promise anything to your members. Be honest with them in your email about any step they need to take.

Give people a person to ask

During the overlap, answer migration questions quickly. A dedicated email address or a pinned post in your new community, with a short FAQ, will prevent dozens of separate messages.

Test before you tell anyone

A pilot saves you from public embarrassment. CourseProfit Lab advises a pilot with real product types and test learners, freezing content changes during the move, cutting over in a controlled window and keeping a rollback path.

Here is a test list to adapt:

  • Create a test member for each product type: one-time course, membership, cohort, 1:1 package.
  • Buy each product yourself and confirm access arrives automatically.
  • Open every lesson on iPhone, Android and desktop.
  • Trigger every automated email and check the links in it.
  • Click your top ten old links and confirm they land on the right new page.
  • Confirm your refund process works.

If your new platform lets you route outgoing emails to your own address while you test, use it. Moodle guidance from Edzlms recommends diverting all outgoing email to the administrator's own address before any real student communication goes out. Even on a different system, the principle holds: your first test email should reach you, not your members.

Common problems, and how to prevent them

Most migrations that go wrong fail in the same few places.

Broken payment webhooks. DDIY notes that webhooks can break silently, so a purchase happens and nothing is delivered. Prevention: test a real purchase end to end and check the receipt, the access and the welcome email.

Reset automations. If tags and sequences are not rebuilt, existing members can get the wrong emails or start onboarding again. Prevention: write out your automation logic first, rebuild it, and test with a dummy contact.

Broken lesson URLs. Returning students click saved links and hit an error. The listicler guide calls 301 redirects from old lesson URLs to new ones essential for preserving search traffic and avoiding broken links. Prevention: map old to new URLs in your inventory sheet and redirect each one.

Lost consent. Having an email address is not the same as having permission to email it on a new system. Check consent status and your local rules, and keep your records. If you have members in the EU or UK, get advice from a data protection professional before you move lists.

Common problems, and how to prevent them

Silent drop-off. Members who never see your migration email simply vanish. Prevention: send the announcement more than once, post it in the community and mention it at the start of live sessions.

Why we built Hopper around this problem

We started Hopper because we watched coaches live inside a Frankenstein stack: one tool for courses, another for community, another for selling, and yet another for the app. Every piece had its own bill, its own login and its own way of breaking.

The moment someone decides to move, they run into the second problem: lock-in. Many platforms make leaving painful, and some earn from that. We think that is backwards. Your teaching and your people belong to you.

So we built a flat-price all-in-one around hubs. A hub is a self-contained space for one business or programme, and one account runs unlimited hubs on one plan. Each hub has Discussions, a Library, Async Sessions on Pro and a Landing Page, so your members join and buy in one place, and there is a native app on iOS and Android on both plans.

We also do the hard part with you. Migration and onboarding are free and done-with-you, led by the founder team. That is why the move should feel like arriving somewhere you belong, not like paying a toll to leave.

Cedrik, Founder at Hopper.so

Moving to Hopper: what it costs and what you get

If you are consolidating courses, community and checkout, Hopper gives you one plan for all of it. Base is $58 per month ($580 per year) and Pro is $108 per month ($1080 per year). Migration and onboarding are free. Both plans include unlimited hubs, members, team and products plus the native app, and Pro adds Async Sessions and 0% fees.

Hopper

Sprout, our built-in AI twin, answers students from your own lessons and escalates what it cannot answer, which helps during the first weeks when members have the most questions. If you are weighing options, our comparison of LMS platforms with community shows how seven of them stack up for coaches. When you are ready, start with Hopper and we will plan your move with you.

FAQ

How long does it take to move courses to a new platform?

For a solo coach with one programme, a realistic plan is three to four weeks of active work, following the one-to-two weeks, one week and one week phases in the course.coach guide. Add a 30 to 45 day overlap with the old platform for safety. Larger libraries or several programmes take longer.

Can I move student progress and certificates?

Sometimes, but do not count on it. Guides on education data report that progress, quiz data and discussion history often do not transfer cleanly. A practical fallback is to export completion lists, give affected members access to everything they have finished, and reissue certificates if needed.

What should I do about members with active subscriptions?

Leave existing subscriptions running on the old platform while you grant access manually on the new one, then move members across at a renewal point. One migration guide describes this approach. Tell members clearly what, if anything, they need to do.

Not if you plan for it. Set up 301 redirects from each old lesson or sales page to its new address, and update links in emails, social bios and your website. Check the top pages by clicking them yourself after the switch.

Do I have to rebuild my automations?

Mostly yes. DDIY reports that automations, tags and email sequences generally do not export. Document each one in plain words first, rebuild it, then test with a dummy contact before real members are affected.

Sources

On our list and want off? .