Send us a message and we'll get back to you shortly.
On April 22, 2026, LiquidWeb dissolved StellarWP - the corporate parent of LearnDash - and folded roughly ten WordPress brands into just four products. LearnDash technically survived the cuts. The team that built it did not. LearnDash.com now redirects to LiquidWeb. The Product Owner and ~25% of staff were laid off in November 2025. And LiquidWeb has committed to security patches only through April 2027 - a roughly 12-month support cliff for a plugin that powers 83,415 course websites.
If you run a LearnDash site, this is the planning moment. Not because LearnDash is "shutting down" - it isn't, in the literal sense - but because the product you bought no longer exists in any meaningful organizational sense. The brand, the team, and the roadmap are gone. The plugin is still on disk. Whether that's good enough for you depends on what your LMS does for your business.
This guide does three things no other post about the dissolution does:
The dissolution wasn't a single event. It was a 12-month decline that ended with a botched relaunch.
| Date | Event |
|---|---|
| September 2021 | LiquidWeb acquires LearnDash, adds it to the StellarWP portfolio |
| October 2025 | Nexcess absorbed into LiquidWeb; loses independent brand |
| November 2025 | ~25% workforce reduction (36 people); LearnDash Product Owner Taylor Walden among those laid off |
| Late 2025 | KadenceWP founder Benjamin Ritner departs; GiveWP co-founders Matt Cromwell and Devin Walker give notice |
| April 22, 2026 | LiquidWeb officially dissolves StellarWP, consolidating ~10 brands into 4 (Kadence, LearnDash, The Events Calendar, Give) |
| May 2026 | LearnDash.com, KadenceWP.com, GiveWP.com begin redirecting to LiquidWeb |
| April 2027 | LiquidWeb's committed end date for critical security patches on retiring features |
GiveWP co-founder Devin Walker summarized the mood publicly
Private equity often takes a hard edge, putting profits over people and disregarding morale.
The May 2026 rollout itself went badly. Independent reporting from The Repository and Search Engine Journal documented login failures, missing invoices, and lifetime-deal customers unable to confirm what they still owned. Kadence Theme v1.5.0 quietly added a permanent Liquid Web admin panel that users couldn't disable. Competitors didn't wait for the dust to settle - Awesome Motive's Syed Balkhi published a public invitation to StellarWP customers and ex-founders within days.
LearnDash is not technically shutting down. On April 22, 2026, LiquidWeb dissolved the StellarWP brand that owned LearnDash, absorbing it into LiquidWeb directly. LearnDash continues to receive updates and critical security patches through April 2027, but its independent team, brand, and roadmap are gone.
LearnDash's parent company, StellarWP, was dissolved by LiquidWeb on April 22, 2026, consolidating ten brands into four products. LearnDash's product owner and most senior staff departed in late 2025. The plugin still ships, but with a reduced team, no independent brand, and security-only commitments through April 2027.
LearnDash is not one market. It's two and they need very different responses to the dissolution.
A 2026 study of 240,000 WordPress LMS websites found LearnDash held 34.8% market share overall, powering 83,415 sites. But among sites with high tech spend - the premium segment - LearnDash's share jumps to 60.3%. Customers in that segment include the University of Florida, Yoast, and DigitalMarketer.
About 70% of LearnDash sites belong to teams of 1–10 people (Software Advice, 2026). For those operators, the right move is often patience: keep the plugin running, monitor for genuine security issues, and plan a migration over 12 months. The other ~30% - universities, regulated training providers, multi-tenant platforms, mid-market course businesses - face real continuity risk. An LMS that handles credentialing, compliance, or institutional reporting cannot run on unmaintained software past April 2027.
Every honest learndash alternative 2026 decision lands on one of five paths. The right path depends on your scale, your team, and how much WordPress is helping you versus getting in the way.
| Path | Best For | Cost Profile | Tradeoffs |
|---|---|---|---|
| Stay on LearnDash | Tiny sites, no compliance pressure | $199–$799/yr license | Plugin works, but no roadmap, ~12-month security commitment |
| Another WordPress plugin (Tutor LMS, LearnPress, LifterLMS) | Small WP-based course sites that want to stay in WP | $0–$199/yr license + WP overhead | Same WP fragility; different vendor but same architecture |
| Hosted SaaS (Kajabi, Thinkific, Teachable, Podia) | Course creators leaving WordPress entirely | $40–$300/mo | Lose WP, lose customization; great for solo creators |
| Self-hosted Open edX | Engineering-led teams that need real scale and full control | $0 license + significant devops | Free software, real ops cost — see TCO section- |
| Managed Open edX or Cubite LMS | Universities, enterprise training, multi-tenant operators who want institutional features without devops | $290/mo (Cubite LMS) to $1,900/mo (Managed Open edX) | Higher sticker price, lower total cost of ownership |
The best LearnDash replacement depends on scale. For small WordPress sites, Tutor LMS or LearnPress are easiest. For mid-market and enterprise - universities, training providers, multi-tenant platforms - Open edX (self-hosted or managed) and Cubite LMS offer institutional-grade features LearnDash never matched, with no risk of brand dissolution.
The next two sections take the most under-covered option seriously: Open edX, the open-source platform that powers MIT, Harvard, and ASU. Almost no LearnDash-alternative article includes it. They should.
Open edX is the open-source LMS originally built at MIT and edX, now maintained by an independent open community plus 2U/edX. It runs on its own stack (Django/Python, with React-based frontends called MFEs — Micro-Frontend Apps — the modular UI building blocks Open edX uses). It is not a WordPress plugin. That difference is the whole story: every Open edX advantage comes from being purpose-built for serious learning, and every Open edX challenge comes from not being a $199 download.
Recent releases show an actively maintained, modern platform:
A direct comparison:
Feature | LearnDash (2026) | Open edX (Teak / Verawood) |
|---|---|---|
| License | $199–$799/yr per site | Free, open-source (AGPL) |
| Architecture | WordPress plugin | Standalone Django/Python platform |
| Course authoring | WP admin + Gutenberg | Open edX Studio (purpose-built CMS) |
| Cohorts and sections | Via add-ons | Native |
| Proctoring | 3rd-party plugin | Native integrations (multiple vendors) |
| Certificates | Native | Native, programmable templates |
| xAPI / SCORM | Add-on | Native xAPI; SCORM via plugin |
| Multi-tenant | Multisite hack | Native organizations + sites |
| Content reuse across courses | Limited | Content Libraries (Sumac+) |
| Analytics | ProPanel add-on | Native Aspects dashboard, Superset-based |
| Enterprise users | Yoast, U. of Florida, DigitalMarketer | MIT, Harvard, ASU, IBM, US DOD |
| Self-host complexity | Low (any WP host) | High (Tutor deployment, ops) |
| Future-proofing | Uncertain (dissolution risk) | Active OSS roadmap |
Open edX is a strong LearnDash alternative for organizations needing real scale, deep customization, or institutional features (cohorts, proctoring, certificates, xAPI). It is fully open-source and free to license, used by MIT, Harvard, and ASU. The tradeoff is operational complexity - self-hosting requires devops, which managed providers like Cubite handle.
The honest disclaimer that competitor articles skip: Open edX's biggest cost is not the install. It's the year-two operational cost - upgrades, patching, scaling, MFE customization. "Free software" is true; "free LMS" is not. That's why the managed path exists, and why it's usually the right answer for organizations whose business isn't running Django services.
The technical core: LearnDash stores courses as WordPress custom post types
Open edX uses OLX (Open Learning XML), with content broken into XBlocks, modular content units (video, problem, HTML, discussion) that are the building blocks of every Open edX course. There is no native one-click bridge between the two. Independent migration vendors handle the gap manually; so does Cubite.
Step 1: Audit. Inventory courses, lessons, topics, quiz items, certificate templates, user roster, progress data, and every integration (payment, email, SSO, analytics, third-party add-ons). Anything not on the list will surface mid-migration.
Step 2: Pick your target. Self-hosted Open edX, managed Open edX, or Cubite LMS SaaS. Decide before you start exporting.
Step 3: Export from LearnDash. Use LearnDash's built-in Import/Export tool for site-to-site mirrors. For cross-platform moves, dump CPTs and meta to structured JSON or CSV - courses, lessons, topics, quizzes, questions, and the parent–child relationships.
Step 4: Map content to OLX. This is the work. Each LearnDash course becomes an Open edX course, each lesson becomes a chapter, each topic becomes a sequential or vertical, each quiz becomes a problem XBlock. HTML lesson bodies translate cleanly; embedded video shortcodes need a video XBlock conversion; LearnDash quiz types map to Open edX's CAPA problem types (Computer Assisted Personalized Approach - Open edX's native assessment format covering multiple choice, numerical, formula, code-graded, and drag-and-drop) with a transformation step per question type.
Step 5: Re-import via Open edX Studio. Studio (the Open edX authoring tool) accepts OLX tarballs directly. Each mapped course imports as a draft. Run a sanity pass: structure, asset links, problem behavior.
Step 6: Migrate users and progress. User roster moves via CSV import. Historical progress is the hard part - LearnDash stores completion at the user/lesson/topic granularity; Open edX records state per XBlock per user in courseware_studentmodule. Decide whether to migrate progress (custom script + LMS API) or reset and re-enroll. Most operators reset for non-credentialed courses and migrate for credentialed ones.
Step 7: Cutover. DNS plan, redirects from old LearnDash course URLs to new Open edX course URLs, learner communications, and a parallel-running window of at least 30 days for support tickets.
Here's the honest TCO for a mid-sized course operation (≤5,000 learners, ≤200 courses), Year 1 + Year 2 combined.
| Path | License | Infrastructure | Ops / Dev time | Migration (one-time) | 2-year total |
|---|---|---|---|---|---|
| LearnDash today | $400–$1,600 | $300–$1,200 (WP hosting) | $1,000–$4,000 (plugin maintenance) | $0 | $1,700–$6,800 |
| Tutor LMS / LearnPress / Lifter | $0–$400 | $300–$1,200 | $1,000–$4,000 | $1,000–$5,000 | $2,300–$10,600 |
| Self-hosted Open edX | $0 | $300–$1,200 (server + DB + storage) | $1,000–$4,000 (devops engineer time) | $1,000–$5,000 | $2,300–$10,600 |
| Managed Open edX (Cubite) | $0 | Included in fee | Included (20 support hrs/mo) | $0 | $1,7000-$3,000 |
| Cubite LMS SaaS | Included in fee | Included | Included | $ | $1,300 |
A few honest observations from this table:
LearnDash sites will keep working past April 2027, but LiquidWeb has only committed to critical security patches through that date. After April 2027, there is no formal support guarantee. Sites running LearnDash should plan a migration strategy now to avoid running unmaintained software in production.
Cubite has built and operated LMS platforms since 2013. The customer list - Starbucks, Snowflake, Redis, Arizona State University, The Open University - is the segment hit hardest by the LearnDash dissolution: organizations whose LMS earns revenue, trains compliance, or grants credentials. We offer two paths:
Cubite LMS: Fully managed SaaS, unlimited users and courses, AI course generation, modern checkout and enrollment automation. Built for course businesses and mid-market training teams that want a real LMS without running one.
Managed Open edX: Dedicated instance, 20 included support hours, full Open edX feature set with our operational layer on top. Built for universities, regulated industries, and large training operations that need institutional features (cohorts, proctoring, multi-tenant, xAPI, certificates) and the credibility of running the same platform as MIT and Harvard.
| Your situation | Recommended path |
|---|---|
| Hobby site or course business <100 learners | Stay on LearnDash through 2026; plan Tutor LMS or Cubite LMS migration in 2027 |
| Course business, 100–5,000 learners, want to leave WP | Cubite LMS SaaS |
| Course business, 100–5,000 learners, must stay in WP | Tutor LMS (best 2026 WP migration target) |
| Mid-market training company, regulated content | Managed Open edX (Cubite) |
| University, hybrid programs, ≥5,000 learners | Managed Open edX (Cubite) or self-hosted Open edX with internal devops |
| Multi-tenant platform (you resell LMS to others) | Managed Open edX(Cubite) - multi-tenant is native |
The five most-asked questions about the LearnDash dissolution are answered inline in their respective sections above (the dissolution itself, Open edX as an alternative, the migration mechanics, and the best replacement). Three more that come up in every consultation:
The 90-second version of this guide:
LearnDash being effectively over is bad news if you're attached to the product. It's good news if it's the kick you needed to move to a platform built for what your LMS is actually doing in 2026.
Looking to learn more about and ? These related blog articles explore complementary topics, techniques, and strategies that can help you master LearnDash Alternatives 2026: Migration Guide After StellarWP.