Data Mapping Overview
Object mapping
| WeGive object | NPC object | Notes |
|---|---|---|
| Donor (individual) | Account (Person Account record type) | Person Account = Account + embedded Contact |
| Company | Account (Organization record type) | |
| Household | Account (Household record type) | Linked to individual donors via ParentId |
| Campaign | Campaign | |
| Fund | GiftDesignation | NPC’s purpose-built designation object |
| Transaction | GiftTransaction | |
| Fund Allocation | GiftTransactionDesignationRelation | Designation splits on a transaction |
| Scheduled Donation | GiftCommitment + GiftCommitmentSchedule | Schedule rows define frequency and interval |
| Pledge | Pledge | |
| Soft Credit | GiftSoftCredit | |
| Campaign Donor | CampaignMember | |
| Transaction Refund | GiftRefund |
Field-level reference
Person Account Individual donor field mapping (PersonAccount + embedded Contact fields).
Organization Account Company donor field mapping.
Household Household account field mapping and member linkage.
Gift Transaction Transaction field mapping including status and payment method.
Gift Commitment Recurring donation field mapping and schedule translation.
Gift Designation Fund field mapping.
Soft Credit Soft credit type, role, and split-amount mapping.
Pledge Pledge field mapping.
Campaign Campaign field mapping.
Campaign Member Donor-to-campaign relationship mapping.
Sync direction legend
In the field tables on each page:
- ↔ — bidirectional sync
- → — push only (WeGive writes to NPC; NPC edits ignored)
- ← — pull only (NPC writes to WeGive)
- create-only — set on initial create; subsequent edits are not synced
Customizing a mapping
Every default mapping is overridable per organization. The override lives in WeGive as a NeonMappingRule row pointing the integration at a different NPC field or a custom path on the WeGive model. Open a support ticket to add or change one.