LifterLMS Backup and Disaster Recovery: What to Save and How

What a LifterLMS backup must include, how often to take it, and how to restore without losing orders or double-charging students: a data map of LifterLMS tables and files, a recovery runbook, and the post-restore checks most guides miss.

  • Add as a preferred source on Google
Illustration for “LifterLMS Backup and Disaster Recovery: What to Save and How”

A generic WordPress backup plugin will copy your LifterLMS site. Whether it lets you recover cleanly is a different question. A course site changes every minute: students complete lessons, quizzes are graded, orders are paid and renewals are scheduled. Restoring yesterday's copy without thinking can erase today's sales or trigger a second charge for a renewal that already went through.

This guide is for site owners and developers who want a LifterLMS backup they can actually rely on. You will learn exactly where LifterLMS keeps its data, how often to back up, how to test a restore, and a step-by-step recovery runbook that protects your payments and your students' progress.

Where LifterLMS keeps your data

A LifterLMS backup has to capture the WordPress database and part of the file system. Knowing what lives where tells you what is at stake if a backup is incomplete.

DataStored in
Courses, sections, lessons, quizzes, questions, memberships, access plans, coupons, vouchers, engagements, certificate templatesWordPress posts and post meta, as custom post types
Orders and transactionsPosts of type llms_order and llms_transaction with their meta
Enrollments, lesson and course completion, progresswp_lifterlms_user_postmeta
Quiz attempts and answerswp_lifterlms_quiz_attempts
Awarded certificates and achievementsPosts of type llms_my_certificate and llms_my_achievement
Voucher codes and redemptionswp_lifterlms_vouchers_codes, wp_lifterlms_voucher_code_redemptions, wp_lifterlms_product_to_voucher
Notifications, events, sessions, lesson time sessionswp_lifterlms_notifications, wp_lifterlms_events, wp_lifterlms_events_open_sessions, wp_lifterlms_sessions, wp_lifterlms_lesson_time_sessions
Scheduled renewals, delayed emails and background jobsAction Scheduler tables, wp_actionscheduler_*
Student profile and billing detailsWordPress users and user meta
SettingsWordPress options beginning lifterlms_ and llms_
Protected media uploadswp-content/uploads/lifterlms/
Logswp-content/uploads/llms-logs/

The table prefix may not be wp_ on your site. The practical rule: back up the whole database and the whole wp-content folder. Selective backups that skip "unknown" tables are the classic way to lose student progress. For a deeper explanation of how these pieces connect, see the LifterLMS data model explained.

How often to back up a LifterLMS site

Decide two numbers before you choose a tool:

  • Recovery point objective (RPO): how much data you can afford to lose. If you restore last night's backup at 4pm, everything since midnight is gone: orders, enrollments, quiz attempts.
  • Recovery time objective (RTO): how long the site can be down while you restore.

Rough guidance by site type:

  • Internal training, low change rate: daily database and files is usually enough.
  • Selling courses, steady sales: database at least every few hours, files daily.
  • High-volume sales or active subscriptions: near real-time database backups (many managed hosts and backup services offer incremental or point-in-time options), files daily.

Keep at least 30 days of history, because some problems, such as a hack or a bad import, are discovered weeks later. Store copies off the server and preferably with a different provider from your host. The WordPress handbook's guide to backups covers the general principles well.

Choosing a backup method

Any of these can work, provided it captures the full database and wp-content:

  • Host-level snapshots. Fast to restore and no load on WordPress. Check how often they run, how long they are kept, and whether you can restore the database alone.
  • A backup plugin sending archives to cloud storage. Good for portability between hosts. On large sites, make sure it can handle your database size without timing out.
  • WP-CLI and a server cron job. Simple, scriptable and easy to verify, as below.

Whatever you use, have at least two independent copies: for example, host snapshots plus an off-site plugin or script backup.

A scripted backup with WP-CLI

#!/usr/bin/env bash
# llmsx-backup.sh - database and wp-content backup. Run from the WordPress root.
set -euo pipefail

STAMP=$(date +%Y%m%d-%H%M)
DEST="/backups/lms"
mkdir -p "$DEST"

# Confirm the LifterLMS and Action Scheduler tables exist (and will be included).
PREFIX=$(wp db prefix)
wp db tables "${PREFIX}lifterlms_*" "${PREFIX}actionscheduler_*" --all-tables-with-prefix

# Full database export, compressed.
wp db export - --single-transaction | gzip > "$DEST/db-$STAMP.sql.gz"

# Files: uploads (including protected media and logs), themes and plugins.
tar -czf "$DEST/wp-content-$STAMP.tar.gz" wp-content

# Keep 30 days locally; sync $DEST off-site with your storage tool of choice.
find "$DEST" -type f -mtime +30 -delete

The --single-transaction option is passed to mysqldump so InnoDB tables are exported consistently without locking the site. Copy the results off the server with a tool such as rclone or your cloud provider's CLI.

Test your restores

An untested backup is an assumption. At least quarterly:

  1. Restore the latest database and files to a separate staging server.
  2. Before anything else runs, make sure the staging copy cannot charge anyone (see the next section).
  3. Log in as a test student and check enrollments, progress, quiz results and certificates.
  4. Open a recent order in the Orders menu and check its transactions.
  5. Write down how long the restore took. That is your real RTO.

Disaster recovery runbook for LifterLMS

When you need to restore production, work through these steps in order. Print them; you will not want to think from first principles during an outage.

1. Stop the damage

Put the site into maintenance mode. If you suspect a hack, change hosting, database and administrator passwords and revoke REST API keys before restoring, or the attacker may simply come back.

2. Choose the restore point

Pick the most recent backup taken before the problem. Note its exact time: everything after it will need reconciling.

3. Save what you are about to overwrite

Export the current, broken database first. It may contain orders and progress from after the restore point that you can recover later.

4. Restore and handle the payment safeguard

LifterLMS stores the site's URL and disables automatic recurring payments when it detects that the site is running at a different URL, to stop a copy from charging students twice. If you restore to the same URL, nothing changes. If you restore to a new domain or a temporary URL, you will see the notice It looks like you may have installed LifterLMS on a staging site! Choose Enable Automatic Payments only on the one site that should take payments. Our guide to staging sites and recurring payments explains the URL lock and the LLMS_SITE_IS_CLONE constant for copies that must never charge.

5. Reconcile payments with your gateway

This is the step most recovery guides miss. Your payment gateway's records did not roll back. Compare its payments since the restore point with the orders in LifterLMS:

  • New purchases since the restore point are missing from LifterLMS. Recreate access for those customers, using the saved database from step 3 as a reference.
  • Renewals that were charged after the restore point may be scheduled to run again. Check the Scheduled Actions tab under LifterLMS > Status for llms_charge_recurring_payment actions due soon on those orders, and confirm each order's next payment date before allowing renewals to run.
  • Refunds and cancellations made in the gateway after the restore point need repeating in LifterLMS.

6. Repair the schedule

Run Reschedule Recurring Payments under LifterLMS > Status > Tools & Utilities. It checks active recurring orders and reschedules any due payment that has no scheduled action. Then confirm WP-Cron or your server cron is running.

7. Recover student activity

Progress made after the restore point is gone from the live tables. For a short gap, the simplest fix is often to tell affected students and mark lessons complete for them from the student's course view under LifterLMS > Reporting, which has Mark Complete buttons per lesson. For larger gaps, a developer can copy rows for affected users from the saved database's lifterlms_user_postmeta and quiz attempt tables, but test that on staging first.

8. Tell people

Email affected students with what happened and what they need to do, if anything. A short, honest message prevents a wave of support tickets.

Common backup mistakes on LifterLMS sites

  • Backing up only posts and pages. Some export tools skip custom tables, which hold enrollments, progress and quiz attempts.
  • Excluding uploads to save space. Protected course files live in uploads/lifterlms/.
  • Restoring over a live site with active subscriptions without reconciling the gateway.
  • Restoring to staging and leaving automatic payments on.
  • Keeping backups on the same server. A failed server or compromised account takes the backups with it.
  • Deleting the plugin "to reinstall it". If LLMS_REMOVE_ALL_DATA is set to true in wp-config.php, deleting LifterLMS removes its tables, options and content. Deactivating is safe; deleting with that constant is not.

Frequently asked questions

Does LifterLMS have a built-in backup feature?

No. LifterLMS can export and import courses, but that is for moving course content, not a backup of students, orders or progress. Use host snapshots, a backup plugin or a scripted database and file backup.

Can I restore one student's progress?

Not with a standard backup tool, which restores the whole database. A developer can extract that user's rows from a backup copy and insert them into the live tables, or you can mark lessons complete manually for a small number of lessons.

Will restoring a backup re-charge my students?

It can, if a renewal charged after the backup was taken is still scheduled in the restored copy. Reconcile with your gateway and check scheduled recurring payment actions before allowing renewals to run.

How long should I keep backups?

At least 30 days of daily copies, plus monthly copies for longer if you can. Problems like a compromised site or a bad bulk edit are often discovered weeks later.

What to do next

Check today that your backups include the full database and wp-content, are stored off the server, and run often enough for your sales volume. Then book a test restore on staging and time it. Add backups to your LifterLMS maintenance routine so they are checked every week.

If you want this handled for you, including off-site backups, restore testing and help on the day something goes wrong, our LifterLMS support service covers it. Contact us to talk about your site.

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