How to import Bulk Members

Modified on Thu, 2 Jul at 12:22 AM

Lets you add multiple members to a membership course at once using a CSV file, instead of creating them one-by-one.

Prepare a CSV file with exactly two columns, in this exact order: name, email
The first row must be the header row with those exact column names — not "Name," "full_name," or any variation
Maximum 100 rows per import — the article's original wording ("don't import more than that, it might be causing issues") is vague; treat this as a hard limit, not a soft suggestion, until confirmed otherwise
Double-check emails in your CSV for typos before importing — fixing 100 wrong emails after the fact is far more painful than checking them first

Format exactly like this:

name,email
John Smith,john@example.com
Jane Doe,jane@example.com

2. Click "Import Members"

Select which product/bundle these imported members should have access to
This applies the same access level to every member in the file — you cannot assign different products to different rows in a single import

Step 6: Verify the Import

Go back to My Members
Spot-check a few of the newly imported names/emails to confirm they appear correctly
If possible, verify with at least one imported member that they received login access

Problem	Likely Cause	Fix
Import fails immediately	Column headers aren't exactly `name` and `email`, or wrong file format	Re-check headers are lowercase and exact; confirm file is saved as `.csv`
Only some members imported	File exceeded 100 rows, or specific rows had malformed data (missing email, invalid format)	Split into batches of 100 or fewer; check each row for typos or missing values
Members imported but can't access content	Wrong product selected during "Give access" step	Re-check the product assignment applied to the batch
Duplicate/existing emails cause errors	Some emails in the CSV already exist as members	Remove existing members from the CSV before re-importing, or check individually via My Members
No password set for imported members	CSV only supports name/email — no password field	Confirm how imported members receive login credentials (see flagged question below)