When syncing with Raiser's Edge NXT (RE NXT), we pull data to build five files: Constituent, Gift Transaction, Interaction, Proposal, and Portfolio Assignment. 

Below, we’ve outlined the fields available for mapping for each file type, as well as the fields not supported by RE NXT. We’ve also included links for each file that detail how EverTrue fields map to RE NXT fields during the Data Sync process.  

---

Configuring Your Constituent File with RE NXT

When configuring your Constituent file, you can choose to exclude deceased and/or inactive records. For details on how giving data is calculated, check out our article: Configuring Total Giving and Categorized Giving Data from Raiser's Edge NXT.   

• Supported EverTrue Fields: Unique Record ID, Prefix, First Name, Nickname, Middle Name, Last Name, Previous Last Name, Suffix, Gender, Graduation Year, Is Deceased?, Custom Field(s), Constituency, Sports/Athletics, Activities, Address Type, Line 1, Line 2, Line 3, City, State, Zip Code, Country, Is Primary?, Email Type, Email, Is Primary?, Phone Type, Phone Number, Is Primary?, Relationship Type, Relationship Full Name, Relationship Unique Record ID, Title, Company, School Name, Degree, Major(s), Graduation Year, Lifetime Amount, Largest Gift Amount, Largest Gift Date, Largest Gift Label, Last Gift Amount, Last Gift Date, Last Gift Label, Pledge Balance, Recurring Payment, Fiscal Year Giving Totals, Category Level, Lifetime Giving Amount, Largest Giving Amount, Largest Gift Amount, Largest Gift Date, Largest Gift Label, Last Gift Amount, Last Gift Date, Last Gift Label, Pledge Balance, Recurring Payment, Solicitor Name, Solicitor ID, Stage, Solicitor Type
• Unsupported EverTrue Fields: Ethnicity, Is Deleted?, Industry/Work, Function/Work, Solicitation Codes, Donor Score, Capacity Score, Engagement Score
• Field Mapping Guide

If your organization is using EverTrue’s Clarity dashboards, be sure to check out our Constituent File Guide to see what fields are required for Clarity! 

Configuring Your Gift Transaction File with RE NXT

If you need additional details on how gift transaction data is calculated, check out our article: Configuring Gift Transaction Data from Raiser’s Edge NXT.

• Supported EverTrue Fields: Gift ID, Donor Constituent ID, Donor Name, Amount, Date, Legal Credit, Gift Type, Transaction Type, Designation, Campaign Credit
• Unsupported EverTrue Fields: Designation Category, Related Gift ID,  Is Deleted?
• Field Mapping Guide

If your organization is using EverTrue’s Clarity dashboards, be sure to check out our Gift Transaction File Guide to see what fields are required for Clarity! 

Configuring Your Interaction File with RE NXT

When configuring your Interaction file, both Action Type and Status can be pulled as custom fields. Please note the following sync requirements for Signal to CRM:

• 1 constituent maximum and 6 solicitors maximum per interaction.
• Custom fields can be configured to map to RE action attributes.
• Substantive interactions are automatically mapped to 'Priority High' in RE. 
• The EverTrue Interaction ID is embedded in the body of the interaction as:

<etid>1234567890</etid>

• All interactions are loaded as 'Completed' in RE NXT.
• Edits should be made in CRM only.
• Supported EverTrue Fields: Interaction ID, Constituent ID, Date, Type, Summary, Body, Author Name, Author ID, Solicitor Name, Solicitor ID
• Unsupported EverTrue Fields: Additional Constituent ID, Proposal ID, Is Deleted?
• Field Mapping Guide

If your organization is using EverTrue’s Clarity dashboards, be sure to check out our Interaction File Guide to see what fields are required for Clarity!

Configuring Your Proposal File with RE NXT

When configuring your Proposal file, please note that inactive proposals cannot be pulled by Blackbaud’s SKY API. Signal sync requirements include:

• 1 constituent maximum and 6 solicitors maximum per proposal.
• A custom opportunity attribute is required to store 'EverTrueProposalID'.
• If a proposal description is needed, a separate custom opportunity attribute must be created to store this data.
• Proposal designations are supported as long as they already exist in RE.
• Edits should be made in Signal only.
• Supported EverTrue Fields: Proposal ID, Constituent ID, Title, Description, Stage, Solicitor Name, Solicitor User ID, Ask Amount, Ask Date, Expected Amount, Funded Amount, Funded Date, Designation Name
• Unsupported EverTrue Fields: Stage Start Date, Solicitor Key Proposal, Solicitor Title, Active?, Created Date, Original Ask Amount, Original Ask Date, Proposal Type, Confidence Score, Designation Value, Proposal Report Flag, Is Deleted?
• Field Mapping Guide

If your organization is using EverTrue’s Clarity dashboards, be sure to check out our Proposal File Guide to see what fields are required for Clarity!

Configuring Your Portfolio Assignment File with RE NXT

When configuring your Portfolio Assignment file, please note that constituents without prospect statuses will not be pulled into the file. The following logic applies to the API sync:

• Assigning/unassigning prospects will be managed in CRM, while stage changes are managed in Signal.
• Blackbaud does not allow writing directly to 'Prospect Status'.
• New assignment stages should be loaded into a constituent attribute.
• 'Team Name' is a required data field in Signal and must be mapped to a custom field in the solicitor record in RE NXT.
• 'EverTrue Stage', 'EverTrue Stage Start Date', and 'Key Prospect' attributes must be created at the constituent level.
• Supported EverTrue Fields: Team Name, Prospect ID, Solicitor ID, Stage
• Unsupported EverTrue Fields: Stage Start Date, Solicitor Title, Assignment ID, Assignment Title, Key Prospect
• Field Mapping Guide

If your organization is using EverTrue’s Clarity dashboards, be sure to check out our Portfolio Assignment File Guide to see what fields are required for Clarity!

 

---

For any other questions reach out to EverTrue Support at genius@evertrue.com.