Three exports give you people data as CSV files sent to your email: the registrant list with invite details, the open chats between attendees, and an attendee file formatted for a CRM import.

Before you start

You need to be an organization admin or an event admin.
Brella emails every file as a zip to the address you use for the admin panel. Nothing downloads in the browser.
The meetings export is next to these exports. See Monitor, export and cancel meetings.

Where to find it

Registrants and open chats: People > Settings > Export.
CRM data: Integrations > Integration List. The page is titled Attendee data to CRM.

Export registrants

Open People > Settings and go to Export.
Under Export registrants, select Export registrants (.csv). The message "Your CSV export will be delivered by email shortly." confirms the request.
Open the email with the subject "<event name> join codes". The zip contains <event code>-registrants-<date>.csv.

The file has one row per registrant, joined or not, sorted by Brella ID. Interests and goals are not in this file; use the CRM export or Matchmaking > Statistics > Export data (.csv).

Column	What it contains
`id`	Brella's ID of the registrant.
`event_id`	Brella's ID of the event.
`ticket_type_list_id`, `ticket_type_list_name`	The registrant's ticket type list.
`custom_list_ids`	IDs of the custom lists the registrant was added to by hand, comma-separated. Lists filled by automations are not included.
`registered_id`	The ID you gave the registrant in an import or through the API.
`registered_email`, `registered_first_name`, `registered_last_name`, `registered_company`, `registered_job_title`	The registration data you entered or imported.
`status`	`invited` or `joined`.
`pitch`	The registrant's pitch text.
`join_token`	The personal join code.
`persona_id`, `persona_name`, `function_id`, `function_name`, `industry_id`, `industry_name`	The identity values. The column names stay `persona`, `function` and `industry` even if you renamed the labels.
`created_at`	When the registrant was created: the time the invite was added, or the join time for people who joined without a personal invite.
`joined_user_id`, `joined_user_email`, `joined_user_first_name`, `joined_user_last_name`, `joined_user_company_name`, `joined_user_job_title`	The account that joined and the person's profile in the event. For registrants who have not joined, `joined_user_id` is empty and the registration data is repeated in the other columns.
`onboarding_completed_at`	When the person finished onboarding in the app.
`qr_string`	The content of the person's Brella QR code.
`external_qr_string`	The QR code value you imported, if any.
`joined_user_skip_networking_status`	`true` when the person opted out of networking.
`old_invite_id`, `old_attendee_id`	IDs from before registrants replaced invites and attendees.
`join_url`	The personal join link, `<web app>/join/<code>`.
`allows_natural_search`	Whether the registrant is included in natural language search.
`registration_link`	Name of the registration link the person used, if any.

Export open chats

Open People > Settings and go to Export.
Under Open chat export, select Open chat export (.csv).
Open the email with the subject "<event name> - open chats report". The zip contains <event code>-open_chats-<date>.csv.

The file has one row per conversation that is still an open chat. Open chats that turned into meeting requests are in the meetings export instead. Columns:

Column	What it contains
`Date`, `Time`	Empty. Open chats have no time slot.
`Status`	`Chat_requested` (no reply yet) or `Chat_replied`.
`Location`, `Meeting Point`	`Networking area` and empty. Open chats have no location.
`Requester Email`, `Requester Name`, `Requester Company`, `Requester Title`, `Requester Ticket Type List`	The person who started the chat.
`Receiver Email`, `Receiver Name`, `Receiver Company`, `Receiver Title`, `Receiver Ticket Type List`	The person who received it.
`Created`, `Changed status`	When the chat was started and last changed, as `dd-mm-yyyy hh:mm` in the event's time zone.

With Meeting ratings on, the file also has the 8 rating columns of the meetings export. They hold 0.0 and empty values, because open chats can't be rated.

Export attendee data for a CRM

Open Integrations > Integration List.
On the card for your CRM, Salesforce, Hubspot or Pipedrive, or on Other for a generic file, select Export data. The message "Data sent to <your email>" confirms the request.
Open the email with the subject "<event name> - Attendees for CRM import". The zip contains <event code>-attendees-<date>-for-crm.csv.

Integration List page titled Attendee data to CRM with the Salesforce, Hubspot, Pipedrive and Other cards and their Export data buttons

Brella does not connect to your CRM. The file is a CSV you import yourself. It has one row per attendee who joined, sorted by Brella ID.

Column	What it contains
`First name`, `Last name`, `Email`	From the attendee's profile.
`Company name`	Company from the profile. Pipedrive files name this column `Organization name`.
`Job title`, `LinkedIn`, `X`, `Website`, `Operates in`	From the profile.
`Ticket type list`	The attendee's ticket type list.
`Event name`, `Event date`	The event and its start date.
`Joined at`	When the registrant was created, in the event's time zone. For a registrant who was invited first, this is the time of the invite, not the time they joined.
`Number of meetings`	Accepted meetings.
`Meetings with`	For each of those meetings, the name of the other person who requested or received it, comma-separated.
`Number of open chat`	Open chats that got a reply and have not turned into meetings.
`Open chat with`	Names of the other people in all the attendee's open chats, replied or not.
`Opted out of networking`	`true` when the attendee opted out of networking.
`Networking about`, `Exploring getting or buying`, `Offering or selling`, `Seeking a job in`, `Offering a job in`, `Seeking investment for`, `Investing in`, `Looking for a mentor in`, `Mentoring in`	The interests the attendee selected with that goal, comma-separated. One column per goal.

The Other file adds 3 columns at the end with the event's identity labels, by default Persona, Industry and Function, holding the attendee's identity values. The Salesforce, Hubspot and Pipedrive files have no identity columns.

Check your CRM's import requirements before importing. Column names in the file are fixed; rename them in a spreadsheet if your CRM needs other names.

Limits

The registrants export is the only one that includes registrants who have not joined.
Custom list memberships from automations are not in the registrants export.
The CRM export counts accepted meetings and replied open chats only.

Troubleshooting

The email hasn't arrived
Check the spam folder of the email address you use for the admin panel, then request the export again. For the CRM export, the message "Failed to send data, please refresh your browser and try again" means the request did not start.

Interests are missing from the registrants export
Expected. Interests and goals are in the CRM export and in Matchmaking > Statistics > Export data (.csv).

Export registrants, open chats and CRM data