A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Raiser's Edge NXT Integration

Powered by Commercient
Integration Assessment
Integration Assessment · Nonprofit

Raiser's Edge NXT × HubSpot

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.

Blackbaud SKY APIOAuth 2.0 + subscription keyConstituent, Gift, Fundraising APIsEvent and Opportunity APIsSKY Webhook APICoexistence by design
Platform ownerBlackbaud
Integration typeCustom build on SKY API
Primary directionRE NXT → HubSpot, consent both ways
FeasibilityStrong fit, quota-aware
API accessOpen API
01 — Summary

Does Raiser's Edge NXT integrate with HubSpot?

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
API coverageBroad
Real-time eventsWebhooks, IDs only
API quotaTier-bound
Build complexityModerate

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.

Strength

Every fundraising object has an API

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.

Plan for

Quota and thin webhook payloads

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.

Gate

Consent and privacy rules first

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.

02 — API modules

Which Raiser's Edge NXT APIs does the integration use?

Seven building blocks shape the integration. Four carry it, two enrich it, and one is a scope decision the organization makes up front.

Core

Constituent API

api.sky.blackbaud.com/constituent/v1

Individuals and organizations, with their emails, phones, addresses, relationships, constituent codes and custom fields.

  • Lifetime giving, first, latest and greatest gift summaries
  • Relationships for spouses, households and employers
  • Fundraiser assignments and prospect status
Core

Consent & solicit codes

Constituent API · consent records, solicit codes

Channel consent records and solicit codes (such as do not email or do not solicit) that decide who can be contacted, and how.

  • Read and create consent records
  • Solicit code added, changed and deleted webhook events
  • Maps to HubSpot subscription types
Core

Gift API

api.sky.blackbaud.com/gift/v1

Gifts of every type (donations, pledges, recurring gifts and their payments, gifts in kind), with splits across funds, campaigns and appeals.

  • Gift splits carry fund, campaign and appeal
  • Soft credits and recurring gift schedules
  • Gift added, changed and deleted webhook events
Core

Fundraising API

Appeals · campaigns · funds · packages

The attribution structure behind every gift. Appeals and campaigns line up with HubSpot campaigns so marketing can see what it raised.

  • Appeal, campaign and fund lists with custom fields
  • Low change rate; synced daily
  • Reference data for gift attribution
Enrichment

Event API

Events · participants · fees

Fundraising events, their participants, RSVP and attendance, and participant fees and gifts.

  • Invitations and RSVPs from HubSpot campaigns
  • Attendance on the contact timeline
  • Post-event follow-up workflows
Handoff

Opportunity API

Prospect asks · major gifts

Major gift opportunities with ask, expected and funded amounts. Gift officers keep working them in RE NXT.

  • HubSpot engagement signals go to the assigned fundraiser
  • Opportunity status shown on the HubSpot contact
  • Actions can log HubSpot touches in RE NXT
Scope decision

Where gifts are entered

Online giving and gift processing

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.

  • Online donations land in RE NXT first
  • HubSpot receives the gift after it is posted
  • Any exception is named in the SOW
03 — Framework

How does the Raiser's Edge NXT HubSpot integration work?

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.

Raiser's Edge NXT (SKY API)
Constituent APIdonors, households, giving summaries
Gift APIgifts, splits, recurring gifts
Fundraising & Event APIsappeals, campaigns, funds, events
Webhook APIconstituent, gift, solicit code events
CC integration layer
Webhook receiverhandshake, queue, de-duplicate
Record fetcherIDs to full records, quota-aware
Consent & privacy filtersolicit codes, opt-outs, field list
Identity resolverconstituent ID → lookup ID → email
HubSpot writerbatch upserts, error replay
HubSpot
Contactsdonors with giving summary and consent
Companiesorganizations and households
Gifts (custom object)gift date, amount, fund, appeal
Campaignsmatched to RE NXT appeals and campaigns
Lists, workflows & reportsstewardship, lapsed donors, events
RE NXT → HubSpot (donors, giving, attribution, events)HubSpot → RE NXT (consent, new constituents, engagement as actions)
Principle

Each system owns its job

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.

Principle

Consent travels with the donor

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.

Principle

Spend the quota on what matters

Reference data syncs daily, webhooks drive changes, and giving summaries are refreshed only for constituents whose gifts changed.

04 — Process

What does Raiser's Edge NXT HubSpot integration setup involve?

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.

1

Discovery & access

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.

Gate to next phaseCredentials work against the Constituent and Gift APIs
2

Ownership & consent rules

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.

Gate to next phaseSigned ownership table, consent map and approved field list
3

Data audit

Pull a sample of constituents, gifts, appeals and campaigns. Measure email coverage, duplicate constituents, household structure and how appeals and campaigns are coded.

Gate to next phaseSigned match rules and attribution map
4

HubSpot data model

Create donor properties, the Gift custom object, household associations, campaign mapping and stewardship lists in a HubSpot sandbox.

Gate to next phaseSchema approved and created
5

Integration build

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.

Gate to next phaseAll sync modules running end to end in sandbox
6

Backfill

Load current constituents with consent, giving summaries and an agreed gift history window in batches spread across days if the quota requires it.

Gate to next phaseHubSpot totals reconcile to RE NXT within an agreed tolerance
7

Workflows, parallel run & launch

Build stewardship, lapsed donor, recurring gift and event workflows with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Raiser's Edge NXT HubSpot integration sync?

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 fieldHubSpot propertyObjectDirectionNotes
Constituents & households · Constituent API
constituent.idrenxt_constituent_idContactRE → HSPrimary key. Stored as text.
constituent.lookup_idrenxt_lookup_idContactRE → HSThe ID staff see in RE NXT.
constituent.typerenxt_constituent_typeContactRE → HSIndividuals become contacts; organizations become companies.
first, last, preferred namefirstname, lastnameContact↔ BothFill blanks only; RE NXT wins on edits by gift processing.
primary email addressemailContact↔ BothMatch key after the constituent ID.
primary phonephoneContactRE → HSNormalize to E.164.
preferred addressaddress, city, state, zipContactRE → HSSeasonal addresses stay in RE NXT.
constituent codesrenxt_constituent_codesContactRE → HSMulti-select: alumni, board, volunteer and so on.
spouse / household relationshipHousehold company + associationCompanyRE → HSHousehold structure confirmed in discovery.
organization constituentname, domainCompanyRE → HSCorporate and foundation donors.
Giving summary · Constituent API
lifetime givingrenxt_lifetime_givingContactRE → HSRefreshed when a gift event arrives.
first gift date and amountrenxt_first_gift_dateContactRE → HS
latest gift date and amountrenxt_last_gift_date, renxt_last_gift_amountContactRE → HSDrives lapsed-donor workflows.
greatest gift amountrenxt_largest_giftContactRE → HS
active recurring giftrenxt_recurring_donorContactRE → HSFrom gifts of type RecurringGift; status confirmed in discovery.
Gifts & attribution · Gift and Fundraising APIs
gift.idrenxt_gift_idGift (custom)RE → HSPrimary key.
gift date, amount, typegift date, amount, typeGift (custom)RE → HSTypes include Donation, Pledge, RecurringGift and RecurringGiftPayment.
gift split fundrenxt_fundGift (custom)RE → HSSplit gifts keep each fund line.
gift split appeal / campaignrenxt_appeal, renxt_campaignGift (custom)RE → HSAssociated to the matching HubSpot campaign.
soft creditsAssociation to soft-credited contactGift (custom)RE → HSLabeled association.
appeal and campaign listsHubSpot campaign mappingCampaignRE → HSDaily reference sync.
Consent, events & prospects
consent records by channelSubscription typesContact↔ BothOpt-out in either system suppresses both.
solicit codesrenxt_solicit_codesContact↔ BothDo-not codes block HubSpot sends.
email do-not-email flagEmail subscription statusContactRE → HSRespected even without a consent record.
event participant RSVP / attendedCustom event: Event attendanceContactRE → HSAssociated to the event's HubSpot campaign.
opportunity status and ask amountrenxt_open_opportunityContactRE → HSStatus only; prospect notes stay in RE NXT.
fundraiser assignmentrenxt_fundraiserContactRE → HSMapped to a HubSpot user where one exists.
HubSpot form or event sign-upNew constituent (create)ContactHS → REOnly when no match is found; flagged for gift processing.
HubSpot email engagement summaryAction on constituentContactHS → REOne action per agreed milestone, not per email.
06 — Auth & API

How are authentication and API limits handled?

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.

TopicRE NXTHubSpot
AuthenticationOAuth 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 lifetimeAccess 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 modelAn 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-timeWebhook 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 & quotaPer-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 & backfillPaged 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 privacyConstituent records include giving history, wealth and prospect data. Only approved fields leave RE NXT.Sensitive fields restricted by property permissions.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Daily quota sets the paceHigh

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.

Consent rules must be agreed firstHigh

Solicit codes, consent records and do-not-email flags overlap. Without one signed consent map, HubSpot could email a donor RE NXT has suppressed.

Donor privacy and data minimizationHigh

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.

Duplicate constituentsMedium

Duplicates in RE NXT become duplicate contacts. Match on constituent ID first, and agree who merges records and where.

Households and soft creditsMedium

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.

Webhook handshake and coverageLow

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.

Opportunities in HubSpot

Giving data on every contactHigh value

Lifetime giving, last gift, largest gift and recurring status become list filters and personalization tokens for every appeal and newsletter.

Lapsed and upgrade journeysHigh value

Donors who miss their usual giving month, or whose last gift beats their average, enter HubSpot journeys automatically.

Appeal attribution in one reportHigh value

HubSpot campaigns line up with RE NXT appeals and campaigns, so marketing sees emails, pages and forms next to the gifts they raised.

Major gift signals to fundraisersMedium value

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.

Event invitations to follow-upMedium value

Invitations go out from HubSpot, RSVPs and attendance come back from RE NXT, and follow-up workflows run on the real attendance list.

Consent kept in stepMedium value

An unsubscribe in HubSpot becomes a consent record in RE NXT the same day, so direct mail and phone teams see it too.

Coexistence plan

Fundraising in RE NXT, engagement in HubSpot.

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.

  1. Gift processing: gifts, receipts, pledges and acknowledgements stay in RE NXT, and HubSpot reads them after they post.
  2. Marketing: email, forms, landing pages and journeys run in HubSpot, using giving data and consent from RE NXT.
  3. Major gifts: gift officers keep opportunities and prospect plans in RE NXT and receive HubSpot engagement signals as tasks and actions.
  4. Reporting: HubSpot reports on the full donor journey, from first email to latest gift, by appeal and campaign.
08 — Property schema

Which HubSpot properties does the integration create?

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 nameLabelObjectTypeSource / logic
renxt_constituent_idRE NXT Constituent IDContactSingle-line textconstituent.id; unique
renxt_lookup_idRE NXT Lookup IDContactSingle-line textconstituent.lookup_id
renxt_constituent_codesConstituent CodesContactMultiple checkboxesConstituent code table
renxt_lifetime_givingLifetime GivingContactNumber (currency)Lifetime giving summary
renxt_first_gift_dateFirst Gift DateContactDateFirst gift summary
renxt_last_gift_dateLast Gift DateContactDateLatest gift summary
renxt_last_gift_amountLast Gift AmountContactNumber (currency)Latest gift summary
renxt_largest_giftLargest GiftContactNumber (currency)Greatest gift summary
renxt_recurring_donorActive Recurring DonorContactSingle checkboxActive recurring gift on record
renxt_solicit_codesSolicit CodesContactMultiple checkboxesConstituent solicit codes
renxt_fundraiserAssigned FundraiserContactHubSpot userFundraiser assignment
renxt_gift_idRE NXT Gift IDGiftSingle-line textgift.id; unique
09 — Scope builder

Interactive scope builder

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.

Scope summary

0Fields
0Inbound
0Write-back
RE NXT × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Raiser's Edge NXT HubSpot integration FAQ

Does Raiser's Edge NXT integrate with HubSpot?

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.

What data syncs between Raiser's Edge NXT and HubSpot?

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.

Which system owns which data?

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.

What does setting up the Raiser's Edge NXT HubSpot integration involve?

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.

How long does the integration take and what does it cost?

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.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.