# LearnDash to Mobile App: Move Courses Without Losing Access

> Move LearnDash courses and customers into your own iPhone, Android and web app while WooCommerce keeps selling, so nobody buys twice or loses a course.

*Source: [https://hlt3.studio/blog/learndash-to-app-migration/](https://hlt3.studio/blog/learndash-to-app-migration/)*

*By Vaclav Skarka · Published 2026-11-16*

**Short answer:** You can move a LearnDash course business into your own iPhone, Android and web app without asking anyone to buy again. Move the courses, then the users, enrollments and group access, keeping every old WordPress ID so links, orders and progress still point at the right course. Customers sign in with the email they already use and find their courses waiting. Keep WordPress and WooCommerce selling until the app grants exactly the same access, and keep a way back.

Content is the part you plan for. Access is the part customers notice: someone who paid for a course and finds it locked in your new app is likely to contact support before watching a single lesson.

I did this for ProFinity, a training and community app for aesthetics clinicians: in July 2026 I brought its LearnDash customers into the app with the courses they had bought, and WooCommerce shop purchases unlock courses in the app ([ProFinity case study](https://hlt3.studio/case-studies/profinity/)). The app's public release notes record it: version 1.8.5 of 16 July 2026 added "support for migrated LearnDash course access" ([App Store version history](https://apps.apple.com/app/id6753218245)).

> **Moving off LearnDash?** [Tell me how your customers buy courses today and whether your app exists yet](https://hlt3.studio/contact/?project=other). I reply with what would move, what would not, and how I would keep everyone's access intact. I build the app as well.

## Can I turn my LearnDash site into a mobile app?

Yes, in two ways: wrap your existing WordPress site in an app, or move courses and customer access into an iPhone, Android and web app with its own backend (the server and database behind your app). A wrapper is quicker, but Apple expects "features, content, and UI that elevate it beyond a repackaged website" ([guideline 4.2](https://developer.apple.com/app-store/review/guidelines/#minimum-functionality)). Your own app makes sense when you want to design the course experience and features yourself, keep data in your own backend, or serve buyers from several shops in one app. This guide covers the move.

## What moves from LearnDash to a mobile app, and what doesn't?

Courses, lessons, topics, quizzes, users, enrollments, group access and progress move from LearnDash to an app; page-builder layouts, shortcodes, add-on plugin features, payment history and readable passwords don't. LearnDash keeps course content as WordPress posts, and its [REST API (v2)](https://developers.learndash.com/learndash-rest-api-ldlms-v2/) can read all of it.

What usually moves well:

- **Courses and their structure.** The course steps endpoint returns "the hierarchy and ordering of lessons, topics, and quizzes".
- **Lessons, topics, quizzes and questions.** Quiz settings such as pass marks need mapping to what your app's quizzes support.
- **Media:** files from the WordPress media library and video from your video host. Check that the host allows playback inside the app, not only on your website.
- **Users:** email, name and registration date.
- **Enrollments and group access.** LearnDash's [groups documentation](https://docs.nexcess.com/software/learndash/groups/) says anyone in a group "will be automatically enrolled into the course(s)", so group access must move with direct enrollments.
- **Progress, if you want it:** per course, step and quiz.

What usually doesn't move as it is:

- **Page-builder layouts, theme styling and shortcodes** inside lessons, such as Elementor sections or a `[video]` shortcode. The app needs its own content blocks, so plan to review every lesson built this way.
- **Add-on plugin features** such as points or forums: decide one by one.
- **Payment history** stays in WooCommerce or your payment provider. The app only needs who has access to what, and until when.
- **Readable passwords.** WordPress never stored them (see below).

Want this list for your own site? [Tell me how your customers buy courses today](https://hlt3.studio/contact/?project=other). I reply with what would move and what would not.

Before you touch anything, take a dated backup with LearnDash's Import/Export tool (LearnDash LMS > Settings > Advanced > Import/Export). It exports course content, groups, users and more, and LearnDash's [transfer guide](https://docs.nexcess.com/software/learndash/transfer-courses/) strongly recommends practising on a development site first.

This part is for whoever builds your backend. A script can read these endpoints with a WordPress [Application Password](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/) over HTTPS (built in since WordPress 5.6):

~~~text
GET /wp-json/ldlms/v2/sfwd-courses
GET /wp-json/ldlms/v2/sfwd-courses/{id}/steps
GET /wp-json/ldlms/v2/users/{id}/courses
GET /wp-json/ldlms/v2/users/{id}/groups
GET /wp-json/ldlms/v2/groups/{id}/courses
GET /wp-json/ldlms/v2/users/{id}/course-progress
~~~

Emails come from the [WordPress users endpoint](https://developer.wordpress.org/rest-api/reference/users/) (`edit` context only) or [`wp user list`](https://developer.wordpress.org/cli/commands/user/list/).

## How do you keep old course links and purchases working?

For you this means two things: links in old emails still open the right lesson, in the app when it is installed, and every past purchase still points at the right course. The five steps are for whoever builds your backend.

Keep every WordPress ID on the matching app record, give every old URL a destination, let links open the app, and map each WooCommerce product to the courses it unlocks. Enrollments, products and progress all point at WordPress IDs (LearnDash's [transfer guide](https://docs.nexcess.com/software/learndash/transfer-courses/) notes that stored progress must match the post IDs of courses, lessons, topics and quizzes), so changed IDs quietly break access.

1. **Keep the old ID on every record.** Store the WordPress ID of each course, lesson, topic and quiz in the app (a `legacy_id` field). Never renumber or reuse it.
2. **Keep the slugs.** By default LearnDash uses URLs such as `/courses/course-name/` and `/lessons/lesson-name/`, or nests lessons under the course when Nested URLs is on ([LearnDash permalinks](https://docs.nexcess.com/software/learndash/permalinks/)). Write down which pattern your site uses.
3. **Give every old URL a destination:** the same page on your new web app, or a permanent redirect to it.
4. **Make links open the app.** With universal links on iPhone and [App Links](https://developer.android.com/training/app-links) on Android, a link to your website opens the app when it is installed; otherwise "the system opens the URL in their default web browser" ([Apple](https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content)). Links in old emails keep working for everyone.
5. **Keep a product map.** List which courses or groups each WooCommerce product unlocks, by legacy ID.

## How do customers get access on day one?

Import each customer's direct enrollments, group access and dates, match them by email, and let anyone who bought with another email claim access with a one-time code; customers then only need to install the app.

### Match accounts by email

Trim and lowercase every email before matching. Then list the conflicts: accounts that differ only by letter case, buyers whose checkout email differs from their account email, and staff or test accounts. Resolve them before launch, not in the support inbox.

Keep the original enrollment dates: LearnDash's [course access expiration](https://docs.nexcess.com/software/learndash/course-enrollment-mode/) "limits access based on the learner's enrollment date", so new dates would restart access periods on launch day.

### Give people a way to claim access

- **Same email:** access is waiting and attaches at first sign-in.
- **Different email:** the customer enters the email they bought with, receives a one-time code there, and the access moves to their signed-in account. Log every claim.
- **Support fallback:** an admin screen that maps a purchase to an account, with an audit trail.

In ProFinity, buyers claim a purchase with a link and a six-digit code sent by email, no password needed, and the team maps products to courses itself, with a history of every change ([ProFinity case study](https://hlt3.studio/case-studies/profinity/)).

### Decide what happens to passwords

You have two choices. Customers keep their old password, or they sign in with a one-time code sent to their email and never need the old one. When many customers sign in rarely, I lean towards the email code: nobody has to remember a password set years ago.

For whoever builds your backend:

- **Keep existing sign-in working.** WordPress stores one-way hashes (scrambled versions), not passwords. Since WordPress 6.8, new hashes use bcrypt, older phpass hashes stay valid, and a password is rehashed with bcrypt at its owner's next login ([WordPress core announcement](https://make.wordpress.org/core/2025/02/17/wordpress-6-8-will-use-bcrypt-for-password-hashing/)), so one export can hold hashes in several formats. The new sign-in checks the password once against the old WordPress hash, using the same rules as WordPress's own [`wp_check_password()`](https://developer.wordpress.org/reference/functions/wp_check_password/), then stores a fresh hash: the same check-once pattern as [moving Firebase users to Supabase without password resets](https://hlt3.studio/blog/firebase-to-supabase-migration/). Treat exported hashes like any other secret, and throttle the check (limit repeated attempts).
- **Use a passwordless claim.** Customers sign in with a one-time code or link sent to their email, and set a password later if they want one.

## How do you keep WordPress and WooCommerce selling during the move?

Keep selling through WooCommerce, and leave LearnDash's [WooCommerce integration](https://docs.nexcess.com/software/learndash/setting-up-woocommerce-integration/) granting access from each order's status (its Enrollment Status settings). Change only which system grants access, phase by phase:

1. **Before launch:** WordPress. The app copies users and enrollments from it.
2. **At the switch:** connect [WooCommerce order webhooks](https://hlt3.studio/blog/woocommerce-unlock-in-app/) (automatic messages about new and changed orders), then run a final import of everything changed since the full import. Orders placed in between arrive by webhook, so no sales freeze is needed.
3. **After launch:** grant access from webhooks through the product map, and run a nightly comparison with LearnDash that alerts on any difference.

WooCommerce [automatically disables a webhook](https://woocommerce.com/document/webhooks/) "after more than five consecutive delivery failures", so alert on that too; the nightly comparison catches what it missed.

Mirror removals as well as grants. [By default](https://docs.nexcess.com/software/learndash/setting-up-woocommerce-integration/), the integration removes course or group access as soon as a WooCommerce subscription expires; make the app do the same, or decide on purpose that it won't. Before the final import, run "Give LearnDash Students Retroactive Access" (WooCommerce > Status > Tools) on a staging copy first: it updates enrollments to match your Enrollment Status settings, which can remove access as well as grant it. Review the differences, then run it live.

In-app selling is a separate question. Google Play allows an app where customers sign in to courses bought elsewhere, and Apple usually expects the same courses to be for sale as in-app purchases too. See [what the two stores allow](https://hlt3.studio/blog/app-unlock-courses-bought-on-website/), as of November 2026.

## How do you test the migration with real accounts?

Test on a staging copy only your team can open.

1. **Pick test customers from real patterns:** a direct buyer, a group-only member, a free-course learner, expired access, a refunded order, an active subscription, a changed email, someone halfway through a course, a group leader and an admin.
2. **Compare access for every user:** courses granted in LearnDash against courses granted in the app, aiming for zero unexplained differences.
3. **Sign in on real devices:** an iPhone, an Android phone and a desktop browser.
4. **Click old course and lesson links** from your emails.
5. **Buy a course on staging,** watch access appear in the app, then refund it and watch it go.

## How do you roll back a LearnDash migration?

Keep WordPress, LearnDash and the WooCommerce integration running unchanged, with redirects switchable in one place, so you can send customers back at once. Agree the triggers before launch day, for example a paying customer locked out with no same-day fix, or access differences nobody can explain.

When in doubt, grant access and log it: a lesson opened by mistake is cheaper to fix than a paying customer locked out.

## LearnDash to app migration checklist

**1. Decide on paper**

- ID map: WordPress IDs kept on every record, and a destination for every old URL.
- Product map from WooCommerce products to courses and groups.
- Claim flow with one-time email codes and an audited admin mapping.
- Password approach: check old hashes once, or passwordless.
- Progress: move it, or note why not.
- Rollback triggers agreed in writing.

**2. Back up and copy**

- Dated Import/Export backup and a full site backup.
- Course content imported in order, with WordPress IDs.
- Media re-hosted or confirmed playable in the app.
- Users imported with normalised emails; conflicts resolved.
- Enrollments, group access, dates and expiries imported.

**3. Test on staging**

- All test customers pass on iPhone, Android and the web.
- Old links open the right page, or the app.
- Refunds, cancellations and expiries remove access.

**4. Switch and watch**

- Webhooks connected before the final import, alerting if one is disabled.
- Final import just before the announcement.
- Customer email: what changes, how to sign in, where to get help.
- Nightly access comparison, alerting on differences.

## Common questions

### What does it cost to move a LearnDash course business into an app?

If you do not have an app yet, you get a fixed price in writing for the app and the move of your courses and customers before any work starts. If your app is already live, you get a fixed price in writing too.

### Do customers have to buy their courses again after moving from LearnDash?

No. Their direct enrollments, group access and dates are imported and matched to their account by email; anyone who bought with another email claims access with a one-time code.

### Can I keep my LearnDash site after the app launches?

Yes, and you should during the transition. WordPress and WooCommerce keep selling and granting access while the app reads it. Retire LearnDash once the nightly access comparison stays clean and access questions to support have stopped.

### Should I move course progress from LearnDash?

It's optional; LearnDash's REST API exposes progress per course, step and quiz. Move it when customers are partway through long courses or certificates depend on it; otherwise starting fresh is reasonable.

### Does moving customers into an app change my privacy paperwork?

It can: your app's backend and its providers become new places that store customer records. Check your privacy notice and your data processing agreements before you copy anyone, under the [EU GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj), the [UK GDPR](https://www.legislation.gov.uk/eur/2016/679/contents), Switzerland's [FADP](https://www.fedlex.admin.ch/eli/cc/2022/491/en) or, in the US, [HIPAA](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html). Your counsel decides what applies.

## Need help with this?

If you're moving a LearnDash course business into an app, I build the app, the course import and the customer move. For [ProFinity](https://hlt3.studio/case-studies/profinity/) I brought the LearnDash customers into the app with the courses they had bought, and purchases in its WooCommerce shop unlock courses in the app.

[Tell me how your customers buy courses today](https://hlt3.studio/contact/?project=other). I reply with what would move, what would not, and how I would keep everyone's access intact, and you get a fixed price in writing before any work starts. Talk to me before you export anything: the ID map, the claim flow and the rollback triggers are easy to design up front and hard to repair after launch.

Related: [unlocking courses from paid WooCommerce orders](https://hlt3.studio/blog/woocommerce-unlock-in-app/), [moving GoHighLevel customers into your app](https://hlt3.studio/blog/gohighlevel-customers-into-your-app/), [apps for aesthetic clinics and clinician training](https://hlt3.studio/services/aesthetic-clinic-apps/).

## Sources

- [LearnDash REST API v2 (LearnDash Developers)](https://developers.learndash.com/learndash-rest-api-ldlms-v2/)
- [Transferring LearnDash Courses (LearnDash documentation)](https://docs.nexcess.com/software/learndash/transfer-courses/)
- [User Groups (LearnDash documentation)](https://docs.nexcess.com/software/learndash/groups/)
- [Course Enrollment Mode Settings (LearnDash documentation)](https://docs.nexcess.com/software/learndash/course-enrollment-mode/)
- [LearnDash Permalinks (URLs) (LearnDash documentation)](https://docs.nexcess.com/software/learndash/permalinks/)
- [Setting Up WooCommerce Integration (LearnDash documentation)](https://docs.nexcess.com/software/learndash/setting-up-woocommerce-integration/)
- [Authentication (WordPress REST API Handbook)](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/)
- [Users (WordPress REST API Reference)](https://developer.wordpress.org/rest-api/reference/users/)
- [wp user list (WP-CLI Commands)](https://developer.wordpress.org/cli/commands/user/list/)
- [WordPress 6.8 will use bcrypt for password hashing (Make WordPress Core)](https://make.wordpress.org/core/2025/02/17/wordpress-6-8-will-use-bcrypt-for-password-hashing/)
- [wp_check_password() (WordPress Developer Resources)](https://developer.wordpress.org/reference/functions/wp_check_password/)
- [Webhooks (WooCommerce documentation)](https://woocommerce.com/document/webhooks/)
- [Allowing apps and websites to link to your content (Apple Developer Documentation)](https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content)
- [About deep links (Android Developers)](https://developer.android.com/training/app-links)
- [App Review Guidelines (Apple Developer)](https://developer.apple.com/app-store/review/guidelines/), sections 3.1.3 and 4.2
- [Understanding Google Play's Payments policy (Play Console Help)](https://support.google.com/googleplay/android-developer/answer/10281818?hl=en)
- [Regulation (EU) 2016/679, GDPR (EUR-Lex)](https://eur-lex.europa.eu/eli/reg/2016/679/oj)
- [UK General Data Protection Regulation (legislation.gov.uk)](https://www.legislation.gov.uk/eur/2016/679/contents)
- [Federal Act on Data Protection, FADP (Fedlex)](https://www.fedlex.admin.ch/eli/cc/2022/491/en)
- [Covered Entities and Business Associates (HHS)](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html)

---

Provider: HLT3 Studio, a one-person software studio in Zurich, Switzerland (legal entity Health3 AG), run by founder and engineer Vaclav Skarka. Contact: contact@hlt3.studio. Prices: https://hlt3.studio/pricing/ (in USD; offers for clients in Switzerland are issued in CHF).
