📥 MemberMojo Import
The MemberMojo importer migrates your existing member database into Pavilion without manual re-entry. It is safe to run multiple times — it matches by email and updates existing records rather than creating duplicates.
How to export from MemberMojo
- Log in to your MemberMojo admin panel
- Go to Members → Export
- Select All members and download the CSV file
What the importer does
- Matches members by email — creates new WordPress accounts for anyone not already in the system
- Maps MemberMojo membership types to Pavilion types (Full, Sports, Social, Winter)
- Imports membership numbers, join dates, renewal dates, payment status, phone and address
- Assigns the
pvl_memberrole to all imported accounts
Expected CSV columns
Member Number, First Name, Last Name, Email, Phone, Membership Type, Status, Join Date, Renewal Date, Amount Paid, Address Line 1, Town, County, Postcode, Notes
Common questions
- Will it overwrite data I have already entered in Pavilion?
- Yes — for members matched by email, the import updates their Pavilion profile with data from the CSV. Run the import before you start manually editing profiles, or take a database backup first.
- What password are new imported members given?
- A secure random password is generated. Members should use the Forgot password link on first login.
- Can I import from a system other than MemberMojo?
- Yes. The importer accepts any CSV with at minimum: email, first name and last name. Additional columns are imported if present. Column names are matched flexibly.
- What happens if a membership type or status in my file doesn't exist here?
- The importer checks every “membership type” and “status” against the ones this club actually uses. Familiar names and common variations are matched automatically, but anything it can’t match to a real type or status is flagged as an error on that row — so a member is never imported attached to a type or status that isn’t set up. Correct the value in your file (or use one of the club’s types) and re-import. This is part of a wider rule in the importer: data is only imported once the things it depends on already exist, and when several kinds of data are imported together they are ordered so prerequisites (for example rinks and members) come before the data that needs them (such as bookings).