| Three founders we work with sent us the same screenshot last week. LearnDash.com is redirecting to liquidweb.com. Different messages, same question underneath: “Should I be worried?” We at WisdmLabs have been around LearnDash since 2013. Long enough that StellarWP acquired our own LearnDash add-ons in 2024 (press release). We have a closer view than most of what just happened. This piece is the answer we sent them, written down. |
If you’re reading this because of the LearnDash news from April and May 2026, you know the surface story.
The StellarWP brand was wound down. LearnDash.com now redirects. There were team changes and a corporate restructuring. Founders left. Headlines used words like “collapse” and “RIP”
None of that is wrong. It also isn’t the full picture, and it isn’t the picture that matters most if you actually run a course business on LearnDash today.
First, the short version of the LearnDash news (so you can stop refreshing X)
Here is what actually happened, stripped of drama.
On April 22, 2026, the company that has owned LearnDash since 2021, Liquid Web, published an announcement consolidating its WordPress software portfolio into four core products: Kadence, LearnDash, The Events Calendar, and Give.
The StellarWP brand that used to sit above these products is gone. LearnDash itself survived as one of those four core products.
LearnDash is not being discontinued. It is one of the products Liquid Web is keeping and continuing to invest in. The company has explicitly said existing customers keep their current plan, pricing, and features.
Switching to a new plan is optional, not a forced migration. Your license keys still work. Your data stays on your own site. The plugin still runs on whatever hosting you use.
What did change is the corporate structure around the plugin, the website you used to visit, and the customer portal. The team behind the products has been reorganised as part of the consolidation. The brand identity is different. Some smaller products in the old StellarWP family (SolidWP, Iconic, Restrict Content Pro, and MemberDash) are no longer sold as standalone products and have been folded into Kadence or LearnDash.
That’s the news. Everything else here is about helping you tell the difference between what is confirmed, what is genuinely unknown, and when this is actually a thing you need to do something about.
The five-year timeline that explains how we got here
A lot of the uncertainty in the WordPress community right now is not about the consolidation announcement itself. It’s about the year of context that came before it. To make sense of what’s happening, you need that context laid out cleanly.
September 2021. Liquid Web acquired LearnDash from co-founder Justin Ferriman and placed it under the StellarWP brand alongside SolidWP, The Events Calendar, GiveWP, Restrict Content Pro, and Kadence WP. The press release promised the LearnDash team would operate independently and customers would see no change in service.
May 2024. StellarWP acquired the LearnDash add-ons originally built by WisdmLabs. That’s us. We mention it because it’s relevant to why you’re reading this piece. We’ve worked alongside this product for over a decade, including time while it was part of the StellarWP family.
October 2025. Nexcess, Liquid Web’s managed hosting brand, was fully absorbed into Liquid Web and lost its independent identity. This was the first signal that the parent company was moving from a “house of brands” approach to consolidation.
November 2025. Liquid Web and StellarWP went through a round of internal restructuring. For long-time observers of the ecosystem, this was the moment the structural change became visible.
Late 2025. A series of leadership transitions followed. Devin Walker, GiveWP’s other co-founder, wrote publicly that “private equity often takes a hard edge, putting profits over people and disregarding morale.”
April 22, 2026. The consolidation announcement we already covered.
May 12, 2026. The product websites (learndash.com, kadencewp.com, givewp.com) began redirecting to Liquid Web’s main domain. This is the moment most users found out something had changed. Founders posted publicly.
Justin Ferriman tweeted, “RIP to the LearnDash brand 🚦 — the site now redirects to a lander on LiquidWeb.” Community reaction across Post Status Slack and WordPress Twitter was sharp.
Why this timeline matters more than the news itself
The leadership transitions and team restructuring across 2025 are doing more emotional work in the community than the rebrand itself. If all that happened on April 22 was a new website and tier names, the WordPress world would have shrugged.
What’s generating real concern is the pattern in the months leading up to it. Multiple rounds of internal change. The transition of people who had built deep product knowledge. The visible departure of founders who built these tools.
This is worth separating from whether your LearnDash site is at risk right now. A leaner restructured team, and a fresh corporate structure are not, by themselves, a product failure. They are signals to watch.
And what about the LearnDash add-ons we all rely on?
This is one of the most common questions we’ve received over the last few weeks, and it deserves its own short answer.
A lot of LearnDash sites in the real world don’t run on the core plugin alone; they run on a stack of premium add-ons (Instructor Role, Group Registration, Reports for LearnDash, Ratings & Reviews, Content Cloner, ProPanel, the WisdmLabs-built add-ons that joined LearnDash in 2024, and others).
If the parent company just consolidated its software portfolio, the natural next question is: what happens to all of those add-ons?
The short, honest answer: based on Liquid Web’s own published guidance, the official LearnDash add-ons that previously sat under separate brands are being brought under the unified LearnDash umbrella.
Existing add-on customers can continue using them as normal, functionality has not changed, and support will continue (transitioning to the LearnDash help desk and customer account portal as the migration completes).
There are no immediate feature changes announced, and refund/terms coverage moves under the LearnDash Terms and Conditions once the transfer is finalised.
That is genuinely all that has been confirmed in writing so far.
What hasn’t been confirmed is the longer-term roadmap for each add-on; which ones will keep shipping major updates, which will be folded directly into LearnDash core, and which will receive only maintenance releases.
Liquid Web has not published that level of detail per add-on, and we are not going to speculate beyond what they’ve said.
If you depend on a specific add-on for your business, the most useful thing you can do today is exactly the same thing we recommend for the core plugin: verify it shows up correctly in your new portal, screenshot your active licenses, and watch the changelog for the next two release cycles.
Confirmed facts vs. open questions: the table founders actually need
This is the table missing from every other piece written about this story. Most coverage right now blends what’s confirmed with what’s being speculated about, then ties it up with a recommendation to switch to whatever the publisher happens to sell.
That’s not useful to you if you’re trying to make a real decision.
Here’s the clean version.
| What is confirmed | What is genuinely unknown |
| LearnDash is one of four products Liquid Web is keeping and selling under the new structure. | How aggressively will the product roadmap be invested in over the next 12 to 24 months? |
| Existing customers keep current plan, pricing, features, and license keys until they choose otherwise. | What support response times will look like with a leaner team across multiple products. |
| The plugin remains self-hosted on any hosting provider you choose. | How pricing will shift on the new tiered plans for customers whose current subscription eventually lapses. |
| Your data, courses, students, and progress stay on your own site. This is a licensing change, not a data migration. | Whether the new AI features and MemberDash integration will be developed as deeply as standalone teams might have built them. |
| Existing license keys remain valid and have been moved to a new unified portal at software.liquidweb.com. | How long Liquid Web’s commitment to LearnDash as a “core product” remains stable through any future ownership changes at parent company CloudOne Digital. |
| MemberDash is no longer sold standalone; its features have been folded into LearnDash. | Whether founder-led culture and community engagement at WordCamps can be rebuilt under a hosting-company brand. |
| Critical security patches for retiring features continue through April 2027. | How the consolidation will affect third-party integrations and add-ons in the broader LearnDash ecosystem. |
| Self-hosted flexibility is unchanged. You are not being forced to host with Liquid Web or Nexcess. | What the renewal experience will look like for customers when their current legacy plan expires. |
What is confirmed (and verifiable from primary sources)
Everything in the left column traces back to Liquid Web’s own announcement.
The company stated that switching is optional, current pricing and tools remain the same unless you upgrade, and existing license keys still work.
There’s a public statement from inside the company worth reading directly. Jack Kitterhing, now VP of Product at Nexcess, addressed community concern in Post Status Slack: “The products aren’t dying, they aren’t dead, and we’re making active investments in them.”
You don’t have to take that at face value. One prominent WordPress voice, Joost de Valk, pushed back: “‘Check back in 1 to 2 years’ cuts both ways, and the burden of proof is on the side making the change.” But it is the company’s actual position, on record.
What is genuinely unknown (and where opinions are filling the gap)
The right column is harder to talk about honestly. The open questions are real, and they’re not the same as predictions.
Nobody, including us, knows how the LearnDash roadmap will look in 18 months. Nobody knows whether support quality will hold up under a leaner structure.
Nobody knows whether the new AI course-builder and quiz tools will get the kind of careful product attention StellarWP-era LearnDash got. Anyone telling you the answers today is selling you something.
There’s also a more measured industry view worth registering. WooCommerce expert Rodolfo Melogli wrote that “it’s far too early to declare this a failure or the ‘death’ of these brands.“
Liquid Web made a big strategic bet.” Maybe it works. Maybe it doesn’t. That’s the honest range right now.
What this LearnDash update actually changes for your site today
For most of you reading this, the practical answer is: very little, today. But there are three distinct situations, and the right answer depends on which one applies to you.
If your subscription is active and current
Nothing breaks. Your license key still works. Your plugin still updates. Your courses, lessons, quizzes, and student records sit exactly where they were yesterday. You’ll see your account in the new portal at software.liquidweb.com, and old portal links redirect automatically.
Your main action item this month: log in to the new portal once and confirm your billing details and license keys are visible. There were reported login issues and missing invoices during the migration, which Liquid Web has been working through. Verifying now means you’ll spot any glitches while support is responsive.
If your subscription is close to renewal or has recently lapsed
This is where the change starts to matter. If your current subscription lapses, you’ll need to purchase one of the new software plans. Pick one that has the same features you’d like to keep. The new structure is three tiers: Essentials, Pro, and Elite.
Before your next renewal date, check which features you actually use today versus which tier they live in under the new plan. If you’ve been on a legacy bundle, the equivalent feature set may sit at a different price point than you expect. We’ve written about the real cost of building courses with LearnDash, and the principle still applies.
If you bought lifetime or legacy add-on licenses
Lifetime customers are being grandfathered. Jack Kitterhing confirmed publicly: “Lifetime customers retain everything they already had. If you owned it you still own it today. Every single customer is being grandfathered in.”
That said, the rollout was rough for some lifetime holders. Login issues and missing invoices affected customers during the portal migration. If you bought a lifetime deal, especially for products folded into Kadence or LearnDash (like MemberDash or Restrict Content Pro), log in to the new portal and verify your access shows up correctly. Screenshot what you see.
For founders running $1M+ ARR on LearnDash: a different conversation
If a meaningful slice of your revenue runs through a LearnDash-powered course or training business, the rest of the internet’s coverage of this story is built for the wrong reader. You are not panic-buying a new platform on a Friday afternoon. You are evaluating platform risk the way you’d evaluate any vendor your business depends on.
Here’s the shift in framing that helps. This isn’t an emergency. It’s an unscheduled vendor review. The kind your board would expect if any critical software dependency in your stack just went through a corporate restructuring, a leadership change, and a brand consolidation in six months.
You don’t change platforms reactively. You build a clearer picture of your platform risk, then make a decision when the data supports one.
Three questions to put in front of your tech lead this quarter
These are the three we’d ask if we were sitting in your team’s quarterly tech review. None of them require you to commit to anything. All three give you the visibility a founder running a real business should have.
1. What is our actual replacement cost? Not “what does LearnDash cost?” What would it cost in engineering time, content rebuild, student communication, payment-flow rewiring, integration redo, SEO preservation, and revenue at risk to move our entire course business off LearnDash in 90 days if we had to?
This is not a project plan. It’s a number on a page. If your tech lead can’t produce it in a week, you have less visibility into your platform risk than you should.
2. Where are we technically locked in, and where are we portable? Course content is usually portable. Student records and progress data are usually portable. The hard-to-migrate pieces are the custom logic: your quiz workflows, certificate engines, drip schedules, group enrollments, CRM connections, and integrations built around the core plugin.
Map those. The more your business runs on customisation, the higher your switching cost. This is also why our team spends so much time on LearnDash customisation work. Most serious course businesses run a customised version of LearnDash, not vanilla.
3. What’s our roadmap dependency? Are there specific features on the LearnDash roadmap you’re counting on, for compliance, a new product line, or an integration you promised a customer? Write them down. Those are the canaries in your specific coal mine over the next 12 months.
What an “exit-ready” position looks like (without actually exiting)
The smart move for most $1M+ ARR founders right now isn’t to migrate. It’s to put your business in a position where you could migrate cleanly if you ever needed to, then go back to running your business. The two aren’t the same.
Being exit-ready means a few specific things. Current backups you’ve actually tested. Your course content is documented in a format that isn’t trapped inside one plugin’s database. A clear list of which integrations would need to be rebuilt. A rough scope for what a migration would involve.
That’s a quarter of work, max. It costs you nothing in disruption. It puts you in a position where any future decision is made on your timeline, not on a vendor’s.
We’ve helped course businesses navigate platform changes in both directions: Onto LearnDash, off LearnDash, and even within the WordPress ecosystem. One clean example is our case study on a smooth subscription platform transition for a growing digital learning business, where the goal was to protect active subscribers and billing continuity throughout the move.
The pattern that works for founder-led businesses isn’t a frantic rebuild. It’s a quiet preparation, so that if and when a decision becomes warranted, you execute on your terms. If you do reach the point where structured platform-migration support is genuinely warranted, the work will have a defined shape. Until then, calm preparation beats a sudden move.
The decision framework: when does action actually become warranted?
Here’s a clean way to think about where you stand right now and what would actually move you between states. There are three of them.
State 1: Hold position (where most readers are right now)
You’re in Hold position if all of the following are true:
• Your LearnDash subscription is active, or your lifetime access is showing correctly in the new portal.
• Your site works. Your students aren’t reporting issues. Your course delivery is functioning normally.
• You don’t have a hard-deadline roadmap dependency in the next 6 months that requires a feature LearnDash hasn’t shipped yet.
• You haven’t had a support issue go unresolved in a way that’s hurting your business.
If all four are true, the correct action is no action. Stay informed, watch the signals listed below, and run your business. Platform moves made under uncertainty almost always cost more than platform moves made when the situation is clearer.
State 2: Watch list (specific signals to track over 12 months)
You move to the Watch position when any of the following start to happen. None of these requires action by itself. They are the things that, if they accumulate, change the picture.
• Update cadence slows visibly. LearnDash currently ships regular updates. Track whether that continues. A gap of 3+ months between meaningful releases would be a meaningful signal.
• Support response times degrade for issues that matter to your business. One slow ticket is a bad week. A pattern across two or three months is data.
• Documentation stops being maintained. Outdated docs are often the first sign of a product team stretched thin.
• Pricing changes on the new tiers in ways that meaningfully change your renewal economics. Watch your next renewal cycle carefully.
• Key remaining team members continue to transition out. Founders have already moved on. The question is whether the next layer of senior engineers and product staff will stay.
• A specific feature you depend on gets quietly deprecated. This is the one most likely to surprise you. Check the changelog on every release.
If you’re in Watch position, the right action is to do the “exit-ready” preparation we described above. Not migrate. Prepare.
State 3: Action warranted (the threshold for actually moving)
You move to Action only when one of these is true:
• A confirmed, business-critical feature gap has emerged, and there’s a public signal that it’s not going to be addressed.
• Support quality has degraded to the point that it’s directly costing you customer trust or revenue.
• Pricing on your renewal is materially worse than the comparable alternatives in a way your business cannot absorb.
• An independent platform decision (a major rewrite, a new business model, a compliance requirement) would have triggered a platform review anyway, and this is the moment to combine it with one.
If you’re in the Action position, that’s a real project, with real scope, real cost, and real risk. It’s worth doing right. It’s worth not doing reactively.
The decision framework artifact below lets you walk through your own situation and see which state you’re actually in. Most of you will land in Hold. Some will land in Watch. A small minority will land in Action.
The honest perspective: why this article doesn’t end with “switch to XYZ platform.”
Almost every other piece written about the LearnDash news in the last three weeks ends with a pitch. Switch to one platform. Switch to another. The publishers all happen to sell the thing they’re recommending.
We at WisdmLabs aren’t going to pretend we don’t have skin in the game. We do. Our business depends on healthy, working WordPress and LearnDash sites, and on helping people move between platforms when that’s the right call.
The honest version: we work with LearnDash. We build add-ons for it. We’ve spent over a decade in this ecosystem. We also handle migrations off LearnDash when a customer’s situation calls for it. We have no commercial reason to push you toward an exit you don’t need, and no reason to hide that exits are sometimes the right move.
What we do have is a strong view that the current internet conversation about this LearnDash update isn’t serving the people who actually have to make decisions. It’s loud, reactive, and full of pitch decks dressed up as analysis. The most useful thing we can do is publish the version of this story that doesn’t end with a coupon code.
If you want a second pair of eyes on your specific setup, that’s a conversation we’re happy to have. If the framework above answered your question, you don’t need us. Get back to teaching.
Frequently asked questions
Is LearnDash being discontinued?
No. LearnDash is one of four core products Liquid Web is keeping and continuing to invest in. The product, the plugin, and the underlying functionality all continue. What changed is the brand structure around the plugin and the team size behind it. The plugin is still being shipped, supported, and updated.
Will my LearnDash license still work after my subscription renews?
Your existing license remains valid as long as your current subscription stays active. If your subscription lapses, you’ll need to purchase one of the new software plans. Pick one that includes the features you want to keep, because the new tier structure distributes features differently than the older bundles.
What happens to MemberDash if I was using it as a standalone plugin?
MemberDash is no longer sold standalone. Its features have been folded into LearnDash. If you’re an existing MemberDash customer, your current plan and features continue. If you upgrade or your subscription lapses, the equivalent features live inside the new LearnDash plans.
Should I migrate away from LearnDash now?
For most of you, no. The decision framework in this piece is designed to help you avoid a reactive platform move that costs more than it saves.
Counterintuitively, a lot of businesses are still migrating to LearnDash because the integration ecosystem and data ownership model hold up well in 2026. We’ve written a separate piece on how that migration works if you’re considering it.
Is the LearnDash plugin still receiving updates and security patches?
Yes. The core LearnDash plugin continues to be developed and patched. For features and add-ons specifically being retired, Liquid Web has committed to critical security patches through April 2027. That sunset applies to retiring tools, not to LearnDash itself.
| If this piece helped, your next step depends on which state you landed in. Most of you are in the Hold position. Close the tab and go build courses. If you’re in Watch position, the exit-ready preparation we described is a quarter of quiet work that gives you optionality without disruption. |
For founders running $1M+ ARR on LearnDash who want a structured second opinion on where their business actually sits, here’s how we at WisdmLabs work.
We can get on a free 30-minute call where we look at your current setup, your customisation, your renewal timeline, and your business stakes. In this call, you’d know whether you’re in a Hold, Watch, or Act position based on your actual specifics.
If the answer is “stay put,” we say so. If the answer is “prepare for optionality,” we scope what that looks like. If the answer is “this is the right moment to move,” we walk you through what a structured WordPress migration process involves before you commit to anything.
The work we’ve done on large-scale eLearning transitions, migrating a platform with 26,000 students without disrupting their billing or progress, is the kind of careful execution you should expect from anyone you’d trust with this decision. Ready when you are!
