Invite members to Skool with CSV: prepare a safe import

Importing an email list into Skool requires checking who should receive access and under what conditions. Official help says email invitations and bulk CSV invitations grant access without purchasing or requesting membership. They should therefore not be treated as an interchangeable replacement for an acquisition campaign. A list of interested prospects and a list of people entitled to join are not the same thing, even when both contain valid email addresses.

Prepare recipients, not an entire database

Our recommendation is to use the minimum necessary information and remove duplicates, mistyped addresses and people who should not receive an invitation. Confirm that using their details for this purpose is appropriate. The public guide consulted describes uploading the file but does not establish a universal column schema. Follow the instructions or template shown in the current interface rather than inventing headers or assuming extra database fields will be supported.

The import route and the recipient's step

Open Settings and select Invite. For a bulk import, the documentation says to click Import and then Upload file. The same area also supports copying an invitation link or sending individual email invitations. Recipients must click Join now in the email to be pre-approved. Uploading a file does not mean everyone has joined: distinguish an invitation being sent from a person actually becoming a member of the group.

Worked example: moving an earlier workshop group

A trainer wants to move 24 former learners whose agreed entitlement includes community access. She checks addresses against her records, removes one duplicate and sets aside two addresses needing confirmation. As a recommendation, she starts with a small authorised batch and verifies the acceptance journey before continuing. She excludes people who only downloaded a free resource because they do not have the same access agreement, even though their details appear in her contacts.

Pre-upload checklist

• Confirm every recipient should receive access without a purchase or application.
• Clean duplicates and uncertain addresses before exporting the file.
• Use the format specified by the current interface.
• Review course access where the chosen invitation method allows it to be configured.
• Restrict access to the CSV and delete temporary copies when they are no longer needed.

For large lists, Skool recommends inviting through an external CRM instead of bulk upload. The guide does not state a numerical threshold, so avoid inventing one and check the appropriate process for your situation.