Enhanced Constituent Import allows for importing a broader set of data from NXT into GiveCampus. This includes multiple email addresses, phone numbers, and physical addresses.
Enhanced Constituent Import
To access the integration head into your School Dashboard > Integrations > Blackbaud RE NXT
Under the import configuration tab, you'll be able to enable 'Include Enhanced Constituent Data'.
Once enabled, you'll see the option to map various additional fields to the configuration.
Enhanced constituent data is imported nightly. The first import happens the night after the integration is enabled.
Import Field Mapping
Constituent Identity & Names
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| Lookup ID or System ID | Constituent ID (Unique Identifier) | Configurable per school |
| First Name | First Name | |
| Middle Name | Middle Name | |
| Last Name | Last Name | |
| Preferred Name | Preferred First Name | |
| Suffix | Suffix | |
| Former Name | Former Last Name | |
| Birth Date | Birth Date |
Education
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| Class Year* (from primary Education record) | Class Year | 2-digit years expanded using class-year cutoff setting |
*In order to import Class Year from RE NXT you must use RE's Alumni module. Without it, this field won't import.
Email Addresses
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| All active emails | Email Addresses (list) | |
| NXT "Primary" email | Preferred Email | |
| NXT type mapped to "Business" | Business Email | School-configured type mapping |
| NXT type mapped to "Other" | Other Email | School-configured type mapping |
Phone Numbers
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| NXT type mapped to "Preferred" | Preferred Phone | School-configured type mapping |
| NXT type mapped to "Cell" | Cell Phone | School-configured type mapping |
| NXT type mapped to "Home" | Home Phone | School-configured type mapping |
| NXT type mapped to "Work" | Work Phone | School-configured type mapping |
Unmapped phone types are skipped.
Addresses
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| All addresses (multiple per constituent) | Addresses (list) | |
| NXT "Primary" address | Preferred Address | |
| Address Type | Address Type |
Constituency Codes (Affiliations)
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| Constituency Code | Affiliation | Multiple per constituent supported |
| Start Date / End Date | Used to determine active vs. inactive | Expired codes (end date < today) or codes flagged inactive in NXT are excluded |
Custom Fields
Custom fields imported from Blackbaud Raiser's Edge NXT sync into GiveCampus in a consistent format. We support string, boolean, date, number, multi-value, and selected-list value types.
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| School-selected NXT custom fields | Custom Fields | Schools choose which fields to import |
- Multiple-value fields import as text. Currency, number, or date fields with multiple values per constituent also import as text. These fields can’t be totaled, filtered by range, or used in advanced search or segments. To keep a field numeric or date-based, limit it to one value per constituent in Blackbaud.
- GiveCampus mirrors Blackbaud. Each sync updates GiveCampus to match Blackbaud. Edits made in GiveCampus are replaced at the next sync, and deletions in Blackbaud are reflected in GiveCampus. Manually added or imported values remain unchanged.
- Keep your Blackbaud data clean. Values that don't match their field type (like "N/A" in a number field) are skipped without error. For list fields, dropdown options must match exactly, so "Art" and "art" are considered different.
- Select sync options. New Blackbaud custom fields aren’t imported automatically. Choose which fields to import in integration settings. Renaming a field in Blackbaud adds a new custom field in GiveCampus.
Spouse
| NXT Field | GiveCampus Field | Notes |
|---|---|---|
| Spouse Constituent ID | Spouse (linked relationship) | |
| Spouse First Name | Spouse First Name | |
| Spouse Last Name | Spouse Last Name | |
| Spouse Birth Date | Spouse Birth Date | |
| Spouse Deceased | Spouse Deceased |
Notes
- Inactive constituents in NXT are skipped and not imported.
- Phone and email types that aren't mapped in your settings are ignored.
- Class year imports rely on the 2-digit cutoff setting (default: 50).
FAQ — How are spouse email addresses and phone numbers imported?
- The email and phone mapping controls on the Import Configuration tab (School Dashboard > Integrations > Blackbaud RE NXT > Import Configuration) apply only to the primary constituent record. There are no separate mapping options for a spouse's email or phone types.
- Spouse contact data is imported automatically only when the spouse exists in RE NXT as a separate, active constituent with its own contact data.
- When a spouse is imported as a separate record, only the Preferred Email and phone numbers (Cell Phone, Home Phone, and Work Phone) from the spouse’s own record are imported. Business Email and Other Email are not imported for spouse relationships. In that case, GiveCampus reads the spouse’s contact values from their own record and creates the linked spouse relationship accordingly.
- If the spouse does not exist as a separate record (for example, when a single shared RE NXT record is used for both partners), the spouse email and phone fields on the linked relationship remain empty.
- Next steps and options:
- To import separate contact details for each partner, ensure each has an individual, active constituent record in RE NXT. Their contact data will appear in GiveCampus on the next nightly enhanced import.
- If your household uses a shared RE NXT record, the shared record's email and phone values will import per the primary constituent mappings. There is no UI option to split a shared record into two separate constituents.
- Spouse contact data is updated nightly along with other enhanced constituent imports.
FAQ — How does the Class Year Cutoff work and what value should I pick?
Where to find it:
In your admin, navigate to School Dashboard > Integrations > Blackbaud RE NXT and open the Import Configuration tab. With Enhanced Constituent Data Import enabled, scroll to the Class Year section. The field label is Class Year Cutoff with helper text: "Enter a two-digit year (e.g. 25 for 2025). Two-digit class years at or below this value will be treated as 21st century years." The default value is 50.
How it works:
GiveCampus expands a two-digit class year from RE NXT using your cutoff setting:
- Two-digit years less than the cutoff use the "20" prefix (e.g. with a cutoff of 50, a year of 30 becomes 2030).
- Two-digit years greater than or equal to the cutoff use the "19" prefix (e.g. with a cutoff of 50, a year of 50 becomes 1950).
Examples:
- With a cutoff of 50: 00–49 become 2000–2049; 50–99 become 1950–1999. For instance, 30 imports as 2030, 49 as 2049, and 50 as 1950.
- With a cutoff of 29: 00–28 become 2000–2028; 29–99 become 1929–1999. For example, 28 becomes 2028 and 29 becomes 1929.
Choosing a cutoff:
- For schools with alumni from the 1930s or 1940s, select a cutoff lower than 30 (e.g. 29) so years in the 30–49 range are correctly interpreted.
- For schools with predominantly pre-2000 alumni, set the cutoff to 1 so nearly all two-digit years expand to the 1900s. (Entering 0 disables class-year processing.)
- For schools with many recent alumni and few older graduates, the default 50 is usually appropriate. Review outliers after import.
Additional considerations:
- Four-digit years (e.g. 1985 or 2005) are imported as entered and are not affected by the cutoff.
- The field accepts only numeric digits and a maximum of two characters. Leaving it blank or entering 0 disables processing.
- Blank or non-numeric values in RE NXT result in no class year being set.
Recommended workflow:
- Review a sample of two-digit class-year values in your RE NXT data.
- Choose and update the cutoff to ensure most values expand correctly (for example, 29 forces 29–99 to become 1900s, while 50 treats 00–49 as 2000s).
- Update the Class Year Cutoff field and click Update Settings. The nightly import will reflect your changes—spot-check a few records to confirm the correct expansion.
If issues persist, adjust the cutoff and allow the next nightly import to update the records.
Comments
0 comments
Article is closed for comments.