Skip to main content
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 Opportunity-based NPSP model.
If your org is on NPSP, 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

Because the object models differ, the NPC integration cannot read NPSP Opportunities, and the NPSP integration cannot read GiftTransaction records. If you are migrating from NPSP to NPC, historical data migration happens inside Salesforce; WeGive picks up the NPC objects once you connect it to the NPC org.

​
Key features

  • OAuth 2.0 authorization. No Salesforce password is stored in WeGive.
  • Bidirectional sync for donors, transactions, recurring plans, pledges, soft credits, campaign members, and refunds.
Companies and households currently sync one direction only (Salesforce → WeGive). The dashboard shows push toggles for both, but they have no effect — this is a known issue (see the Sync Toggles table on Configuration Options for detail).
  • Bulk API 2.0 for CampaignMember batch push operations. Historical imports and all other objects use paginated REST queries, not Bulk API 2.0 — see Setup Requirements for detail.
  • Person Account support with automatic discovery of your Person Account, Organization, and Household record type IDs.
  • Configurable field mapping. Every default mapping can be overridden per organization.
  • Schema-aware. WeGive checks which fields and relationships your org exposes before querying them, so orgs on different NPC releases sync without errors.
  • Sandbox and production connections, each authorized separately.

​
Synced objects

​
Getting started

Implementation Guide

The full sequence from Sandbox to Production, with a checkpoint per phase.

Setup Requirements

Prerequisites, licensing, and what WeGive discovers from your org automatically.

External Client App and Connection Setup

The app configuration Salesforce needs and how the connection works.

Configuration Options

Pull frequency, per-object toggles, filters, and status mapping overrides.

Data Mapping

Field-by-field mapping for every supported object.
Questions? Email [email protected].