📥 Migrating From WishList Member

If WishList Member runs this site today, or ran it in the past, everything it stored is still in your database. The Import / Export tab reads it and builds the same membership site in ResultsAiX Membership, step by step, without changing a single row of the old plugin's tables.

You keep your members, their passwords, their join dates and the level numbers your other tools already use. When the counts match, you switch the old plugin off and turn on compatibility mode, so pages and integrations built for WishList keep working.

Where to find it:

Open AiX Membership in the WordPress menu, then the Import / Export tab. The first section is Migrate from your current membership plugin. When WishList data is on the site, the box at the top says what it found, for example "4 levels, 347 membership grants, 42 protection rules, 3 protected folders". If nothing is found, the section says so and points you to the CSV importer further down the same tab.

The six steps on screen:

Run them in order, top to bottom. Each button shows a tick and the time it last ran, and every step is safe to run again: nothing is ever created twice.

1. Import levels and settings. Press Import levels. One level is made here for each WishList level, keeping the same numeric id, so your checkout, licence server and sync tools need no changes. Per level login, registration and logout redirects come across. Free registration stays off for every imported level. The global after login and wrong level redirects and the API key are copied where this plugin still has its defaults. The old plugin's level actions are read too and recreated on the Level Actions tab, marked as imported.
2. Import content protection. Press Import content protection. Page, post, custom post type and category protection is copied onto the new levels. Only content the old plugin actually flagged as protected gets locked here. Attachment rules are listed rather than imported, because protected downloads belong in the sealed library on the Files & Folders tab.
3. Protect the folders. Press Protect folders. WishList knew folders only by a checksum of their name, so this reads the folder root it was set up with, matches each rule to a real folder on disk and writes this plugin's guard into each one. Any rule it cannot match is listed for you.
4. Import the menu rules. Press Import menu rules. Menu items the old plugin showed or hid by level come across onto the same levels, and its login and log out menu items become working links here. The step tells you how many it found, or that there is nothing to bring across.
5. Import members. Press Import members. Every member is attached to their levels in batches of 250 with a progress bar. Original join dates come across, cancelled grants arrive as cancelled, and transaction references are kept. A few thousand grants take a few minutes, so leave the tab open until the bar fills.
6. Verify. Press Run verification. You get the old counts next to the new counts, level by level.

Nothing is sent to anybody during an import. Autoresponder bridges and level actions do not fire, so moving thousands of members never sets off thousands of welcome emails.

What comes across, in short:

• Levels, with their original numeric ids and per level redirects
• Every member's level grants, with join dates, cancelled flags and transaction references
• Page, post, custom post type and category protection
• Protected folders, matched to real folders and guarded
• Menu visibility rules and the login and log out menu items
• Level actions, which appear on the Level Actions tab with an imported badge
• The API key, so the tools that call the old API keep their settings

The Last import notes box under the steps keeps a short record of each pass: how many pages were protected, which rules pointed at content that no longer exists, which folders had no rule, and how many level actions were found and created.

Why your members notice nothing:

WishList members are already WordPress users. Nobody gets a new password and nobody has to log in again. Because the original join dates come across, drip content carries on from where each member really is, so a member of two years still sees every lesson they had yesterday.

A worked example:

Say Yoursite Academy ran WishList with four levels: Silver Club, Gold Club, Workshop Replays and Free Newsletter. The box on the Import / Export tab reads 4 levels, 347 membership grants, 42 protection rules and 3 protected folders.

1. Press Import levels. Four levels appear on the Levels tab with the same ids WishList used.
2. Press Import content protection, then open the Protect Content tab. The protected pages are listed under Currently protected content with their new levels.
3. Press Protect folders, then check the Files & Folders tab: each folder shows .htaccess in place.
4. Press Import menu rules.
5. Press Import members and wait for the bar to finish.
6. Press Run verification and compare the numbers for each level.

After importing, your checklist:

1. Open the Members tab and look up two or three members you know. Their levels and join dates should match what WishList showed.
2. Open a protected page in a private browser window. You should see your protection message, not the content.
3. Open the Settings tab and tick Turn on compatibility mode, then save.
4. Deactivate WishList Member and its shortcode add on. Keep both installed but inactive for a while.
5. Open a few pages that use WishList shortcodes and check they still read correctly.

Switching back, if you need to:

Untick Turn on compatibility mode and save, then reactivate WishList Member. Its data was never touched, so it picks up exactly where it was. If you reactivate it first, this plugin steps aside for that request on its own and stays aside while the old plugin is active.

Tips:

• Run the steps on a quiet evening, and keep the old plugin installed but inactive for a few weeks.
• Leave the old plugin's tables alone until compatibility mode has run cleanly for a while. Retiring them later is a rename, never a delete.
• If your old members live on another site, export them there as a CSV and use Import members from CSV at the bottom of the same tab.

Next, read Compatibility Mode, API Keys And Retiring The Old Tables, then Level Actions And Bundles to see the rules that came across.