Connect your Raiser's Edge NXT database to Avid so you can benchmark performance, build audiences, power playbooks, and calculate ROI with live gift, constituent, and appeal-expense data.
Use this article when
- You are ready to connect Raiser's Edge NXT as your primary CRM in Avid.
- You are an NXT administrator, or you can work with one, to install the Avid app.
- You want to understand which NXT permissions are required for a successful Avid connection.
- You want Avid to pull your appeal and package expenses from NXT so ROI appears in the Matchback report without a separate cost-file upload.
- You want to map, filter, or categorize gifts by their linked Events, Pledges, Proposals or Opportunities, or Planned Gifts in your Transactions data set.
- You want Avid to remove records from your data when they are hard-deleted in NXT (for example, deleted through Database View).
Applies to and prerequisites
| CRMs | Raiser's Edge NXT (RE NXT) |
| Avid areas | Settings → Connections / Avid AI Integration Checklist |
| Recommended roles | Blackbaud administrator or NXT user with required view and query permissions |
| Estimated time | 10–20 minutes to authenticate; up to 24 hours for first data sync |
Optional configuration
Spouseholding is an optional mapping configuration for Raiser's Edge NXT. It is not the default because it can change donor counts and confuse users who expect an individual-level model. If you want Avid to treat households as the primary donor record, use the spouseholding mapping guide. Enable spouseholding for Raiser's Edge NXT. This configuration changes how records roll up and can affect dedupe behavior, so validate donor counts after you enable it.
Required NXT permissions for the authenticating user
The Raiser's Edge NXT user who authenticates the Avid connection must have View access to these objects (including any custom fields):
- Gifts (including Custom Fields)
- Constituents (including Codes, Address, Email, Phone, Relationships, and Custom Fields)
- Fundraising (including Campaigns, Funds, Appeals, Packages, Expenses, and Custom Fields)
The following objects are also supported when the modules are enabled in NXT and the authenticating user has access:
- Events
- Memberships
We highly recommend that the authenticating user also has the NXT permission Analysis – Query – Export. Several important data points are only available through Query, including:
- Solicit codes
- Salutation / addressee
- Recurring gift details
- Tribute details
- Appeal and package expenses (required for ROI in the Matchback report)
- Linked Event, Pledge, Proposal/Opportunity, and Planned Gift fields on Gifts (required to categorize gifts by linked records in your Transactions data set)
- Hard-deleted record detection for Gifts, Constituents, and Addresses (required to remove records from Avid when they are hard-deleted in NXT)
If the user does not have these permissions, Avid may connect but key fields, including costs, linked-record details, and hard-delete signals, will be missing from your data.
Steps
-
Open Avid settings.
In Avid, go to Settings. You can also open the Avid AI Integration Checklist from the home screen. -
Go to CRM connections.
Do one of the following:- In the checklist, click CRM, then click Connect your CRM, or
- In Settings, open the connections area, click the Add button, then choose System.
-
Select Raiser's Edge NXT.
Find the Raiser's Edge NXT tile and click it. -
Install the Avid app from the Blackbaud Marketplace.
Blackbaud requires that apps authenticate through its marketplace. Open the Avid listing: Avid AI in the Blackbaud Marketplace.- If you are not a Blackbaud admin, send this link to your NXT administrator and ask them to complete the install.
- If you are the administrator, continue with the steps below.
-
Authorize the app in Blackbaud.
On the Marketplace page:- Click Get started.
- Sign in to Raiser's Edge NXT if prompted.
- Review the requested permissions.
- Click the button to authenticate and install the application.
-
Return to Avid and complete authentication.
Go back to the Avid browser tab and your NXT connection screen. Click Authenticate. Use the NXT user with the required View and Analysis – Query – Export permissions when prompted. -
Confirm that the initial data sync starts.
Stay on the connection page or open any Avid benchmark or Insights page tied to CRM data. -
Allow time for data to backfill.
The first full sync can take up to 24 hours, depending on your data size.
What you'll see after connecting
- Your NXT connection shows as Connected in Avid settings.
- Benchmarks and Insights begin to populate with gift, constituent, and fundraising data from NXT.
- Appeal and package expenses sync from NXT automatically (see below), so ROI populates in the Matchback report without any additional upload.
- If Events or Memberships are enabled and included, related data becomes available in relevant Avid views after sync.
- Avid will prompt you to review column mappings and confirm default settings when your data is ready.
- When you open the column mapping screen for the Transactions data set, you see new groups of linked-record fields on Gifts (see Categorize gifts using linked Events, Pledges, Proposals, and Planned Gifts).
- Records that are inactivated or hard-deleted in NXT drop out of your Avid data on the next sync (see How Avid handles deleted records in NXT).
Cost and ROI data from NXT
Avid pulls your appeal and package expenses from Raiser's Edge NXT automatically on every sync. You do not need to upload a separate cost file. This is the easiest path to see ROI in the Matchback report.
What syncs
For each appeal (and, when present, each package within that appeal), Avid pulls the values recorded on the Appeal > Expenses record in NXT:
| NXT expense field | How Avid uses it |
|---|---|
| Actual expense amount | Treated as the cost in the ROI calculation: (Revenue − Cost) ÷ Cost × 100. |
| Budgeted expense | Stored for reference. Not used in ROI by default. |
| Expense type, date, comment, package | Stored alongside the expense so you can verify which appeal and package the cost belongs to. |
Requirements
- The authenticating NXT user has the Analysis – Query – Export permission. Expenses are pulled via NXT Query, so this permission is required.
- Appeal expenses are recorded in NXT. Empty appeals produce no cost and no ROI.
- Appeal codes on your gifts match the appeal the expense is tied to. (This is the standard NXT behavior; no extra setup.)
Where to see it in Avid
- The Matchback report displays ROI and Net Revenue columns on the Results and Package Results tabs for appeals that have expenses in NXT. See Run a Matchback report.
- Cost data refreshes alongside the rest of your NXT sync (typically daily).
If you use Raiser's Edge NXT but ROI is not populating, start with the Matchback report's Why don't I see ROI metrics? diagnostic. In most cases, either the expense record is missing in NXT or the authenticating user does not have Query permission.
Categorize gifts using linked Events, Pledges, Proposals, and Planned Gifts
Avid surfaces details about records that are linked to a gift in NXT so you can map, filter, segment, and categorize transactions by what they fund. These appear on the column mapping screen for the Transactions data set, grouped under field names like Linked Events, Linked Pledge, Linked Proposal/Opportunity, and Linked Planned Gift.
Once mapped, these fields are available everywhere a Transactions field is available in Avid, including audience filters, playbook conditions, and exports to integrated systems.
What is available
| Linked record on a gift | What Avid surfaces |
|---|---|
| Linked Events | Key event details (such as event name, type, group, and category) for any events the gift is linked to in NXT. |
| Linked Proposal/Opportunity | Key proposal or opportunity details (such as name, status, and category) for any proposals or opportunities the gift is linked to. |
| Linked Planned Gift | Key planned-gift details for any planned gift the gift is linked to in NXT. |
| Linked Pledge | Key pledge details, plus a subset of the pledge's designations and the values from any Event, Proposal/Opportunity, or Planned Gift the pledge itself is tied to. |
One-to-many relationships
A single gift can be linked to more than one event, proposal, planned gift, or pledge in NXT. When that happens, Avid surfaces the values as a pipe-separated list in the field. You can filter or match against the pipe-separated string to find any gift whose linked records include a specific value.
For example, a gift linked to two events shows both event names in Linked Events > Event Name, separated by |.
Pledges and Inclusion / Exclusion filters
Linked Pledge fields populate on a gift even when your Inclusion / Exclusion filters suppress Pledges as their own row in the Transactions data set. The pledge details are read from the linked record, not from a separate pledge row, so excluding pledges from transactions does not hide the pledge context on the gifts that paid against them.
Requirements
- The authenticating NXT user has the Analysis – Query – Export permission. These fields are pulled via NXT Query.
- The relevant module is enabled in your Raiser's Edge NXT subscription (for example, Events for Linked Events, or Prospect Research Management for Proposals, Opportunities, and Planned Gifts).
- The linked records exist in NXT. Avid surfaces values that are populated on the source record. Empty fields stay empty.
Where to see it in Avid
- In Avid, go to Settings and open your Raiser's Edge NXT connection.
- Open the column mapping screen for the Transactions data set.
You see new groups of fields with names that begin withLinked(for example,Linked Events,Linked Pledge,Linked Proposal/Opportunity, andLinked Planned Gift). - Map the fields you need to your Avid Transactions schema, then save the mapping.
The mapped fields become available in audiences, playbooks, exports, and any other surface that reads Transactions.
LockStep insight
Linked-record fields are the cleanest way to split Annual Giving from Major Giving, planned-giving programs, event-driven revenue, and partnership or pass-through gifts. Map a small number of high-signal fields first (such as Linked Proposal/Opportunity > Status, Linked Planned Gift > Type, Linked Events > Group, and Linked Pledge > Designation), then build a categorization rule on top of those mapped fields rather than re-deriving categories from gift codes alone.
How Avid handles deleted records in NXT
Raiser's Edge NXT lets users remove records in two different ways, and Avid handles each one differently.
Inactive records (NXT Web View)
The newer NXT Web View typically does not delete records outright. Instead, users mark them as Inactive using the inactive flag on the record.
Avid always reads the inactive flag, regardless of whether the authenticating user has Query permission. Inactive records sync into Avid with their inactive status preserved so you can include or exclude them in audiences, segments, and reporting.
Hard-deleted records (NXT Database View)
NXT Database View (the older desktop-style interface) allows users to permanently remove a record from the database. This is called a hard delete. Once a record is hard-deleted in NXT, it no longer exists in the API and standard incremental syncs cannot tell that it ever existed.
Avid uses NXT Query to detect hard deletes. When the authenticating user has the Analysis – Query – Export permission, Avid compares the live record set to what it has previously synced and removes records from your Avid data when they have been hard-deleted in NXT.
Hard-delete detection currently supports these record types:
- Gifts
- Constituents
- Addresses
Support for additional record types (such as Phones and Emails) is on the roadmap and will be added without additional configuration on your side.
Requirements
- The authenticating NXT user has the Analysis – Query – Export permission. Without it, Avid cannot detect hard deletes and previously synced records will remain in your Avid data even after they are removed from NXT.
- The connection is healthy and has completed a recent sync. Hard-delete detection runs on the same schedule as the rest of the NXT sync.
What you see after a delete
- If a constituent is marked Inactive in NXT Web View, the constituent record stays in Avid with the inactive flag set.
- If a gift, constituent, or address is hard-deleted in NXT Database View and the connection has Query permission, the record is removed from your Avid data on the next sync.
- If a record type is hard-deleted but is not yet supported by hard-delete detection (for example, a phone number), the value may persist in Avid until it is overwritten by a later sync of the parent record.
LockStep insight
If your team uses Database View to clean up duplicate constituents or correct gift entry errors, granting Analysis – Query – Export to the Avid integration user is the only way to keep your Avid audiences and reports aligned with NXT. Without it, audience counts, lifetime value, and matchback results can drift over time as deletions accumulate.
Next steps and related tasks
- Review and adjust CRM column mappings when Avid prompts you, including the new
Linkedfield groups on Transactions. - Configure audiences and playbooks that depend on NXT data once the first sync completes.
- Run the Matchback report to see appeal performance, including ROI from NXT expenses.
- If you decide you cannot make a direct NXT connection, use secure file uploads or sFTP instead: When should I use file uploads?
Notes and limits
- Avid can only import data the authenticating NXT user can see. If key fields are missing, review that user's permissions first.
- Some fields and behaviors (including solicit codes, salutations, recurring gift details, tribute details, appeal and package expenses, Linked Event, Pledge, Proposal/Opportunity, and Planned Gift fields on Gifts, and hard-delete detection for Gifts, Constituents, and Addresses) are only available via NXT Query. Without Analysis – Query – Export, those fields and behaviors, including cost data for ROI, linked-record context for categorization, and removal of hard-deleted records, will not appear in Avid.
- Linked-record fields surface what NXT returns for the linked record. If a linked record is missing or hard-deleted in NXT, the corresponding fields on the gift will be empty.
- One-to-many linked records are returned as pipe-separated lists. Build audience and playbook conditions using contains-style matches against the pipe-separated string rather than equality matches.
- Linked Pledge fields populate even when Pledges are suppressed by Inclusion / Exclusion filters on the Transactions data set.
- Hard-delete detection currently covers Gifts, Constituents, and Addresses. Other record types may be added over time without configuration changes on your side.
- The Inactive flag from NXT Web View is always honored, regardless of Query permission.
- If you change the NXT user or their permissions, you may need to re-authenticate the connection in Avid to refresh access.
- Events and Memberships data will only appear if your organization licenses those NXT modules and the authenticating user can view them.
- If expenses are recorded at the fund or campaign level in NXT but not at the appeal level, they will not appear in the Matchback report. ROI is calculated against appeal-level expenses.