Skip to content
English
Submit a Support Request
  • There are no suggestions because the search field is empty.

Raiser's Edge NXT Field Mapping

How data is mapped from iDonate to Raiser's Edge NXT.

This article documents how data from iDonate is mapped into Blackbaud Raiser's Edge NXT (RENXT).

Object Mapping

iDonate Object RENXT Object
Donors Constituents
Designations Funds
Campaigns Campaigns
Donations Gifts
Recurring Schedules Recurring Gifts
Recurring Donations Recurring Gift Payments

A donation split across several designations becomes one gift with several gift splits in RENXT, not one gift per designation. A donor-covered fee may post as an additional gift depending on your Donor Fee Processor setting. See Donor Fees below.

Constituent Fields

RENXT Field Notes
First Name The donor's first name as entered on the giving form.
Last Name The donor's last name as entered on the giving form.
Email Address The donor's email. Also used to match donors to existing constituents. See How Donors Are Matched below.
Address Street, city, state, and postal code from the donation.
Phone Added as a new phone, or written over the existing primary phone, depending on the Replace Existing Phone Number setting.
Constituent Custom Field The iDonate donor ID, written for reference so you can trace a constituent back to the iDonate donor record. Requires the custom field to exist in your environment; see the note below.

The Lookup ID on the constituent is never overwritten by this integration. Whatever your organization already uses it for is left alone.

The donor ID custom field must already exist in your RENXT environment to be populated. Matching a returning donor does not depend on it, so donations post normally either way. Automatic provisioning of this field is coming soon.

How Donors Are Matched

Before any gift is created, the donor is resolved to a single constituent in this order:

  1. Previously synced donor. A donor who has given before is matched to the constituent they were matched to last time.
  2. Email. An exact email match on exactly one constituent.
  3. Name. An exact first and last name match. If more than one constituent matches, email is used to narrow it, and then city, state, and postal code.

If no constituent matches, a new one is created.

Each step is decisive. If a donor's email matches two constituents, the donation is held for review rather than falling through to name matching, because an email shared by two records is exactly the duplicate situation that needs a human decision. The same applies when name and address matching cannot narrow to one record.

Held donations are not posted, and each candidate constituent is flagged with a Constituent Action for your team to review and merge.

Because a returning donor is matched to the constituent recorded at the time of their last gift, deleting or merging away a constituent that iDonate has already given to can send a later gift to a record you no longer expect. If a donor's gifts stop landing where they should after a merge or cleanup, contact iDonate Support so the donor can be re-matched.

Gift Fields

RENXT Field Notes
Constituent The constituent the donor was matched to, or the one created for them.
Amount The donation amount. Includes the donor-covered fee when Donor Fee Processor is set to Rollup.
Gift Date The date the donation was made in iDonate.
Gift Post Date Set to the same date as the Gift Date.
Lookup ID The iDonate transaction ID. This is how a gift is traced back to its donation in iDonate reporting.
Gift Type One-Time for a single donation, Recurring Gift for a schedule, and Recurring Gift Payment for each charge against a schedule.
Payment Method Mapped from the iDonate payment method. See the table below.
Gift Splits One split per designation on the donation. See Gift Split Fields below.
Gift Custom Fields Whatever you configure in Custom Field Mapping. See below.

Gift Split Fields

RENXT Field Notes
Amount The amount the donor gave to that designation. In Rollup mode, each split also carries its proportional share of the donor-covered fee.
Fund Resolved from the iDonate designation. See Designation to Fund Resolution below.
Campaign Resolved from the iDonate campaign by name, or your configured Default Campaign. Setting a Default Campaign is recommended.

Designation to Fund Resolution

Each designation on a donation is resolved to a RENXT fund in this order:

  1. Lookup ID. A fund whose Lookup ID is the iDonate designation ID.
  2. Name or description. A fund whose name or description matches the designation's code or title.
  3. Created. A new fund is created. The new fund's Fund ID is that code, so later donations to the same designation match it by name.
  4. Default Fund. If none of the above produce a fund, the configured Default Fund is used.

If a designation matches more than one fund, at either the Lookup ID or the name step, the donation is held rather than posted to a guess. Two funds sharing a name, or sharing a Lookup ID, are worth cleaning up in RENXT.

RENXT requires a fund on every gift split. If a designation cannot be resolved and no Default Fund is configured, the gift does not post. Configuring a Default Fund keeps donations flowing while your team reconciles the designation later.

Payment Method Mapping

iDonate Payment Method RENXT Payment Method
Credit Card Credit Card
e-Check / ACH Direct Debit
Check Check
Cash Cash
Other Other

PayPal and Venmo are not yet mapped. RENXT accepts a fixed list of payment methods, and whether it accepts these two is still being confirmed with Blackbaud. If your organization takes donations through PayPal or Venmo, raise it with iDonate Support before going live so those donations are handled deliberately rather than failing to post.

Recurring Gifts

A recurring schedule in iDonate becomes two kinds of record in RENXT: one Recurring Gift that holds the schedule, and one Recurring Gift Payment for each charge. The recurring gift itself carries no money; the payments record the cash received.

The recurring gift is created the first time the schedule charges, not when the donor sets it up. A schedule that has never charged has no record in RENXT yet.

Recurring Gift Fields

RENXT Field Notes
Lookup ID The iDonate recurring schedule ID.
Amount The scheduled gift amount. Updated when the donor or your team changes the amount in iDonate.
Frequency Mapped from the iDonate schedule frequency. See Frequency Mapping below.
Start Date The schedule's start date.
Gift Status Active while the schedule is running and Terminated once it is cancelled in iDonate.
Payment Method Other. The schedule is recorded as manually processed because iDonate, not Blackbaud, charges the donor.
Post Status Do Not Post, since the recurring gift represents the schedule rather than a receipt of funds.

Because iDonate processes the charges, these recurring gifts are recorded as externally processed. Do not attach a Blackbaud Merchant Services payment configuration to them or expect RENXT to generate the charges.

Frequency Mapping

iDonate Frequency RENXT Frequency
Weekly Weekly
Every 2 Weeks Every Two Weeks
Monthly Monthly
Quarterly Quarterly
Annually Annually

Recurring Gift Payment Fields

Each charge against a schedule posts as a Recurring Gift Payment linked to the recurring gift. It carries the same fields as a one-time gift, including the amount charged, the gift date, the iDonate transaction ID as its Lookup ID, and the gift splits, and it is placed in a batch or created directly according to your Posting Mode.

Refunds and Cancellations

iDonate Event RENXT Behavior
Refund The original gift is located by its Lookup ID and adjusted to its new total using a gift adjustment. A partial refund reduces the gift by the refunded amount; a full refund brings it to zero.
Cancellation, uncommitted batch The gift is removed from the batch before it is committed, so it never becomes a gift record.
Cancellation, committed batch or Direct mode A note is added to the constituent recording the cancellation.

Gift Custom Fields

iDonate values that have no standard home on a RENXT gift can be written to gift custom fields through Custom Field Mapping in the Config Wizard. Each row pairs one iDonate source field, such as the transaction ID or transaction set ID, with one RENXT gift custom field category. The available source fields are listed in the mapping form, and the target categories are read live from your environment.

A gift custom field category must already exist in your RENXT environment before it can receive data. Mapping to a category that has not been created will not create it.

To connect the integration and configure these behaviors, see Setting Up Raiser's Edge NXT. For the access the integration needs, see Raiser's Edge NXT Permissions.