How a nonprofit can keep fundraising and gift processing in Blackbaud Raiser's Edge NXT while HubSpot runs marketing and digital engagement: which donor data flows into HubSpot, what flows back, and how consent stays aligned in both systems.
Raiser's Edge NXT is Blackbaud's donor management system. It holds constituents, gifts, appeals, campaigns, funds, events and major gift opportunities, and the development and gift processing teams work in it every day.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Blackbaud's SKY API is documented publicly, with a self-serve developer subscription. An organization admin authorizes the app.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
RE NXT stays the fundraising record, and HubSpot becomes where donors are engaged, with giving data on every contact.
Campaign Creators assessment
Blackbaud exposes Raiser's Edge NXT through the SKY API: REST endpoints secured with OAuth 2.0 and a subscription key, grouped into Constituent, Gift, Fundraising, Event and Opportunity APIs. The SKY Webhook API pushes constituent, gift and solicit code changes to a URL CC hosts. That makes a direct integration buildable. The design is coexistence, not replacement: gift entry, receipting, pledges and prospect research stay in RE NXT; email, forms, nurture journeys and digital reporting run in HubSpot. The plan has to fit the daily API quota on the organization's SKY subscription, and donor privacy rules set what HubSpot may hold.
Scores are CC judgments from Blackbaud's public SKY API documentation. The subscription tier, quota and webhook event coverage are confirmed for the organization's Blackbaud environment in discovery.
Constituents, giving summaries, gifts with splits, appeals, campaigns, funds, events, participants, opportunities and actions are all readable, and most are writable, through documented SKY API endpoints.
Webhook messages carry record IDs, not full records, so each event costs follow-up calls. Daily quotas depend on the SKY subscription tier, so the sync is designed around a call budget.
Solicit codes, consent records and do-not-contact flags decide who HubSpot may email. The organization signs off the field list and the consent rules before any donor data moves.
Seven building blocks shape the integration. Four carry it, two enrich it, and one is a scope decision the organization makes up front.
Individuals and organizations, with their emails, phones, addresses, relationships, constituent codes and custom fields.
Channel consent records and solicit codes (such as do not email or do not solicit) that decide who can be contacted, and how.
Gifts of every type (donations, pledges, recurring gifts and their payments, gifts in kind), with splits across funds, campaigns and appeals.
The attribution structure behind every gift. Appeals and campaigns line up with HubSpot campaigns so marketing can see what it raised.
Fundraising events, their participants, RSVP and attendance, and participant fees and gifts.
Major gift opportunities with ask, expected and funded amounts. Gift officers keep working them in RE NXT.
Gift processing, receipting and acknowledgements stay in RE NXT. The SOW states that HubSpot does not create gifts, so finance reconciliation never splits across two systems.
RE NXT pushes change events to a CC-hosted endpoint. The integration layer fetches the full record by ID, applies the consent and privacy rules, matches the donor and writes to HubSpot in batches. Consent changes and engagement summaries go back to RE NXT through the same SKY API.
RE NXT owns gifts, receipts, pledges and prospect plans. HubSpot owns email, forms, journeys and digital engagement. Each field has one owner, written into the SOW.
An opt-out or solicit code in either system suppresses the donor in both. HubSpot never emails a constituent RE NXT marks as do not email.
Reference data syncs daily, webhooks drive changes, and giving summaries are refreshed only for constituents whose gifts changed.
Each phase ends on a gate the organization signs off before the next begins, so the fixed scope holds even if the SKY subscription or data quality differs from what was expected.
Confirm the organization's SKY subscription and daily quota, register the CC application, and have an environment admin connect it to the organization's Blackbaud environment. Request a sandbox environment for testing.
Agree which system owns each field, which solicit codes and consent channels map to which HubSpot subscription types, and which donor fields HubSpot may hold.
Pull a sample of constituents, gifts, appeals and campaigns. Measure email coverage, duplicate constituents, household structure and how appeals and campaigns are coded.
Create donor properties, the Gift custom object, household associations, campaign mapping and stewardship lists in a HubSpot sandbox.
Build the webhook receiver with Blackbaud's handshake, the record fetcher, consent filter, identity resolver, HubSpot writer and the write-back for consent and actions. Pace every call to the quota.
Load current constituents with consent, giving summaries and an agreed gift history window in batches spread across days if the quota requires it.
Build stewardship, lapsed donor, recurring gift and event workflows with sends paused, run two weeks in parallel, then switch on.
RE NXT names follow SKY API objects and operations as Blackbaud publishes them. Exact field paths, custom fields and code tables are confirmed against the organization's environment during discovery.
| RE NXT field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Constituents & households · Constituent API | ||||
| constituent.id | renxt_constituent_id | Contact | RE → HS | Primary key. Stored as text. |
| constituent.lookup_id | renxt_lookup_id | Contact | RE → HS | The ID staff see in RE NXT. |
| constituent.type | renxt_constituent_type | Contact | RE → HS | Individuals become contacts; organizations become companies. |
| first, last, preferred name | firstname, lastname | Contact | ↔ Both | Fill blanks only; RE NXT wins on edits by gift processing. |
| primary email address | Contact | ↔ Both | Match key after the constituent ID. | |
| primary phone | phone | Contact | RE → HS | Normalize to E.164. |
| preferred address | address, city, state, zip | Contact | RE → HS | Seasonal addresses stay in RE NXT. |
| constituent codes | renxt_constituent_codes | Contact | RE → HS | Multi-select: alumni, board, volunteer and so on. |
| spouse / household relationship | Household company + association | Company | RE → HS | Household structure confirmed in discovery. |
| organization constituent | name, domain | Company | RE → HS | Corporate and foundation donors. |
| Giving summary · Constituent API | ||||
| lifetime giving | renxt_lifetime_giving | Contact | RE → HS | Refreshed when a gift event arrives. |
| first gift date and amount | renxt_first_gift_date | Contact | RE → HS | |
| latest gift date and amount | renxt_last_gift_date, renxt_last_gift_amount | Contact | RE → HS | Drives lapsed-donor workflows. |
| greatest gift amount | renxt_largest_gift | Contact | RE → HS | |
| active recurring gift | renxt_recurring_donor | Contact | RE → HS | From gifts of type RecurringGift; status confirmed in discovery. |
| Gifts & attribution · Gift and Fundraising APIs | ||||
| gift.id | renxt_gift_id | Gift (custom) | RE → HS | Primary key. |
| gift date, amount, type | gift date, amount, type | Gift (custom) | RE → HS | Types include Donation, Pledge, RecurringGift and RecurringGiftPayment. |
| gift split fund | renxt_fund | Gift (custom) | RE → HS | Split gifts keep each fund line. |
| gift split appeal / campaign | renxt_appeal, renxt_campaign | Gift (custom) | RE → HS | Associated to the matching HubSpot campaign. |
| soft credits | Association to soft-credited contact | Gift (custom) | RE → HS | Labeled association. |
| appeal and campaign lists | HubSpot campaign mapping | Campaign | RE → HS | Daily reference sync. |
| Consent, events & prospects | ||||
| consent records by channel | Subscription types | Contact | ↔ Both | Opt-out in either system suppresses both. |
| solicit codes | renxt_solicit_codes | Contact | ↔ Both | Do-not codes block HubSpot sends. |
| email do-not-email flag | Email subscription status | Contact | RE → HS | Respected even without a consent record. |
| event participant RSVP / attended | Custom event: Event attendance | Contact | RE → HS | Associated to the event's HubSpot campaign. |
| opportunity status and ask amount | renxt_open_opportunity | Contact | RE → HS | Status only; prospect notes stay in RE NXT. |
| fundraiser assignment | renxt_fundraiser | Contact | RE → HS | Mapped to a HubSpot user where one exists. |
| HubSpot form or event sign-up | New constituent (create) | Contact | HS → RE | Only when no match is found; flagged for gift processing. |
| HubSpot email engagement summary | Action on constituent | Contact | HS → RE | One action per agreed milestone, not per email. |
Both platforms use OAuth 2.0. SKY API adds a subscription key and a daily quota set by the subscription tier. Values Blackbaud does not publish for a given tier are marked for confirmation.
| Topic | RE NXT | HubSpot |
|---|---|---|
| Authentication | OAuth 2.0 authorization code flow. Every request also carries the Bb-Api-Subscription-Key header from the developer's SKY subscription. | Private app access token or OAuth 2.0 public app. |
| Token lifetime | Access tokens last about 60 minutes. Refresh tokens are valid for 365 days and roll forward on use. | Access tokens refresh through OAuth; private app tokens do not expire. |
| Access model | An environment admin connects the CC application to the organization's Blackbaud environment. A sandbox environment is available for testing. | Self-serve in the portal; custom objects need an Enterprise hub. |
| Real-time | Webhook API subscriptions per event type, such as com.blackbaud.gift.add.v1. Endpoints pass a CloudEvents handshake. Payloads carry IDs only. | Webhooks or workflows for HubSpot-side changes, such as unsubscribes. |
| Rate limits & quota | Per-second rate limit (429 with Retry-After) and a daily quota (403 when exceeded), both set by the subscription tier. Confirm the tier with Blackbaud. | Per-10-second burst and daily limits by subscription tier. |
| Bulk & backfill | Paged list endpoints with last-modified filters. Large histories are loaded across several days if the quota requires it. | Batch endpoints (up to 100 records per call) and CRM imports. |
| Donor privacy | Constituent records include giving history, wealth and prospect data. Only approved fields leave RE NXT. | Sensitive fields restricted by property permissions. |
Severity reflects impact on the SOW, not technical difficulty alone.
Every webhook needs follow-up calls, and backfills are call-heavy. Size the quota against constituent and gift volumes in discovery, and agree in the SOW how long the backfill takes.
Solicit codes, consent records and do-not-email flags overlap. Without one signed consent map, HubSpot could email a donor RE NXT has suppressed.
Wealth screening, prospect notes and research stay in RE NXT. The organization approves the exact field list HubSpot holds and who in HubSpot can see giving fields.
Duplicates in RE NXT become duplicate contacts. Match on constituent ID first, and agree who merges records and where.
Spouses, joint gifts and soft credits must land on the right people. The household model is agreed and tested on real records before the backfill.
Endpoints must answer Blackbaud's handshake, and not every object has webhook events. Objects without events are picked up by a scheduled last-modified sync.
Lifetime giving, last gift, largest gift and recurring status become list filters and personalization tokens for every appeal and newsletter.
Donors who miss their usual giving month, or whose last gift beats their average, enter HubSpot journeys automatically.
HubSpot campaigns line up with RE NXT appeals and campaigns, so marketing sees emails, pages and forms next to the gifts they raised.
When a prospect with an open opportunity opens a case statement or visits a giving page, the assigned fundraiser gets a HubSpot task and an RE NXT action.
Invitations go out from HubSpot, RSVPs and attendance come back from RE NXT, and follow-up workflows run on the real attendance list.
An unsubscribe in HubSpot becomes a consent record in RE NXT the same day, so direct mail and phone teams see it too.
Most organizations keep both systems for the long term. The development team stays in Raiser's Edge NXT; marketing and digital teams work in HubSpot. The integration gives each team the other's data without moving anyone's daily work.
All custom properties use the renxt_ prefix in a Raiser's Edge NXT property group. Giving values are written as RE NXT reports them; HubSpot never recalculates them.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| renxt_constituent_id | RE NXT Constituent ID | Contact | Single-line text | constituent.id; unique |
| renxt_lookup_id | RE NXT Lookup ID | Contact | Single-line text | constituent.lookup_id |
| renxt_constituent_codes | Constituent Codes | Contact | Multiple checkboxes | Constituent code table |
| renxt_lifetime_giving | Lifetime Giving | Contact | Number (currency) | Lifetime giving summary |
| renxt_first_gift_date | First Gift Date | Contact | Date | First gift summary |
| renxt_last_gift_date | Last Gift Date | Contact | Date | Latest gift summary |
| renxt_last_gift_amount | Last Gift Amount | Contact | Number (currency) | Latest gift summary |
| renxt_largest_gift | Largest Gift | Contact | Number (currency) | Greatest gift summary |
| renxt_recurring_donor | Active Recurring Donor | Contact | Single checkbox | Active recurring gift on record |
| renxt_solicit_codes | Solicit Codes | Contact | Multiple checkboxes | Constituent solicit codes |
| renxt_fundraiser | Assigned Fundraiser | Contact | HubSpot user | Fundraiser assignment |
| renxt_gift_id | RE NXT Gift ID | Gift | Single-line text | gift.id; unique |
Choose the APIs and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation from Blackbaud. Quotas, webhook event types and field paths are confirmed for the organization's Blackbaud environment during discovery.
Yes. Blackbaud exposes Raiser's Edge NXT through the SKY API, a set of REST endpoints secured with OAuth 2.0 and a subscription key, and the SKY Webhook API pushes constituent, gift and solicit code changes. Campaign Creators builds a direct integration on them, designed so both systems keep running side by side.
Constituents sync to HubSpot contacts with their giving summary and consent, organizations and households to companies, and gifts to a Gift custom object with fund, campaign and appeal. Appeals and campaigns line up with HubSpot campaigns, and events reach HubSpot. HubSpot sends consent changes, new constituents and engagement back as RE NXT actions.
Raiser's Edge NXT owns gifts, receipts, pledges and prospect plans, and HubSpot never creates gifts. HubSpot owns email, forms, journeys and digital engagement. An opt-out or solicit code in either system suppresses the donor in both, and each field has one owner written into the SOW.
Seven phases, each closed by an organization sign-off: discovery and access (including the SKY subscription and quota), ownership and consent rules, a data audit, the HubSpot data model, the integration build, a backfill, and a parallel run before stewardship and lapsed-donor workflows are switched on.
Timeline and cost depend on the SKY API subscription tier and quota, the objects and history in scope, and the consent rules. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.