Skip to main content

How to Migrate from the Old MemberSync System

Older MemberSync installations stored their data differently. This guide moves that data into the current system. Newer installations have nothing to migrate and can skip this.

warning

Back up your database before migrating. The migration preserves old data, but a backup is essential.

Before you start​

  • Take a full database backup.
  • Updating MemberSync to the current version is what starts the migration, so back up first. Make sure its dependencies (LearnDash, WooCommerce, WooCommerce Memberships) are current too.

How the migration works​

You don't trigger the migration manually — it runs automatically when you update (or activate) the current version of MemberSync:

  • The database structure is brought up to date as soon as the new version loads.
  • Your legacy data — old organizations, licenses, and seats, plus membership information that was stored as user data — is converted into the current records in the background, using WordPress's scheduled-task system, so a large site keeps working while it processes.
  • Old data is preserved, not deleted, so you can verify the result before anything is cleaned up.

The migration only runs when there's something new to apply — it's tied to the plugin version, so it won't repeat needlessly — and it's safe if interrupted: the next load continues where it left off.

Verify the migration​

After it runs, confirm your data looks right:

  • Organizations, members, and their roles appear as expected.
  • License and seat assignments are intact.
  • Members have the LearnDash access they should.

Clean up (optional)​

Once you've verified everything, you can remove the preserved legacy data.