LearnDash Risk Assessment

The first thing to notice is that LearnDash did not vanish. It is still one of the four surviving flagship products. That matters because this is not a service shutdown. The concern is the operating context. Liquid Web dissolved the StellarWP umbrella and pushed several brands into a smaller portfolio. Product sites redirected, users reported confusion around accounts and licenses, and the public response was not warm. For TCEA, the question is not whether LearnDash functions today. It does. The question is whether the platform is still a safe multi-year bet without a backup plan.

This slide names the core issue. LearnDash is still a WordPress LMS plugin, and the plugin is not the immediate failure point. The risk sits around the vendor. Consolidation can be reasonable from a business perspective, but it also changes the support model, product roadmap, and renewal conversation. For TCEA, that matters because the platform is tied to paid courses, district sales, subscriptions, and learner access windows. A small pricing change or support slowdown is not just annoying. It affects planning, budgeting, and the learner experience.

This is the bottom line of the brief. I would not recommend an emergency migration simply because the vendor changed its packaging. Emergency migrations usually create their own problems. At the same time, I would not keep renewing LearnDash without a written exit option. The product is self-hosted, which gives TCEA breathing room. Courses will not suddenly disappear because a portal changed. That breathing room should be used to document what TCEA has, test a serious replacement, and decide before the renewal clock creates pressure.

The risk map gives TCEA a checklist rather than a vague worry. Vendor stability is the largest concern because it affects every other category. Pricing and packaging come next because TCEA needs specific commerce features, not just course pages. Lock-in matters because absorbed tools can quietly turn into higher-tier requirements. Operations matter because license and billing confusion can interrupt normal maintenance. The April 2027 security-patch date is also important. Any dependency on retired tools should be found early, while there is still time to replace or budget for it.

The alternatives split into two groups. The first group keeps TCEA in WordPress. MemberPress, WP Courseware, TutorLMS, and LifterLMS all keep the site model familiar, but they differ on commerce, memberships, and migration effort. The second group exits WordPress entirely. Thinkific, Canvas, Google Classroom, and Moodle reduce plugin risk, but they also force a heavier rebuild and a different operating model. For TCEA’s current model, MemberPress is the closest functional match because the need is not just courses. It is courses plus sales, subscriptions, and group access.

This is the migration reality that should stay visible. Course content is usually the easier part. Lessons, topics, quizzes, and media can often be exported or rebuilt with reasonable effort. Learner history is harder. TCEA has more than content to protect. It has learner accounts, enrollments, completions, progress, and access rules. Any pilot should include real courses and real-looking records, not a clean demo course with three sample users. The project plan should budget time to verify learner data, because that is where migrations often look fine until someone tries to prove completion.

This slide reduces the platform decision to four functional requirements. TCEA needs to sell courses to individuals online. It also needs subscription options. More importantly, it needs district bulk sales where a parent account can manage a group of teacher seats with centralized billing. The trickiest requirement is rolling access expiration. A learner who enrolls in March should lose access the following March, not on a shared district calendar date. MemberPress maps well to this model because membership expiration is tied to each user’s purchase date, and Corporate Accounts handles the district parent-and-subaccount pattern.

The important correction here is the plan level. If TCEA only needed individual course sales, Growth might be enough. It is not enough for the district model. Corporate Accounts is the feature that lets one district buy a parent account, assign sub-accounts, and manage teachers at scale. That feature sits in Scale. The right budget number is also the renewal price, not the first-year promotion. Around one thousand dollars a year is still a modest annual increase if it replaces LearnDash plus separate membership and bulk-licensing add-ons, but it needs to be planned honestly.

This slide separates the license conversation from the real project cost. The license itself is per website, not per learner. TCEA could have five thousand learners or fifty thousand learners and the plugin license does not change because of that count. What changes the tier is the commerce feature set: Corporate Accounts, zero MemberPress transaction fee, gifting, gradebook, order bumps, and Authorize.net. Payment processor fees still apply, of course. The other cost is migration labor. With more than fifty courses and thousands of user records, that should be treated as a real project, not a weekend export.

This is the honest limit. MemberPress is a strong fit for commerce and course access, but it is not trying to be a district student-information system. If TCEA’s future needs include district SSO, automated rostering, or grade passback into school systems, those requirements need a pilot before a full migration decision. That does not make MemberPress the wrong choice today. It means the pilot should test the real workflow TCEA has now and the likely workflow TCEA may need later. If the job turns into school-system integration, Canvas or Moodle becomes the better fallback.

This is the practical path. In the first thirty days, stabilize what already exists. Confirm portal access, renewal dates, billing, and license keys. In the next thirty days, inventory everything TCEA depends on. From sixty to ninety days, run the MemberPress Scale pilot against actual workflows: a course that expires one year after purchase, an individual subscription, and a Corporate Account for a sample district. From ninety to one hundred twenty days, decide. Staying is acceptable if LearnDash support holds and the cost makes sense. Leaving is acceptable if the risk or bundling is no longer worth it.

The decision gate keeps this from becoming a vague preference debate. Staying with LearnDash is defensible if the operational pieces stabilize, support remains responsive, and the needed features are still available at a price TCEA can defend. Moving is defensible if the bundled pricing or vendor risk starts to outweigh the cost of migration. Either way, the MemberPress pilot is useful. If TCEA stays, the pilot gives us a tested exit. If TCEA leaves, the pilot gives us the first migration path instead of a theoretical replacement.

I would close with this distinction. TCEA does not need to flee LearnDash. The product still works, and a rushed migration could create unnecessary disruption. But TCEA should not drift into another renewal cycle without leverage. The immediate work is simple: stabilize the current account, inventory dependencies, run a serious MemberPress Scale pilot, and document how content and learner records would move. That gives TCEA a choice. If LearnDash remains the right answer, stay. If it stops being the right answer, leave on TCEA’s timeline rather than the vendor’s.