Once your event is published and registrations start coming in, guests share valuable information — names, emails, phone numbers, addresses, affiliations — along with ticket selections and payments. This article helps you get all of that data where it needs to go, whether that's into Almabase profiles, your connected CRM, or an export file.

The specifics depend on your setup, but the starting point is always the same.

Before any guest data can flow anywhere — to an Almabase profile, to your CRM, or even into a clean export with constituent data attached — each registration needs to be linked to the right person. This is called mapping.

Mapping connects a guest's registration to an existing constituent, so the system knows whose profile to update and whose record to sync. Without it, the registration sits unlinked, and the data has nowhere to go.

Begin mapping as soon as registrations start coming in. You don't have to wait until the event is over.

Full guide: Mapping event guests to the right constituents

Once your guests are mapped,

These are independent — you can do any combination, in any order.

Guests often share updated phone numbers, new email addresses, or current mailing addresses when they register. You can push that information from the event form into their Almabase profiles.

This is controlled by your event connector rules — you decide whether each type of data flows automatically, gets flagged for your review, or is ignored.

This step is relevant regardless of whether you use a CRM integration.

Full guide: Pushing contact details from event forms to Almabase profiles

If you use Raiser's Edge NXT or BBCRM, you can move the updated contact details from Almabase profiles onward to your CRM. This is a separate step from updating the Almabase profile — it's controlled by your constituent sync rules and reviewed through the Data Inbox.

Full guide for RE NXT: Pushing contact details from Almabase profiles to Raiser's Edge NXT/ BBCRM

If you use Raiser's Edge NXT or BBCRM, you can sync the event record itself — tickets, accompanying guests, payments, and donations — so the event appears on constituent records in your CRM.

This involves configuring your event's sync settings, syncing guests to create event participants, and pushing the payment batch.

Guides for RE NXT:

Guide for BBCRM:

If you don't use a CRM integration — or if you need the data in a spreadsheet for other purposes — you can export your event data directly from the Guest Dashboard. Mapping still matters here: mapped registrations are attributed to the right people in the export, while unmapped ones appear without a constituent link.

Guide: Getting an Event Export

Here's how these paths relate to each other:

Every path starts with mapping. After that, pick the ones that apply to your setup and work through them in whatever order makes sense for your team.

No. Mapping is the one step everyone should do. After that, choose the paths that match your setup. If you don't use a CRM, updating Almabase profiles and taking an export may be all you need. If you do use a CRM, you'll likely want to push contact details and sync the event record as well.

Not really. Pushing contact details to Almabase profiles, pushing them onward to your CRM, and syncing event registrations are all independent. You can do them in any order or work on them in parallel. The only dependency is that mapping comes first.

No — syncing event registrations and pushing contact details are independent paths. But mapping is still required. And if guests shared updated contact information during registration, it's worth reviewing that data too, since it's already captured.

Yes. Mapping links each registration to the right constituent on Almabase, which means your engagement tracking is accurate and your exports are clean. Even without a CRM, mapping is what makes your event data useful.