How to switch course platforms without losing a single student

By Norie Delgado · 7 minute read

Every course platform migration starts the same way: someone has outgrown their platform, found a better deal, or watched their current tool sunset a feature they depend on. And every one carries the same fear: "what if my students fall through the cracks?"

Fair fear. A course migration moves three fragile things at once: your content, your people, and the invisible wiring between them. Miss any of the three and you get the messages nobody wants: "I can't log in," "my progress is gone," "why am I getting welcome emails for a course I finished in 2024?"

I've moved courses between Kajabi, Podia, and friends enough times to have a checklist I trust. Here it is, with the three tests everyone skips at the end, because those are the ones that bite.

Phase 1: Inventory before you touch anything

You can't move what you haven't counted. Before building anything in the new platform, list out:

• Content: every course, module, lesson, video, download, and quiz. Note where videos are actually hosted, since platform-hosted video needs re-uploading while embedded video usually doesn't.
• People: active students, completed students, refunded students, and free or legacy access grants. Each group gets handled differently.
• Progress data: does the new platform support importing completion status? If not, decide now how you'll handle "where did my progress go?" (Hint: a simple "mark complete as you skim" note in the welcome email defuses most of it.)
• Money: active payment plans and subscriptions. These are the most delicate part of any migration, because billing usually cannot transfer silently. Map out who's mid-payment-plan before deciding your switch date.
• Wiring: every automation, integration, and zap that touches the old platform. Check your email tool, your Zapier account, and your checkout pages. There is always one someone forgot.

Phase 2: Build the new home in parallel

Keep the old platform fully running while you build the new one. Recreate the course structure, re-upload content, rebuild the checkout flow, and reconnect the automations in the new tool. Nothing points at the new platform yet; you're building the house before anyone moves in.

Phase 3: Move the people

Export your students from the old platform, clean the list (duplicates, refunds, test accounts), and import them into the new one with the right course access. Two rules keep this painless:

1. Import in batches, not all at once. Do a ten-person test batch first, including your own test account. Verify access, then run the rest.
2. Suppress the automations while you import. This one gets its own section below, because it's the number one migration disaster.

The three things everyone forgets to test

1. What your automations do to imported students. Most platforms treat an imported student like a brand-new signup, which means your shiny welcome sequence happily fires at 900 people who bought the course two years ago. Before importing anyone, check what triggers on "new student added" and turn it off or add a condition. This is the mistake that fills inboxes and erodes trust in one afternoon.

2. The login experience for migrated students. Passwords almost never transfer. Your students will need to set a new one, and if the first they hear of it is a failed login, you've created hundreds of support tickets. Test the exact flow yourself with a dummy account: what does the reset email look like, does it land in spam, is it obvious what to do? Then tell students what to expect before switch day, in plain words.

3. The links inside your own content. Lesson 4 links to Lesson 12. Your emails link to the old course URL. Students have the old login page bookmarked. Sweep your content and your email sequences for old-platform links, and set up redirects from the old URLs if your setup allows it. A migration where every internal link still points at the old platform is only half a migration.

Phase 4: Switch and watch

Pick a low-stakes switch day (not mid-launch, not a Friday). Point your sales pages and links at the new platform, send students the "here's your new home" email with login instructions, and then actually watch: support inbox, failed-login reports, automation logs. The first 72 hours tell you everything.

Keep the old platform alive but closed for at least 30 days as your safety net and your reference copy. Cancel it only when the new home has survived a full billing cycle without surprises.