Migration guide

How to move an academy off WordPress, LearnDash and BuddyBoss

Moving a WordPress academy is four migrations at once: courses, people, history and community. Rehearse it in isolation, reconcile the records, and approve the cutover only when the numbers agree.

By Allure LMS8 min read

Why academies outgrow the plugin stack

A WordPress academy usually starts with one plugin for courses, then gains a community plugin, a membership plugin, a forms plugin and a way to issue certificates. Each is reasonable on its own. Together they become a system nobody designed: several update schedules, several places where a learner's progress lives, and a theme that has to hold all of it together.

The questions that tell you it is time to move are practical ones:

  • Does a plugin update make you nervous before a cohort starts?
  • Do learners have one place to see their progress, feedback and community, or several?
  • Can an instructor keep a grade private until it is ready, then release it?
  • Can you tell the difference between someone who completed a course and someone who can do the work?

What actually has to move

Treat the move as four migrations that happen together:

  1. People and roles. Learners, instructors, administrators, and anyone with special access.
  2. Courses and content. Course structure, lessons, quizzes, and any SCORM packages.
  3. Enrolments and history. Who was enrolled in what, and how far they got.
  4. Community. Groups and conversations, and the words your members use for them.

In Allure LMS, SCORM packages are re-hosted on Allure Connect, community moves into the built-in community module, and your look and words are set in Experience Studio before anyone arrives.

Rehearse, reconcile, approve

The safest migrations are boring. That comes from three habits:

  • Rehearse in isolation. Import everything into a rehearsal workspace that no learner can see. Test invitations and every role with dedicated test accounts.
  • Reconcile the records. Compare counts and records from source to target. Every difference should be listed and explained, not waved through.
  • Approve with a name. A named person types the confirmation for the cutover, and rollback is verified first. The old site stays the fallback until then.

This is how migration runs in Allure LMS today, and our team does the work for you. We move academies from WordPress and from Moodle.

Decide what you will not bring

A migration is the cheapest moment to leave things behind: retired courses, test accounts, abandoned groups. Write the list down before the rehearsal so that reconciliation compares like with like.

Plan the first week after cutover

Learners notice three things first: whether they can sign in, whether their progress is where they left it, and whether the place feels like theirs. Allure LMS uses one Allure Account for sign-in, carries progress through the reconciled history, and uses your template and words from day one.

Who is doing this now

Nonprofits are moving to Allure LMS from Moodle and from WordPress with LearnDash and BuddyBoss, each with its own look. 4Kira4Dads, a maternal-health nonprofit for fathers, is one of them: see its academy in Experience Studio. Compare the two approaches side by side on Allure LMS vs a WordPress LMS stack.

Your next step

See the learning experience for yourself.

Try the demo with fictional content, or plan your academy with our team.