> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to Salesforce Nonprofit Cloud

> How WeGive integrates with Salesforce Nonprofit Cloud (NPC) and how it differs from the NPSP integration

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.

<Tip>
  If your org is on NPSP, see the [Salesforce NPSP integration](/salesforce-npsp/introduction) instead. WeGive supports both, but each is wired to that platform's own object model and cannot read the other's records.
</Tip>

## How NPC differs from NPSP

| Capability | NPSP | NPC (this integration) |
| - | - | - |
| Donor model | Contact plus Household Account | Person Account (individual) plus Account (organization) |
| Donation object | Opportunity plus NPSP Payment | `GiftTransaction` |
| Recurring giving | `npe03__Recurring_Donation__c` | `GiftCommitment` with `GiftCommitmentSchedule` children |
| Funds and designations | `npsp__General_Accounting_Unit__c` and `npsp__Allocation__c` | `GiftDesignation`, `GiftTransactionDesignationRelation`, `GiftDefaultDesignation` |
| Soft credits | Partial Soft Credit, Account Soft Credit, Opportunity Contact Roles | `GiftSoftCredit` |
| Pledges | WeGive custom Pledge object | `GiftCommitment` with a formal commitment type |
| Refunds | Not synced | `GiftRefund` |
| Managed package | WeGive4SF required | None required |
| Licensing | Free NPSP package | Paid Salesforce product; integration user needs the Fundraising Access permission set license |
| Sync engine | REST per record plus Bulk API 2.0 | REST per record; Bulk API 2.0 only for CampaignMember batch pushes |

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.

<Warning>
  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](/external/onboarding/npc/configuration-options) for detail).
</Warning>

* **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](/external/onboarding/npc/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

| Salesforce NPC object | WeGive object |
| - | - |
| Account (Person Account record type) | Supporter (individual) |
| Account (Organization record type) | Company |
| Account (Household record type) | Household |
| `GiftTransaction` | Transaction |
| `GiftCommitment` plus `GiftCommitmentSchedule` (recurring) | Recurring plan |
| `GiftCommitment` (formal commitment) | Pledge |
| `GiftDesignation` | Fund |
| `GiftTransactionDesignationRelation` | Fund allocation on a transaction |
| `GiftDefaultDesignation` | Fund allocation on a recurring plan or pledge |
| `GiftSoftCredit` | Soft credit |
| `GiftRefund` | Transaction refund |
| `GiftTribute` | Tribute details on a transaction |
| `Campaign` | Campaign |
| `CampaignMember` | Campaign supporter |

## Getting started

<CardGroup cols={2}>
  <Card title="Implementation Guide" href="/external/onboarding/npc/install-setup/implementation-guide">
    The full sequence from Sandbox to Production, with a checkpoint per phase.
  </Card>

  <Card title="Setup Requirements" href="/external/onboarding/npc/setup-requirements">
    Prerequisites, licensing, and what WeGive discovers from your org automatically.
  </Card>

  <Card title="External Client App and Connection Setup" href="/external/onboarding/npc/install-setup/external-client-app">
    The app configuration Salesforce needs and how the connection works.
  </Card>

  <Card title="Configuration Options" href="/external/onboarding/npc/configuration-options">
    Pull frequency, per-object toggles, filters, and status mapping overrides.
  </Card>

  <Card title="Data Mapping" href="/external/onboarding/npc/data-mapping/overview">
    Field-by-field mapping for every supported object.
  </Card>
</CardGroup>

Questions? Email [support@wegive.com](mailto:support@wegive.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.