Skip to main content

What Data Syncs from Almabase to Raiser's Edge NXT

A complete reference of every gift field that syncs to RE NXT, where each one is configured, and what stays in Almabase only.

Written by Sarita Markande

When you sync gifts from Almabase to Raiser's Edge NXT, the system pulls data from three places in Almabase to build the gift record in RE NXT:

Gift Sync Metadata — campaign-level defaults configured on the giving page (e.g., campaign, appeal, package, and the fund for donor-covered transaction charges).

Gift List level — defaults you set when preparing a gift list for sync. These apply to all gifts in the batch that don't already have values set at a higher level. This is also where custom fields are configured.

Individual Gift level — donor and gift-specific fields that come directly from the gift itself (amount, fund, date, etc.).

When the same field is set at more than one level, the most specific value wins: page-level metadata overrides gift list defaults. See Setting Up Campaign, Appeal, and Package Codes for a detailed explanation of this hierarchy.

Gift Fields That Sync

The table below lists every field that can be pushed from Almabase to RE NXT during gift sync.

Field

Where Configured in Almabase

Donor's Constituent Record

Individual Gift (matched by System Record ID)

Currency

Individual Gift

Gift Amount

Individual Gift

Gift Date

Individual Gift

Fund

Individual Gift

Anonymous Flag

Individual Gift

Payment Mode

Gift List

Campaign

Gift Sync Metadata / Gift List

Appeal

Gift Sync Metadata / Gift List

Package

Gift Sync Metadata / Gift List

Gift Type

Gift List

Gift Subtype

Gift List

Post Status

Gift List

Post Date

Gift List

Receipt Status

Gift List

Acknowledgement Status

Gift List

Soft Credits

Gift List

Donor-Covered Transaction Charges Fund

Gift Sync Metadata

RE NXT Custom Fields

Gift List (Custom Fields tab)

BBMS-Only: Card Payment Details

If your payment gateway is BBMS (Blackbaud Merchant Services), the following additional payment details are included automatically when gifts sync. These are not configurable — they are pulled directly from the payment transaction.

Field

Notes

Cardholder Name

Name on the card used for the transaction

Card Type

Visa, Mastercard, etc.

Card Expiry Date

Expiration date of the card

Authorization Code

Payment authorization reference

These fields help with payment reconciliation and auditing in RE NXT. This applies to BBMS only; Stripe transactions do not include these fields.

Gift Data That Does Not Sync

Field

Why It Doesn't Sync

Tribute Gifts

Not currently supported for sync

Matching Gifts

Not currently supported for sync

Gift Notes

Stays in Almabase only

UTM Source, Medium, Campaign

Almabase analytics data — used for tracking campaign performance in Almabase, not relevant to RE NXT

Giving Page Name

Almabase context only — used to identify where the gift came from within Almabase

FAQs

Q: Which fields are required for a gift to sync successfully?

Only two things are required: the donor must be mapped to a constituent with a valid System Record ID in RE NXT, and the fund must have a valid External Database ID. If either is missing, the gift won't sync — but the system catches this during validation and shows a specific error so you can fix it before syncing. Everything else — gift type, subtype, payment mode, post status, and all other fields — is optional.

Q: Do donor contact details update the constituent record in RE NXT when gifts sync?

No — gift sync pushes gift data to RE NXT, not constituent updates. To push contact detail updates to constituent records, that's handled separately through the connector rules and Data Inbox process.

Q: I use Stripe, not BBMS. Am I missing any fields?

The card payment details (cardholder name, card type, expiry, authorization code) are BBMS-only. All other fields in the table above sync the same way regardless of your payment gateway.

Q: What about recurring gifts — do the same fields apply?

Yes. Recurring gifts sync the same fields as one-time gifts. The difference is in how the sync works (Stripe requires one sync cycle; BBMS requires two), not what data is sent. See Syncing Recurring Gifts to RE NXT for details.

Q: Where can I see which batch a gift was added to?

Open the gift in the gift list, click Edit gift details, and scroll to Sync Details — the batch number is shown there.

Did this answer your question?