Thinking about leaving LearnDash? Your courses are only part of the move. Student accounts, enrollments, learning progress, payments and public URLs all need a plan.
To migrate from LearnDash, audit your existing site, back it up, agree how each data type will map to the new platform, run a test migration, validate the student experience and then switch your live academy. Keep the original site available until the checks are complete.
This guide explains what to check before moving to another LMS, including a hosted platform such as AcademyLauncher.
LearnDash can be a good fit for an academy built around WordPress. A move becomes worth considering when maintaining your particular combination of hosting, themes, plugins and integrations takes time away from teaching.
Start with the outcome you want. Do you need simpler administration, a different student experience, integrated bookings or fewer separate tools? Compare the new platform against those requirements before choosing it.
Include the full operating cost: hosting, licenses, video delivery, payment processing and maintenance. A lower subscription price alone does not establish that a migration will save money.
Create a migration inventory before exporting anything.
Area | What to check |
|---|---|
Courses | Course descriptions, lesson and topic order, prerequisites and drip rules |
Media | Videos, images, PDFs, downloads and access permissions |
Assessments | Questions, answers, scoring, pass marks and attempt limits |
Students | Account details, enrollments, roles and login arrangements |
Learning history | Completed lessons, course progress, quiz attempts and submissions |
Certificates | Issued records, learner access and future certificate rules |
Payments | Orders, subscriptions, renewals and course access after payment |
Community | Groups, discussions and data stored by separate plugins |
Public pages | Course URLs, blog posts, metadata and redirects |
Give every item a destination: migrate it, rebuild it or retain an accessible archive. Do not assume that importing course content also transfers student history.
List the plugins involved in your academy, including LearnDash add-ons, WooCommerce, membership tools, community software and page builders.
Identify which tool owns each piece of data. A community profile or a recurring payment may be managed outside LearnDash, even when students experience everything as one website.
Choose one representative course for the first test. Include lessons, topics, a quiz, media and students with different completion states.
Create a full backup of your WordPress database and files, and confirm that you can restore it.
Retain separate copies of important learner and business records where available. Record baseline counts for courses, users, enrollments and completions so that you can compare the destination against the source.
Keep exports containing student information in a restricted location.
LearnDash documents a built-in export under LearnDash LMS → Settings → Advanced → Import/Export for transfers between LearnDash sites.
Moving to a different LMS requires a destination-specific importer or a separate transformation process. A LearnDash export is not a universal package that every platform can import.
LearnDash also documents WordPress Tools export for some course content, with limitations around course relationships and quizzes. Choose the method with your migration provider rather than treating every export route as interchangeable.
Source: LearnDash course transfer documentation.
Write down how courses, lessons and topics will appear in the destination. Check shared content, prerequisites, drip schedules and quiz placement.
Review page-builder content and shortcodes separately. The text may be reusable while the layout or interactive behavior needs rebuilding.
For H5P, gamification and community add-ons, test the exact features your students use. Importing an embedded activity does not by itself establish that its scores or completion history will transfer.
Use a separate test academy before changing the live site.
Check your representative course as an administrator, instructor and student. Compare lesson order, media playback, quiz scoring and access permissions. For progress migration, inspect individual learner records as well as total counts.
Test a new student, a partially completed student and a completed student. Agree how unsupported historical records will remain available before proceeding.
Confirm whether students can use their existing credentials or need an account activation or password reset email.
Test purchase, enrollment and access expiry. For subscriptions, establish where existing renewals will run and how they will continue granting access. Do not cancel old billing arrangements until the replacement process has been verified.
An imported order record and a functioning recurring subscription are different things.
Create a list of public pages that attract traffic or backlinks. Where URLs change, map each old URL to the closest relevant replacement and implement permanent server-side redirects.
Google recommends retaining redirects for as long as possible, generally at least a year. Search visibility can fluctuate during a move, so redirects are part of a migration plan rather than a guarantee of unchanged rankings.
Update internal links, canonical URLs and the sitemap, then monitor indexing and errors in Google Search Console.
Source: Google guidance on site moves.
Schedule the final data transfer and communicate any pause in purchases or learning activity. Account for changes made since the test import, including new students, payments and completed lessons.
AcademyLauncher is a hosted learning platform from the team behind WPLMS. It brings course delivery, website pages, communities and instructor bookings into one platform.
If your goal is to reduce the work of maintaining a WordPress LMS stack, start by checking your existing academy against AcademyLauncher’s features.
For a LearnDash migration review, prepare your website URL, approximate course and student counts, required add-ons and the learner history you need to preserve. These details help establish the scope of a test migration and identify anything that needs rebuilding or archiving.
Explore AcademyLauncher and request a review of your LearnDash migration requirements before switching your live academy.
Potentially, depending on the destination’s importer and your content. Course structure and standard content may be transferable, while custom layouts, shortcodes and integrations require separate work.
Progress needs explicit mapping and validation. Confirm support for lesson completions, quiz results and other required records before agreeing to a migration.
This depends on the destination’s authentication system and migration method. Establish the login process in advance and test it with sample accounts.
You may be able to use your existing domain if the destination supports it. Domain configuration and individual page URLs are separate checks; changed paths still need redirects.
The scope depends on your content volume, media, integrations, learner history and billing setup. Use the test migration to establish the work and timing.
Keep a secure backup and retain access to required historical records. Retire the old site only after content, access, billing and redirects have been validated.