• Can I use Database View with this integration? The integration workflows will only be possible with RE NXT webview.  Batches created automatically via the GiveCampus direct integration will not automatically be visible in the database view (RE). They will be available in the web view (RE NXT). Once approved, the list of gifts will be visible automatically in your database view.
  • The System ID is what you should select if you are using the ID that can only be found in the Database view in RE NXT. This can be found in the Constituent View > System Record ID. This can also be found in the URL of the web base view of a specific constituent.
  • 
  • The Lookup ID is what you should select if you are using the ID that is visible within RE NXT web view listed as "ID"
  • 
  • For gifts that need to be reviewed before they are exported, the ID that you select during this initial setup will be the one we expect you to enter into the UI.
  • If you plan on importing additional data through the School Level Data Importer, you will need to be using the same ID that matches this integration so duplicate constituents aren't created in GiveCampus. If you are already using the Data Importer, we recommend looking at your current exports to see which ID is being used.Should we use System ID or Lookup ID? There are two options for what RE NXT ID you could be using. This is a required setting for the integration overall that is important for all other integration points and once you have set this, you will need to request help from GC support to adjust it after the fact.
• What ID is used to match designations in GiveCampus with the designations in NXT? When matching designations from your online gifts to your designations in NXT, the integration will look for the ‘Fund ID’ and match that to your GiveCampus Designation Backend IDs.  To avoid having to manually review gifts due to unknown designation IDs, the backend IDs in GiveCampus (school level settings > designations > backend ID) should be the same as the NXT ‘Fund ID’ which can be found within NXT > Gift Management > Funds > Fund ID. 
  
• What do I do if I don't see the Raiser's Edge NXT settings in GiveCampus?  The NXT integration does require an add on to your GiveCampus account. Please contact your Partner Success Manager for more details. 
  
• Who receives the notification email that gifts require review? Any Online Giving school admin with Deposit Notifications enabled will receive the email. This can be configured in Online Giving > Administrators > Notifications.

GIFT DATA

• What data is sent to RE NXT about the individual gifts in the batch? We currently send gift data to populate the following fields in NXT: Constituent, Amount, Gift Date, Mark as Anonymous, Gift Type, Payment Method, Appeal, Campaign, Fund, Acknowledgment Status, Receipt Status, Receipt Date, Post Date, and reference information (in the Comment field) such as the GiveCampus gift ID and write-ins designation information if chosen by the donor.
  • Appeal ID is populated based on the Unique Identifier selected within the individual campaign or giving form settings.  GiveCampus will automatically import a list of appeals from NXT and display these within the dropdown options within your GiveCampus campaign/form settings.
  • While tribute information does not automatically map to tribute information in NXT.  The In Honor of and In Memory Of fields will pull into the ‘Comments’ field in NXT when the standard fields are used in GiveCampus
•  What data is not sent to RE NXT? Currently, we do not send or populate constituent details such as affiliations, phone numbers, or addresses.  We also do not populate stripe deposit IDs or any custom form field data.
• How do soft credits work with this export? We currently do not do anything for soft credits from the GiveCampus side. Schools can determine their process for soft credits inside of functionality built into Raiser's Edge / NXT to automatically soft credit specific relationships between constituents in the database (This is something that can be set up in the database view of RE NXT and is done per relationship between constituents). Once a batch of gifts created from the GiveCampus integration is approved in RE NXT, those rules should take effect to attribute soft credit rules set up.
• How do split/multi-designation gifts work with the export? GiveCampus follows RE NXT's process and sends multi-designated gifts to the NXT integration as "split gifts" in RE.  
• How do pledges work with GiveCampus and NXT? Because there are still some limitations on how pledges are created and managed in NXT, we do not have the ability to send over a pledge gift and link it to a current pledge in RE NXT.  If a pledge is made on a GiveCampus pledge form (with future dates / no credit card / etc.) then the gift will not be sent over in the gift export.  Once the gift is made and processed, the gift will come through as a normal one-time gift in the gift export and appear in the relevant batch.

  Pledge payments and gift types

  Quick summary

  • Pledge payments from GiveCampus export to RE NXT as gifts with the type RecurringGiftPayment.
  • The integration does not support sending gifts as the NXT Pledge gift type.

  What this means for your workflow

  When a pledge payment is processed in GiveCampus, it is exported to RE NXT as a RecurringGiftPayment gift. This means the payment will not automatically link to an existing pledge record unless manually linked in RE NXT.

  Recommended workflow to link pledge payments to an existing pledge in RE NXT

  1. Create the pledge record in RE NXT, if it isn’t already present.
  2. When the first recurring payment appears in your NXT batch, review the payment’s reference information (the Gift’s comment field contains the GiveCampus donation ID).
  3. Add the recurring gift ID from that payment to the initial installment on the RE NXT pledge record.
  4. Subsequent recurring payments will then link automatically to that pledge.

  Practical notes and scenarios

  • If a donor sets up a pledge without an immediate payment (for example, future-dated installments or without a stored card), no pledge record exports until a payment is processed. When a payment does process, it is sent as a RecurringGiftPayment gift.
  • If recurring payments have already export as RecurringGiftPayment gifts and remain unlinked, adding the recurring gift ID to the initial installment will link future installments to that pledge.

  FAQ

  Q: Can GiveCampus send pledge payments as the NXT "Pledge" gift type so they auto-apply to pledges?

  A: No. Pledge payments export as RecurringGiftPayment gifts by design.

  Q: Is there any step in GiveCampus to change this behavior?

  A: No. To link pledge payments to an existing pledge in RE NXT, manually add the recurring gift ID to the pledge’s initial installment.

   

INTEGRATION FIELD MAPPING

GETTING THE MOST OUT OF YOUR INTEGRATION - Tips & Tricks 

• Matching between GiveCampus and NXT uses the Constituent ID and matching email.  In order to keep the most up to date constituent IDs in GiveCampus, we recommend enabling the Automatic Constituent ID Import during your integration setup.  This will import your constituent IDs, emails, and names from NXT on a nightly basis.
• If you choose not to enable the automatic import, it is recommended that you leverage the School Level Data Importer or the Reporting constituent ID upload to ensure those constituent IDs are uploaded into GiveCampus and avoid having to manually add IDs during the manual review gift process.
• For new donors (aka no record in NXT), gifts will show up in the ‘Gifts to Review’ section since GiveCampus is unable to match it to a NXT constituent.  We recommend using donation reports to create the new constituent records in NXT, then let the automatic constituent ID import run so the system can now match those gifts to the new constituent.
  • In September 2025 we updated the integration to add a 'Create Constituents' feature that allows you to create constituents in GiveCampus and push those directly to NXT. More info here.
  • If you choose to add the gifts manually to the new donor records during the record creation process, then you can  use the ‘Skip All’ button on the Gifts to Review page to clear out the gifts that have already been added to NXT
• Similarly, you can also use the ‘Refresh Gifts’ button to re-check the review gifts section for edits or updates you may have made within NXT and should no longer flag in GiveCampus.  For example, if you update a fund ID in NXT or you add a new email address to a constituent record, you can click the ‘Refresh Gifts’ button in GiveCampus after those updates are made to re-check those gifts in review and move them to Pending Export.
• There are two new reporting columns that we recommend adding to any GiveCampus donation reports you use (learn how to edit your reports here).  These fields will tell you which gifts in your donation reports were part of which batches if you ever need to triple check anything:

  Track which gifts have exported to RE NXT

  Use two reporting columns in your donation reports to quickly tell whether a gift has been exported to Raiser's Edge NXT. These fields enable easy filtering and grouping for reconciliation.

  • blackbaud_gift_export_batch_system_id: Displays the Blackbaud system ID of the export batch in RE NXT.
  • blackbaud_gift_export_batch_number: Shows the batch number for the exported gift.

  How to use these fields:

  1. Add the two columns to your donation report (located under the “RE NXT Integration” category).
  2. Confirm that exported gifts have populated batch columns.
  3. Group or sort your report by the batch number to review gift counts and totals. Use the system ID to match the GiveCampus batch with the corresponding batch in RE NXT.

  Tips:

  • After an export, run a report grouped by batch number to verify gift counts and totals.
  • Include the donation ID and batch columns in your exports to create an audit trail for finance or data teams.

  These reporting columns let you track export status directly from GiveCampus, simplifying your reconciliation process.

  • blackbaud_gift_export_batch_system_id
  • blackbaud_gift_export_batch_number