Migrating to LearnWorlds means moving your courses, videos, quizzes, user accounts, and purchase history from platforms like Teachable, Kajabi, Thinkific, LearnDash, or Moodle into a LearnWorlds school. Most migrations take 2–6 weeks. LearnWorlds offers its own migration services, and partners like VertoLaunch handle complex moves end to end.
Harshita C, Director of Platforms · 2026-07-31
A LearnWorlds migration has four workstreams: content (courses, videos, files, assessments), people (user accounts and enrollments), money (pricing, bundles, subscriptions), and traffic (your domain, page URLs, and redirects). The platform gives you real tooling for two of them. Users can be bulk imported and enrolled from spreadsheet files, up to 10,000 rows per file, and during import you can mark courses or learning programs as already complete for learners who finished them on the old platform. On the content side, LearnWorlds accepts SCORM 1.2, SCORM 2004 (3rd and 4th Edition), and HTML5 packages as ZIP uploads of up to 400MB each, which matters a lot if you are coming from an LMS that already speaks SCORM.
Everything else is a rebuild, not a transfer. There is no button that converts a Kajabi product or a Thinkific course into a LearnWorlds course. The honest framing: a migration is one part data move, two parts rebuilding your school in a better-structured way. Teams that accept that early plan realistic timelines; teams that expect a one-click import discover the rebuild in week two.
Every source platform fails in its own way. These are the ones we hit most often.
Teachable exports student lists and transaction history as CSV, but there is no full-content bulk export, so videos come from your original masters or lesson-by-lesson downloads. Quizzes and coding exercises are rebuilt by hand. If you sell through Teachable's own payment gateway, plan the subscription cutover early, because those billing relationships stay behind.
Kajabi has no comprehensive content export; its own documentation tells you to keep local backups of videos and files, so hope you did. The bigger trap is that Kajabi bundles marketing with the LMS: funnels, email sequences, and one-click upsells have no LearnWorlds equivalent and move to a dedicated email and funnel stack instead. Budget time for that re-architecture, not just the courses.
Thinkific is the friendliest source: videos, PDFs, and audio can be downloaded from the course builder and student lists export to CSV, so the content side is mostly re-upload work. Quizzes still do not export in a format LearnWorlds can ingest, so question banks are rebuilt. Communities and spaces are recreated in LearnWorlds' community area rather than moved.
LearnDash lives inside WordPress, so your content sits in posts, plugins, and the database; extraction is a developer task, not an export button. LearnDash quiz data will not import, and courses are usually either rebuilt natively or repackaged as SCORM through a course development team so they stay portable. WooCommerce subscriptions and memberships must be recreated on the LearnWorlds side.
Moodle's .mbz backup files cannot be imported into LearnWorlds, so course shells are rebuilt. The good news: SCORM packages already in Moodle usually re-upload cleanly, since both platforms support SCORM 1.2 and 2004. Gradebook history and cohorts need CSV exports and a mapping plan, and if your Moodle is self-hosted, decommissioning the server stack is its own small project.
The same logic applies to Podia, Skool, Drupal-based systems, and custom builds: audit what exports, assume the rest is a rebuild, and test one course end to end before committing to a timeline. We have run this play from platforms most people have never heard of. The audit is always step one.
The short version: files and people move well, interactivity and billing get rebuilt, and your URLs need a redirect plan.
Swipe to compare
| Does it transfer?Straight answer | What actually happensIn practice | |
|---|---|---|
| Courses & curriculum | Partially | Structure is recreated in the LearnWorlds course builder; SCORM packages upload directly, native lessons are rebuilt |
| Videos & files | Yes | Downloaded from the source (or your masters) and re-uploaded; clean if you still hold the originals |
| Quizzes & assessments | Rarely | Question banks almost never export in a compatible format; rebuilt in LearnWorlds, or carried inside SCORM packages |
| Certificates | Partially | Templates are rebuilt; certificates already issued on the old platform should be exported and archived before cutover |
| Completion history | Partially | Bulk import can mark courses or programs complete; per-lesson progress cannot be replayed, so export source reports first |
| Payment subscriptions | No | Plans are recreated in LearnWorlds and subscribers re-subscribe; time the old billing shutdown so nobody pays twice |
| SEO URLs | No | URLs change; every old course and landing page gets a 301 redirect to its LearnWorlds equivalent before launch |
Platform capabilities as of 2026; LearnWorlds features vary by plan, so confirm your plan includes SCORM uploads and bulk actions before you schedule the move.
Inventory every course, video, quiz, certificate template, coupon, and automation on the old platform. Export user lists, transactions, and progress reports now, while you still have full access, and pull your original video masters together.
Decide what moves as-is, what gets rebuilt, and what gets retired. Most catalogs carry dead weight; a migration is the cheapest moment you will ever get to drop it.
Branding, site pages, course players, pricing, bundles, subscription plans, certificates, and email settings, built against the map rather than improvised as you go.
Re-upload videos and files, rebuild quizzes and native lessons, and upload SCORM packages where they exist. Validate one full course end to end before doing the other forty.
Bulk import accounts, enroll learners into the right courses, and mark historical completions so certificates and access carry over. Spot-check counts against the source exports.
Point the domain, publish the 301 redirect map, run a pilot group through real courses, then switch. Keep the old platform in read-only reach for a few weeks as your safety net.
Typically 2–6 weeks depending on catalog size, how much content needs rebuilding rather than re-uploading, and how many user records are moving. A school with five courses and a few hundred students can be live in 1–2 weeks. A catalog with dozens of courses, custom quizzes, and active subscriptions usually lands in the 4–6 week range. Large academies with historical compliance records or six-figure user counts run 8–12 weeks, mostly because validation, not uploading, becomes the long pole. Whatever the estimate, the subscription cutover date drives the schedule: pick it first and plan backwards.
Right when the catalog is small, no subscriptions are running, and someone on your team has the hours. LearnWorlds publishes a step-by-step migration guide and support articles covering user import, content upload, and final cutover. The hidden cost is your time: the rebuild work is straightforward but long.
LearnWorlds offers in-house migration services, starting with a free consultation, covering course content transfer, course settings, recreation of bundles and subscriptions, and user migration. It also runs an Experts directory of certified professionals for adjacent work. A solid default if your move is a clean lift from one mainstream platform.
Right when the move is messy: multiple source systems, courses that need instructional rework, SCORM repackaging, historical compliance records, or an agency delivering the migration under its own brand. A partner owns the whole runway, from audit to redirects to post-launch support, and answers for the result.
VertoLaunch sits in the third category. We have delivered LearnWorlds migrations from Teachable, Kajabi, Thinkific, LearnDash, Moodle, and Drupal-based systems, including migrations with hundreds of thousands of user records, through our LMS implementation and migration service. We are not a LearnWorlds reseller, so if your situation is a clean DIY or a good fit for LearnWorlds' own team, we will say so on the first call.
Related reading: how to migrate an LMS without losing completion records and SCORM vs xAPI.
We'll send you our white-label partner evaluation checklist: the 30+ checks we'd run on any eLearning vendor before handing them client work, including us.
Book a 20-minute call and walk through your catalog. We'll tell you honestly whether it's a DIY job, one for LearnWorlds' own team, or a project worth handing to us.
Book Your 20-Min Discovery Call →