Fundraising and donor CRMs integration · Updated November 15, 2026

Salesforce Nonprofit Cloud integration

Each website gift becomes a person account with a gift transaction or recurring gift commitment in Salesforce Nonprofit Cloud. We build that link from WordPress, Webflow, Astro or Next.js sites and custom software, and plan it around the NPSP move if you haven't made it.

Rated 5.0 out of 5,72 Google reviews

Salesforce Nonprofit Cloud at a glance

Connects
Website forms to person accounts, gift transactions, gift commitments and campaigns.
WordPress
A small custom plugin that posts gifts server side. Web-to-Lead only for simple enquiries.
Webflow
Submissions go to our hosted function, which calls Salesforce.
Astro or Next.js with Sanity
A server endpoint posts gifts and caches campaign totals. Sanity holds page content.
Custom software
Connect REST fundraising resources or Apex, plus the standard REST API.
Complexity
High. Data model, donor matching and permissions need setup before the first gift posts.
Typical setup
2 to 4 days for Web-to-Lead enquiry forms, 10 to 20 days for gift and recurring-gift sync.

How we connect Salesforce Nonprofit Cloud

  • WordPress

    Web-to-Lead works from any WordPress form, but it creates leads rather than person accounts or gifts, and Salesforce caps it at 500 a day. For donations, a small plugin sends each completed payment to the Fundraising Business APIs from the server as a dedicated integration user. The payment form can be your processor's, so card data never touches WordPress.

  • Webflow

    Webflow forms can't sign in to Salesforce, and API credentials don't belong in a page. Form submissions and payment events go to a function we host, which matches or creates the donor and posts the gift. There's no Webflow app we'd rely on to write Nonprofit Cloud gift records, so every build includes this server step.

  • Astro or Next.js with Sanity

    Editors manage campaign pages in Sanity. An Astro server endpoint or Next.js route handler holds the Salesforce credentials, posts gifts and commitments, and reads campaign progress. We cache those reads and refresh them on a schedule, so a busy appeal page doesn't spend your daily API allocation.

  • Custom software

    For a donor portal, event system or payment integration, we call the Connect REST fundraising resources or the same APIs through Apex, and the standard REST or Bulk API for other objects. Gateway fields on gift transactions and the payment-update endpoints keep a processor's reference numbers and card changes in step with Salesforce.

What organizations use Salesforce Nonprofit Cloud for

  • One-time gifts from the website

    The gifts endpoint creates a gift transaction with a new or matched donor, designations and payment details in one call. With donor matching and duplicate rules configured, a website gift finds the existing person account. We map campaign and source codes from the page so reports show which appeal raised it.

  • Monthly giving

    Recurring gifts are gift commitments with a schedule, and each processed payment becomes a gift transaction. The commitments endpoint creates the commitment, schedule and donor together, and a PATCH call changes the amount or payment method later. We connect your processor so a card update or failed payment lands on the right commitment.

  • Moving from NPSP

    Salesforce's migration guide (version 2.0, June 2026) strongly recommends a new org over an in-place upgrade, with every contact becoming a person account and NPSP opportunities split into several new records. Website integrations built on NPSP objects break in that move. We rebuild them and can run old and new connections side by side during cutover.

What to watch out for

  • No NPSP end date yet

    As of November 15, 2026, Salesforce says NPSP will continue to be supported and has published no end-of-support date, though it steers new customers to Nonprofit Cloud, now called Agentforce Nonprofit. Each new integration built on NPSP objects is one more to rewrite when you move.

  • Person accounts are permanent

    Nonprofit Cloud fundraising expects person accounts, and Salesforce's Trailhead notes that once they're turned on, they can't be turned off. The NPSP household account model isn't supported. Form mappings, duplicate rules and any connected tool that assumes household accounts need testing before you switch on fundraising.

  • Canadian hosting and consent

    As of November 15, 2026, Salesforce runs Hyperforce on AWS in Canada and stores data at rest there when the services you use are available in that region, though some data can leave Canada for support or processing. Your own forms still need an unticked CASL opt-in with its date recorded, and your privacy notice should name Salesforce.

Questions about Salesforce Nonprofit Cloud

Can Nonprofit Cloud produce CRA donation receipts?

Not out of the box. Salesforce's fundraising implementation guide says Canadian tax receipting needs custom configuration or a third-party app. Gift transactions carry a tax receipt status field, and DocGen produces letters with a free add-on licence. We build receipt numbering, CRA wording and the email from that data, or connect a receipting app.

Should our donor portal be an Experience Cloud site?

If donors need to log in and see records that live in Salesforce, Experience Cloud keeps that inside Salesforce, though logins need their own licences and design work. For public appeals and simple giving, your own site is faster and cheaper to run.

How much can our website call Salesforce?

Enterprise Edition gets 100,000 API calls per 24 hours plus 1,000 per Salesforce user licence, shared with every other integration. Customer Community licences add none. We cache public data like campaign totals and use one call per gift, so a website rarely comes close.

Related integrations

Sending website gifts into Nonprofit Cloud?

Tell us whether you're on NPSP or Nonprofit Cloud, which payment processor you use and how you receipt today. We'll say what the integration needs and what changes if you migrate.

Book a call