How to Migrate from Tutor LMS to LifterLMS Without Losing Students

A practical plan for moving from Tutor LMS to LifterLMS: how topics, quizzes, assignments and monetization map, how to import content through the LifterLMS importer, and how to carry students and progress across safely.

  • Add as a preferred source on Google
Illustration for “How to Migrate from Tutor LMS to LifterLMS Without Losing Students”

Moving from Tutor LMS to LifterLMS is one of the easier LMS migrations, because both are WordPress plugins. Your users, pages, media library and theme stay where they are. Only the learning layer changes: courses, lessons, quizzes, enrollments, progress and how people pay.

This guide is for site owners and developers planning that switch. It covers how Tutor's structure maps to LifterLMS, which tools exist (and which do not), a repeatable way to import content, and how to bring students across without sending them a flood of emails or charging anyone twice.

If you have not yet decided whether to switch, our LifterLMS vs Tutor LMS comparison covers that question. For the general process that applies to any platform, such as audits, staging and rollback, start with our general LifterLMS migration guide. This article covers the Tutor specifics.

How Tutor LMS content maps to LifterLMS

Tutor organises a course into topics, and each topic holds lessons, quizzes and (with Tutor Pro) assignments. LifterLMS organises a course into sections, and each section holds lessons. A quiz in LifterLMS is not a separate item in the outline; it is attached to a lesson, and a lesson holds at most one quiz.

Tutor LMSLifterLMSNotes
CourseCourseTitle, description, excerpt, featured image and categories carry over.
TopicSectionA clean one-to-one match. Keep the topic order.
LessonLessonDirect match, including the video URL in the lesson's video field.
Quiz inside a topicQuiz attached to a lessonAttach it to the lesson before it, or create a lesson such as "Topic 3 quiz" to hold it.
Single and multiple choice, true/falseMultiple Choice, True or FalseCore question types.
Fill in the blank, ordering, short and open-ended answersAdvanced Quizzes add-on typesPaid add-on with Fill in the Blank, Reorder Items, Short Answer, Long Answer and more. Otherwise rewrite the question.
AssignmentsAssignments add-onPaid add-on. Old submissions are usually archived, not migrated.
Content drip and prerequisitesDrip and prerequisitesBoth are in the free LifterLMS core.
CertificatesCertificate templatesRebuild the design in the LifterLMS certificate editor.
Ratings and reviewsCourse reviewsLifterLMS reviews are text only, with no star ratings.
Instructor earnings and withdrawalsNo core equivalentLifterLMS has no commission or payout system in core.

Two rows deserve a decision before anyone writes code. The first is quizzes: pick one rule, such as "every Tutor quiz becomes a quiz on a new lesson at the end of its section", and apply it to every course so reports stay consistent. The second is instructor revenue. If you run Tutor as a marketplace that pays instructors, plan a separate solution for commissions and payouts first, because that part of your business needs a different tool.

What migration tools exist

There is no Tutor importer in LifterLMS core, and we found no dedicated Tutor-to-LifterLMS migration plugin on WordPress.org at the time of writing. The official Tutor LMS Migration Tool moves data in the other direction, into Tutor. Tutor Pro's Import/Export tool saves courses and settings as a JSON file, but that file is in Tutor's own format, so LifterLMS cannot read it.

That leaves three realistic routes:

  • Rebuild by hand. Fine for two or three short courses. Copy lesson content in the block editor, recreate quizzes in the Course Builder, and enroll students afterwards.
  • Script it through the LifterLMS importer. Read Tutor's data, write it out as a LifterLMS import file, and let LifterLMS create the courses. This is the method we recommend for anything larger, and it is described below.
  • A fully custom migration plugin. Worth it when you have thousands of students, paying subscribers or unusual structures, and you want a repeatable dry run.

Importing course content through the LifterLMS importer

LifterLMS can create complete courses from a JSON file under LifterLMS > Import. The same importer reads its own course exports, and it accepts a bulk format that holds many courses at once. The LifterLMS guide to importing courses notes that a file from another platform can be imported if it is built to match that format, and that each course arrives as a draft. Because both plugins live in the same database, a short script can read each Tutor course, topic, lesson and quiz and write them into that format. You then import the file on a staging copy, check the result, and repeat until it is right.

A cut-down example of the target format, with one course, one section, one lesson and a one-question quiz:

{
  "_generator": "LifterLMS/BulkCourseGenerator",
  "_version": "10.3.2",
  "courses": [
    {
      "title": "Photography Basics",
      "content": "<p>Course description from Tutor.</p>",
      "status": "draft",
      "sections": [
        {
          "title": "Topic 1: Getting started",
          "lessons": [
            {
              "title": "Choosing a camera",
              "content": "<p>Lesson body from Tutor.</p>",
              "video_embed": "https://vimeo.com/123456789",
              "quiz_enabled": "yes",
              "quiz": {
                "title": "Topic 1 quiz",
                "passing_percent": 70,
                "questions": [
                  {
                    "title": "Which setting controls depth of field?",
                    "question_type": "choice",
                    "points": 1,
                    "multi_choices": "no",
                    "choices": [
                      { "choice": "Aperture", "choice_type": "text", "correct": true, "marker": "A" },
                      { "choice": "ISO", "choice_type": "text", "correct": false, "marker": "B" }
                    ]
                  }
                ]
              }
            }
          ]
        }
      ]
    }
  ]
}

Three details make this approach safer than writing posts directly:

  • It runs as one transaction. The LifterLMS generator wraps the import in a database transaction and rolls it back if an error is thrown, so a bad file does not leave half a course behind.
  • Images come with it. The importer sideloads images it finds in lesson content into your media library. Because Tutor images are usually already in the same media library, they simply keep working.
  • Relationships are built for you. Sections, lessons, quizzes and questions are linked to their parents correctly, which is the part people most often get wrong with generic CSV tools.

Import courses as drafts, and keep a spreadsheet that maps each Tutor ID to its new LifterLMS ID. You will need that map in the next step.

Moving students, enrollments and progress

User accounts do not move at all. Tutor students are WordPress users, so they keep their logins and passwords. What has to move is the link between each user and each course, and their completed lessons.

Tutor keeps enrollments, lesson completions and quiz attempts in its own records. LifterLMS keeps enrollments and completions in its wp_lifterlms_user_postmeta table, which our article on the LifterLMS data model describes. Export from Tutor a list of user, course, enrollment date and completed lessons, translate the IDs with your map, then write them into LifterLMS with its own functions:

  1. Turn off enrollment and completion emails first. llms_enroll_student() and llms_mark_complete() fire the same hooks as a real enrollment, so welcome emails, certificates and achievements go out unless you stop them. Disable the relevant notifications under LifterLMS > Settings > Notifications and suppress engagements in your script.
  2. Enroll each student with llms_enroll_student( $user_id, $course_id, 'llmsx_tutor_import' ). The custom trigger lets you find migrated enrollments later.
  3. Restore the original enrollment date. LifterLMS reads it from the updated_date of the _start_date row. If everyone is enrolled "today", lessons dripped by days after enrollment lock again for long-standing students.
  4. Mark completed lessons with llms_mark_complete( $user_id, $lesson_id, 'lesson', 'llmsx_tutor_import' ). Completing the last lesson also completes the section and course, which may award a certificate, so have templates ready.
  5. Flush the object cache and spot-check a dozen students' dashboards against Tutor.

Our LearnDash migration guide includes a complete WP-CLI script for this step. It works the same way for Tutor once you change the source query. Quiz attempt histories rarely justify the effort: keep a final-grade export for your records and let students start quizzes fresh.

Payments, subscriptions and WooCommerce

How you sold courses in Tutor decides the work here.

  • One-time purchases. Past payments do not need to move. Students keep access through the enrollments you import, and you keep the payment history in your gateway.
  • Tutor's native eCommerce or recurring payments. Existing subscriptions keep billing through the gateway, but LifterLMS does not know about them. Either honour them manually and move each subscriber to a new LifterLMS access plan at renewal, or have a developer create matching LifterLMS orders linked to the existing gateway subscriptions. The second is custom work that must be tested against real gateway events.
  • WooCommerce. If WooCommerce sold access to Tutor courses, you can keep it and switch to the paid LifterLMS WooCommerce add-on, so products grant LifterLMS enrollments instead. See LifterLMS with WooCommerce.

If you move to LifterLMS checkout, remember that the free core includes only the manual gateway. Stripe and PayPal are paid add-ons. Never let both plugins run renewals at once, and never run a staging copy with live gateway keys.

Cut-over plan and URLs

Course and lesson URLs will change unless you plan them, so do the switch on staging first and prepare redirects before launch.

  1. Copy production to staging and run the content import there until counts match: courses, sections, lessons, questions.
  2. Run the student import and compare enrolled and completed counts per course with Tutor.
  3. List every public Tutor URL (course pages and any lesson URLs students bookmark) and map each to its new LifterLMS URL. LifterLMS uses /course/ and /lesson/ by default; you can change the bases in Settings > Permalinks.
  4. Freeze sales and content edits on production for the cut-over window.
  5. Repeat the imports on production using the tested scripts, add 301 redirects, then deactivate Tutor. Keep its tables in the database until you are sure you no longer need them.
  6. Re-enable notifications, test a real purchase end to end, and email students about the new dashboard.

Common mistakes

  • Running both plugins on live for weeks. Two LMS plugins mean two sets of access rules and two sets of emails. Keep the overlap to the cut-over window.
  • Forgetting that one lesson holds one quiz. Tutor topics with two quizzes need two lessons in LifterLMS.
  • Losing enrollment dates. Drip schedules depend on them.
  • Importing with notifications on. Every migrated student gets a welcome email and possibly a certificate.
  • Not budgeting for add-ons. If you relied on Tutor Pro assignments or advanced question types, price the LifterLMS add-ons before you commit.

Frequently asked questions

Will my students need new passwords?

No. Tutor and LifterLMS both use WordPress user accounts, so logins carry over unchanged.

Can I import Tutor's JSON export into LifterLMS?

Not directly. Tutor's export file uses Tutor's own structure. A script has to translate it, or read the Tutor data from the database, into the LifterLMS import format.

How long does a Tutor to LifterLMS migration take?

For a handful of courses with simple quizzes, a few days including testing. Sites with many students, subscriptions or a marketplace take longer, mostly because of payments and testing, not content.

Can I keep my course URLs?

Often yes for course pages, by matching the permalink base. Where you cannot, add 301 redirects from each old URL.

Next steps

Start with an inventory: number of courses, question types in use, how many active students, and how people pay. That list decides whether this is a weekend rebuild or a scripted migration. If you want the content and student import scripted, tested on staging and run for you with a rollback plan, our LifterLMS migration service handles exactly this. Send us your inventory and we will tell you which route fits.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day