Salesforce Nonprofit Cloud Overview

Salesforce Nonprofit Cloud (NPC) is Salesforce’s purpose-built product for nonprofits and the successor to the Nonprofit Success Pack (NPSP). WeGive’s NPC integration syncs bidirectionally against NPC’s native object model — GiftTransaction, GiftCommitment, GiftDesignation, GiftSoftCredit — instead of the older NPSP Opportunity-based model.

Tip

If your org is on NPSP (legacy), see the Salesforce NPSP integration instead. WeGive supports both, but each is wired to that platform’s own object model and cannot read the other’s records.

How NPC differs from NPSP

Capability	NPSP	NPC (this integration)
Donor model	Contact-only	Person Account (individual) + Account (organization)
Donation object	Opportunity + NPSP Payment custom fields	GiftTransaction (native, purpose-built)
Recurring giving	npe03__Recurring_Donation__c	GiftCommitment (native, with GiftCommitmentSchedule children)
Funds / designations	npsp__General_Accounting_Unit__c	GiftDesignation
Soft credits	NPSP partial credits + opportunity contact roles	GiftSoftCredit
Pledges	Opportunity (stage = Pledged) or custom object	Pledge object
Refunds	Manual	GiftRefund
Pricing	Open-source managed package	Paid Salesforce product
Sync engine	REST per-record + bulk	REST per-record + Bulk API 2.0 for large jobs

Because the object models differ, the WeGive NPC integration cannot read NPSP Opportunities, and vice versa. If you’re migrating from NPSP to NPC, the migration of historical data happens inside Salesforce; WeGive will pick up the new objects once you point it at the NPC org.

Key features

• OAuth 2.0 with PKCE — no API keys or manual connected-app configuration.
• Bidirectional sync for donors, companies, households, transactions, recurring plans, pledges, soft credits, and refunds.
• Bulk API 2.0 for large historical imports — efficient CSV streaming instead of per-record REST calls.
• Person Account support — automatic discovery of your org’s PersonAccount, Organization, and Household record type IDs.
• Configurable field mapping — every default mapping can be overridden per organization without code changes.
• Sandbox-aware — point at test.salesforce.com for sandbox orgs and login.salesforce.com for production with a single setting.

Synced objects

Salesforce NPC object	WeGive object
Person Account	Donor (individual)
Account (organization record type)	Company
Account (household record type)	Household
GiftTransaction	Transaction
GiftCommitment + GiftCommitmentSchedule	Scheduled Donation
GiftDesignation	Fund
GiftTransactionDesignationRelation	Fund Allocation (split)
GiftSoftCredit	Soft Credit
Pledge	Pledge
GiftRefund	Transaction Refund
CampaignMember	Campaign Donor
Campaign	Campaign

Getting started

Setup Requirements Prerequisites, the OAuth flow, and what WeGive discovers from your org automatically.

Configuration Options Pull frequency, per-object toggles, status mapping overrides, and sandbox vs production.

Data Mapping Field-by-field mapping for every supported object.

Integration Nuances Person Account requirement, Bulk API behavior, deletion polling, and API version notes.

Support

Need help? Email support@wegive.com.