When donors give through your Almabase campaigns, they share valuable information — names, emails, addresses, payment details — alongside their donations. This article helps you get all of that data where it needs to go: into Almabase profiles, your connected CRM, or both.

The specifics depend on your setup (payment gateway, CRM connection, gift type), but the starting point is always the same.

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

Mapping connects a donor's gift to an existing constituent, so the system knows whose giving history to update and whose record to sync. Without it, the gift sits unlinked — it won't appear on the constituent's giving history, it won't sync to your CRM, and while it will still appear in giving exports, it won't be connected to a constituent on the file.

Begin mapping as soon as gifts start coming in. You don't have to wait until a campaign ends.

The system's auto-mapping handles the majority of records automatically — only gifts it can't confidently match land in your queue for manual review. You can tune the matching rule under Gift Settings → Auto mapping settings to control how aggressively the system matches.

Full guide: Mapping gifts to the right constituents

Once your donors are mapped, you can:

These are independent — you can do either or both, in any order.

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

This is controlled by your giving 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 events and giving 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: Pushing contact details to RE NXT / BBCRM from events and giving

When syncing gifts, you can tag them with campaign, appeal, and package codes so they arrive in Raiser's Edge with the right categorization. This is optional — gifts will sync without it — but setting it up front saves you from entering codes manually each time.

You can configure these codes at several levels: on the campaign's settings page (in the Gift Sync Metadata section), on an individual gift, or at the gift list / segment level when you're building a list to sync. Codes set on the campaign page apply to every gift from that page by default, but you can override them at the gift or list level.

This works the same way event sync configuration does — you set defaults at a global level, then override per page when needed.

Full guide: Setting up campaigns, appeals, and packages for gift sync

Once donors are mapped, you can sync one-time gifts to Raiser's Edge NXT. The process works through gift lists: you filter your gifts, create a list, validate it, configure the gift batch details, and push.

Gifts arrive in RE NXT as a batch under Giving → Overview. You'll review and commit the batch on the RE side to finalize the gifts on constituent records.

Full guide: Syncing one-time gifts to Raiser's Edge NXT

Recurring gifts go through the same gift list process as one-time gifts — you can even include both types in the same list. How the sync works depends on your payment gateway:

With both gateways, once the initial sync and commit are done, subsequent payments flow automatically without any further action from Almabase.

Full guide: Syncing recurring gifts to Raiser's Edge NXT

After syncing, gifts land in Raiser's Edge as uncommitted batches. A batch is visible in RE NXT under Fundraising → Gift Management, but the gifts won't appear on constituent records or in reports until the batch is reviewed and committed.

This step happens entirely on the Raiser's Edge side — an RE admin reviews the batch, confirms the gift details are correct, and approves it.

Full guide: Reviewing and committing gift batches in Raiser's Edge NXT

The Raiser's Edge account connected to Almabase needs to have Solutions Admin access. If permissions are missing, the sync will fail with an error.

If gifts fail to sync — because of a missing System Record ID, an invalid fund ID, an unmapped donor, or a campaign date mismatch — the system flags them in the Errors section of your gift list. You can fix most issues directly and re-run the sync without creating duplicates.

Full guide: Handling gift sync errors

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.

Mapping cannot be skipped.

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 may be all you need. If you do use RE NXT, you'll likely want to push contact details and sync the gifts as well.

Not strictly. Pushing contact details to Almabase profiles, pushing them onward to your CRM, and syncing gifts are all independent. If you plan to use gift sync metadata (campaign, appeal, package codes), it's easiest to configure that before you start syncing — but it's not required, and you can always set or change those codes at the gift or list level.

No — syncing gifts and pushing contact details are independent paths. But mapping is still required. And if donors shared updated contact information during the giving process, it's worth reviewing that data too, since it's already captured.

Both use the same gift list process. With Stripe, when you sync the first recurring gift payment, the recurring gift record is automatically created on RE NXT — once you commit the batch, the payment is added to that record. With BBMS, it's a two-stage sync: the first sync pushes the recurring gift record, and after that batch is committed, you sync the list again to push the first payment. With both gateways, subsequent payments flow automatically after the initial sync is done.

Yes — you can include both types in a single gift list. If you're using BBMS, you'll need to sync the list a second time (after the first batch is committed) to push the recurring gift payments. The system automatically skips gifts that have already been synced, so there's no risk of duplicates.

The system displays the specific error on the gift list. Common causes include missing constituent mappings, invalid fund IDs, or campaign/appeal date mismatches. You can fix the errors directly from the gift list and re-run the sync for the failed gifts.