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

Setting Up Raiser's Edge NXT

How do I integrate with Raiser's Edge NXT?

This article guides through how to connect iDonate to Blackbaud Raiser's Edge NXT (RENXT), configure settings, and manage the connection over time.

Prerequisites

Before beginning, make sure you have:

  1. Access to an iDonate Admin user.
  2. A RENXT subscription with SKY API enabled.
  3. A RENXT user who can authorize the connection and who holds the required permissions. See Raiser's Edge NXT Permissions.

This integration requires RENXT. Organizations still running a database-only version of Raiser's Edge (such as RE7) or a desktop plug-in cannot connect until they have moved to NXT with SKY API.

Connecting to RENXT

  1. In iDonate, navigate to Settings > Integrations.
  2. Click Raiser's Edge NXT from within the Marketplace, which will open the RENXT Config Wizard.
  3. Click Configure.
  4. On the Connection page, click Connect. A Blackbaud sign-in window opens.
  5. Sign in as the RENXT user who will authorize the integration, then approve the requested access. You are returned to the Config Wizard with the connection established.
  6. Click Next to continue to the configuration steps.

The connection is tied to the authorizing user. If that user is deactivated, loses required permissions, or has their Blackbaud access reset, access to RENXT stops until the connection is re-authorized. It is recommended to authorize with a dedicated integrations user rather than an individual's account.

Configurations

The following configurations determine how data flows and behaves within your RENXT integration. Review each setting carefully as they directly impact how information is processed and synced.

Processing

  1. Donor Fee Processor: Determines how donor fees are processed.
  2. Donor Fee Fund: The fund that will receive all donor covered fees. Required if "Donor Fee Processor" is set to "Standard". Defaults to "Standard".

Posting Mode

Determines how gifts arrive in RENXT.

  • Batch: Stages each gift into a RENXT gift batch so your team can review and commit it. Recommended for organizations that reconcile before posting.

  • Direct: Creates the gift record immediately with no batch review step.

Batch Settings

In Batch mode you can expect up to three iDonate batches types: one for one-time gifts, one for recurring schedules, and one for recurring payments. Each batch description will follow the format of iDonate - {batch type} - {batch created date} (e.g iDonate - Recurring Payments - 2026-08-24).

Batches created by the integration are Web View batches, which is how records written through Blackbaud's API arrive. They are committed the same way as any other gift batch, though where they appear may differ from batches your team creates in Database View.

Additional Settings

  1. Default Fund: When a donation occurs and does not have an associated designation, the export will use this designation when exporting to your CRM.
  2. Label Donation Source as Beta: Tags batch descriptions with "Beta" and routes them to their own batch so test gifts are easy to remove (e.g. iDonate - Recurring Payments Beta - 2026-08-24).
  3. Replace Existing Phone Number: Replaces a donor's phone number instead of adding a second one. Off by default.
  4. Donor ID Custom Field Category: RENXT custom field for storing each donor's iDonate ID as a cross-reference. Must already exist in RENXT; blank to skip.

Custom Field Mapping

This step lets you send iDonate values into gift custom fields in RENXT. You build a list of rows, where each row maps one iDonate source field to one RENXT gift custom field. If you add no mappings, nothing changes and your gifts behave exactly as before.

  1. Field Mappings: Add a row, then pick the iDonate Source Field to send, such as the designation name or transaction id, and the Raiser's Edge NXT Custom Field to write it to.
  2. Custom Field: The dropdown lists the gift custom field categories found in your Raiser's Edge NXT environment. If the category you need is not listed, you can type its name directly.

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

After reconfiguring any settings in the Config Wizard, be sure to click Finish on the final step. Changes are only saved once you complete the wizard by selecting Finish.

Duplicate Donors

When a donation cannot be resolved to a single constituent because two or more records look like the same person, iDonate does not guess and does not create a third record. Instead:

  1. The donation is held rather than posted.
  2. A Constituent Action is added to each candidate record so your team knows to review them. These appear on the constituent record, and in Portfolio > Action List > Build New List.
  3. After your team merges the duplicates in RENXT, the held donations post automatically on the next scheduled retry. No resubmission is needed.

A donor with several held donations is flagged once, not once per donation, so review tasks do not pile up. All of that donor's held donations are released together once the duplicates are merged.

The integration keeps a record of which iDonate transactions have already been posted and checks it before creating any gift, so a retried or redelivered donation does not become a second gift.

Refunds and Cancellations

  • Refunds adjust the original gift to its new total, using Raiser's Edge NXT's own gift adjustment, so the change is recorded rather than hidden. Partial refunds reduce the gift by the refunded amount; full refunds bring it to zero.
  • Cancellations in Batch mode remove the gift from its batch, but only while that batch is still uncommitted. If the batch has already been committed, or the gift was posted in Direct mode, a note is added to the constituent instead so your team can decide how to handle it.

For a detailed breakdown of how iDonate data maps to RENXT records and fields, see Raiser's Edge NXT Field Mapping. To pause or deactivate this integration, see Managing an Active Integration in Integrations Overview.