RE NXT to Version2 Mapping
Understanding which RE NXT data fields are included in the Version2 integration and how they map to Version2.
How to use this article
Version2 uses Blackbaud’s SKY API to retrieve portfolio, constituent, contact, and giving data from your RE NXT environment.
The connection is one-way and read-only. Version2 retrieves configured data from RE NXT but does not write data back to your RE NXT database through the API.
During onboarding, your team will complete the RE NXT Customer Configuration Template. Your selections determine how certain data is filtered, mapped, or interpreted by Version2. Once you provide this template back to Version2, all mapping and setup is handled completing by your Version2 onboarding team.
Tip: Keep this article open while completing your configuration template. For more information about the configuration process, see Configure Your Version2 - RE NXT Integration.
Name and demographic data
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | Lookup ID | CRM_ID |
| Constituent | First Name | FIRST_NAME |
| Constituent | Last Name | LAST_NAME |
| Constituent | Primary Constituent Code | AFFILIATION |
| Constituent | Preferred Name | PERSONALIZATION |
| Constituent | Birthdate | BIRTHDATE |
| Fundraiser Assignment | Fundraiser ID | PORTFOLIO |
Portfolio mapping: The Fundraiser ID is mapped to a Version2 portfolio name based on the selections in your organization’s configuration.
Address data
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | Line 1 | HOME_ADD1 |
| Constituent | Line 2 | HOME_ADD2 |
| Constituent | Line 3 | Added to HOME_ADD2 |
| Constituent | City | HOME_CITY |
| Constituent | State | HOME_STATE |
| Constituent | Zip | HOME_ZIP |
| Constituent | Country | HOME_COUNTRY |
Address Line 3: If Line 3 contains a value, Version2 adds it to the end of HOME_ADD2, separated by a comma.
Email data
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | PREFERRED_EMAIL |
Phone data
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | Phone | CELL |
Giving data: constituent-level fields
These fields provide giving information associated with the constituent record.
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | Lifetime Giving | LIFETIME |
| Gifts | Amount | LAST_GIFT_AMOUNT |
| Gifts | Date | LAST_GIFT_DATE |
| Gifts | Fund(s) | LAST_GIFT_DESIGNATION |
| Gifts | Gift Type | RECURRING |
| Gifts | Gift Amount/Soft Credit Amount | FY0_TD |
| Gifts | Gift Amount/Soft Credit Amount | FY_1 |
| Gifts | Gift Amount/Soft Credit Amount | FY_2 |
| Gifts | Gift Amount/Soft Credit Amount | FY_3 |
Last gift designation: If a gift has multiple designations, Version2 combines them in LAST_GIFT_DESIGNATION and separates each value with a | .
Recurring gifts: RECURRING is set to True when the RE NXT Gift Type is Recurring Gift or Recurring Gift Payment.
Giving data: individual gift transactions
These fields are mapped for individual gift transactions retrieved from RE NXT.
| RE NXT Category | RE NXT Field | Version2 Field |
|---|---|---|
| Constituent | Lookup ID | CRM_ID |
| Gifts | Composite transaction identifier | GIFT_ID |
| Gifts | Gift Type | GIFT_TYPE |
| Gifts | Gift Amount/Soft Credit Amount | GIFT_AMT |
| Gifts | Gift Date | GIFT_DATE |
| Gifts | Fund | GIFT_DESIGNATION |
| Gifts | Gift Type | RECURRING |
Gift ID: Version2 creates GIFT_ID using the credit recipient system ID, gift system ID, and either h or s to identify hard or soft credit status. The values are separated by | .
Gift designation: If a gift has multiple designations, Version2 combines them in GIFT_DESIGNATION and separates each value with a | .
Recurring gifts: RECURRING is set to True when the RE NXT Gift Type is Recurring Gift or Recurring Gift Payment.
Custom Fields
If your organization would like to include additional data points beyond the standard fields provided through the integration, work with your Version2 onboarding manager to identify the corresponding field in RE NXT and confirm how it should be used in Version2.
Your team will then complete and submit a one-time Custom Field Submission Template CSV. This template provides the field context Version2 needs to interpret and configure the custom field correctly, including what the field represents and how it should be applied.
Related articles
- How the Version2 - RE NXT Integration Works
- Configure Your Version2 - RE NXT Integration
- Connect Version2 to Blackbaud RE NXT
Questions?
Contact your Version2 onboarding representative or email version2support@givzey.com.