Blackbaud Raiser's Edge NXT to Constant Contact field mapping

Map supported constituent fields into Constant Contact and use field data to power automations and segmentation

When importing constituents from Blackbaud Raiser’s Edge NXT (RENXT) into Constant Contact, you can select which fields you'd like to map. The integration currently supports 44 predefined constituent fields. Some map automatically, while others require a Constant Contact custom field. Below you’ll find a full list of supported fields, including which are mapped by default.

Supported fields

Field mapping table

Using field mapping to power Automation and Segmentation

Supported Fields

The integration supports 44 predefined RENXT constituent fields. These include default fields and manually mapped fields.

Important: RENXT custom fields (attributes you create yourself) are not supported and cannot be mapped into Constant Contact.

Default mapped fields

• 23 fields (9 Standard + 14 Custom) are mapped automatically.
• Standard fields connect to existing Constant Contact fields.
• Custom fields are auto-created during setup.

Manually mapped fields

21 fields are supported but require you to create or select a Constant Contact custom field before mapping.

Mapping rules

• If a RENXT field matches an existing Constant Contact field, it maps automatically.
• If a RENXT field does not have a match but is part of the default mapping set, a custom field is auto-created and mapped in Constant Contact.
• The remaining non-default fields are available for mapping, but you must create or select a Constant Contact custom field to use them.

Where to locate the fields when importing

When you create an import, you'll be brought to a "Map your data" screen. Here, all 44 RENXT fields are available in the Add new field dropdown. You can choose which ones to bring into Constant Contact.

You have full control to add or remove fields from your mapping as you wish, allowing you to sync only your desired fields.

Field mapping table

Keep in mind

• The integration today allows for 44 fields to be mapped, which falls within Constant Contact’s platform limits.
• Constant Contact supports up to 50 custom fields per contact and 100 unique custom fields per account. You can utilize field mapping and will stay within these limits.
• As more fields become available for mapping, you’ll be able to swap mappings while staying within the 50-per-contact cap.
• RENXT custom fields (attributes you create yourself) are not supported.

Coming Soon: Additional Supported Fields

The following fields will be added in addition to the existing 44 fields already supported.

Important: The below list of fields is still being finalized and is subject to change. Field availability, naming, and default mappings may be adjusted before release.

Using field mapping to power Automation and Segmentation

See below for ideas on how to use mapped fields in conjunction with Constant Contact's Automation Path Builder and Segmentation Builder.

Giving History (with Current + Coming Soon fields)

• First Gift Date / Amount - Trigger a welcome journey for first-time donors.
• Latest Gift Date / Amount - Send a personalized thank-you or acknowledgment.
• Lifetime Giving - Create “Major Donor” segments for special campaigns.
• Consecutive / Total Years Given - Celebrate donor loyalty with anniversary campaigns.
• Appeal Response (Latest Appeal Date) - Segment engaged supporters for future appeals.

Education

• School, Degree, Major, Class Of -
  • Segment alumni by graduation year for reunions.
  • Tailor asks by degree/field of study (e.g., targeted giving).

Demographics & Profile

• Birthdate, Age -
  • Birthday automations.
  • Target younger donors vs. legacy gift prospects.
• Religion / Ethnicity - Segment for culturally relevant outreach (if appropriate & with consent).
• Preferred Name, Salutation, Title, Suffix - Personalize communications with correct addressing.

Constituency & Engagement Roles

• Constituency Codes Active - Segment by supporter role (e.g., “Board Member,” “Volunteer”).
• Fundraiser Role (Is Fundraiser, Assigned Fundraiser Name) - Automate internal workflows for fundraiser assignments or alerts.
• Appeals (Active / Constituency Description) - Re-engage lapsed supporters with targeted asks.

Contact & Address

• Address, City, State, Country, ZIP - Geo-target by region (local events, regional fundraising).

Membership

• Membership Joined Date - Automate “anniversary renewal” reminders.
• Membership Category / Subcategory / Program - Segment by membership tiers for benefits, perks, or upsell.

Events

• Event Name, Start Date, RSVP Status -
  • Pre-event reminders and confirmations.
  • Post-event follow-ups and thank-yous.
  • Nurture “no-show” attendees differently from “attended.”
• Attended Latest Event (True/False) - Segment “active event participants” vs. “non-attendees” for engagement campaigns.

Household / Relationships

• Head of Household (True/False) - Direct messaging to household heads for family campaigns.
• Spouse First/Last Name - Personalize appeals to couples.

New Subscriber / Contact

• New Subscriber / Contact - Trigger a welcome journey automatically when a new contact is added in Constant Contact.

Constituent Added to a RENXT List

• RENXT List Sync - Trigger onboarding or nurture campaigns when a constituent is added to a RENXT list that is mapped to a Constant Contact list.

Questions?