Field Mapping Reference

Last updated: April 29, 2026

This article covers the default field mappings between WeGive and Salesforce NPC. These mappings are configured on the Mapping Rules tab in Settings > Integrations > Salesforce Nonprofit Cloud Setup.

Each mapping rule has a sync direction:

Bi-directional - changes sync both ways between WeGive and Salesforce
Export only - data pushes from WeGive to Salesforce only; changes in Salesforce do not flow back
Create only - the field is set when the record is first created but is not updated on subsequent syncs

You can add custom mapping rules on the Mapping Rules tab by clicking Add Rule under any object section.

Supporters

The Supporters section contains 3 object types with 30 rules total.

Person Accounts (Individual Supporters)

16 default rules:

NPC Field	WeGive Field	Direction
`PersonEmail`	`email_1`	Bi-directional
`FirstName`	`first_name`	Bi-directional
`LastName`	`last_name`	Bi-directional
`PersonMailingStreet`	`mailing_address.address_1`	Bi-directional
`PersonMailingCity`	`mailing_address.city`	Bi-directional
`PersonMailingState`	`mailing_address.state`	Bi-directional
`PersonMailingPostalCode`	`mailing_address.zip`	Bi-directional
`PersonMailingCountry`	`mailing_address.country`	Bi-directional
`PersonOtherStreet`	`billing_address.address_1`	Bi-directional
`PersonOtherCity`	`billing_address.city`	Bi-directional
`PersonOtherState`	`billing_address.state`	Bi-directional
`PersonOtherPostalCode`	`billing_address.zip`	Bi-directional
`PersonOtherCountry`	`billing_address.country`	Bi-directional
`PersonMobilePhone`	`mobile_phone`	Bi-directional
`Phone`	`home_phone`	Bi-directional
`PersonBirthdate`	`birthdate`	Bi-directional

Note: Person Account mailing address maps to WeGive mailing address. Person Account "other" address maps to WeGive billing address.

Organization Accounts

13 default rules:

NPC Field	WeGive Field	Direction
`Name`	`name`	Bi-directional
`Phone`	`office_phone`	Bi-directional
`Fax`	`fax`	Bi-directional
`BillingStreet`	`billing_address.address_1`	Bi-directional
`BillingCity`	`billing_address.city`	Bi-directional
`BillingState`	`billing_address.state`	Bi-directional
`BillingPostalCode`	`billing_address.zip`	Bi-directional
`BillingCountry`	`billing_address.country`	Bi-directional
`ShippingStreet`	`mailing_address.address_1`	Bi-directional
`ShippingCity`	`mailing_address.city`	Bi-directional
`ShippingState`	`mailing_address.state`	Bi-directional
`ShippingPostalCode`	`mailing_address.zip`	Bi-directional
`ShippingCountry`	`mailing_address.country`	Bi-directional

Note: Organization billing address maps to WeGive billing address. Organization shipping address maps to WeGive mailing address.

Households

1 default rule:

NPC Field	WeGive Field	Direction
`Name`	`name`	Bi-directional

Donations

The Donations section contains 5 object types with 21 rules total.

Gift Transactions

9 default rules:

NPC Field	WeGive Field	Direction
`OriginalAmount`	`amount`	Bi-directional
`TransactionDate`	`created_at`	Bi-directional
`Status`	`status`	Export only
`PaymentMethod`	`source_type`	Export only
`Description`	`description`	Bi-directional
`DonorId`	`owner.npc_id`	Bi-directional, Create only
`CampaignId`	`campaign.npc_id`	Bi-directional
`GiftCommitmentId`	`scheduled_donation.npc_id`	Bi-directional, Create only
`GatewayReference`	`correlation_id`	Export only

Amount handling: WeGive stores amounts in cents (integer). Salesforce stores amounts in dollars (Currency). The integration converts automatically (divide by 100 on push, multiply by 100 on pull).

Status and PaymentMethod are export only. WeGive is the system of record for these values. The specific status labels pushed to Salesforce are configurable on the Sync Configuration tab under Transaction Status Names.

DonorId and GiftCommitmentId are create only. The supporter and recurring donation links are set when the transaction is first created and will not change on subsequent syncs.

Gift Commitments (Recurring Donations)

3 default rules:

NPC Field	WeGive Field	Direction
`Status`	`status`	Export only
`DonorId`	`source.npc_id`	Bi-directional, Create only
`CampaignId`	`campaign.npc_id`	Bi-directional

Pledges

3 default rules:

NPC Field	WeGive Field	Direction
`Status`	`status`	Export only
`DonorId`	`donor.npc_id`	Bi-directional, Create only
`CampaignId`	`campaign.npc_id`	Bi-directional

Campaign Donors

2 default rules:

NPC Field	WeGive Field	Direction
`CampaignId`	`campaign.npc_id`	Bi-directional
`ContactId`	`donor.npc_id`	Bi-directional

Soft Credits

4 default rules:

NPC Field	WeGive Field	Direction
`PartialAmount`	`amount`	Bi-directional
`Role`	`type`	Bi-directional
`GiftTransactionId`	`transaction.npc_id`	Bi-directional, Create only
`RecipientId`	`donor.npc_id`	Bi-directional, Create only

Campaigns and Funds

The Campaigns and Funds section contains 2 object types with 6 rules total.

Campaigns

3 default rules:

NPC Field	WeGive Field	Direction
`Name`	`name`	Bi-directional
`StartDate`	`start_date`	Bi-directional
`EndDate`	`end_date`	Bi-directional

Fund Designations

3 default rules (GiftDesignation replaces NPSP General Accounting Units):

NPC Field	WeGive Field	Direction
`Name`	`name`	Bi-directional
`Description`	`description`	Bi-directional
`IsActive`	`active`	Bi-directional

Custom Field Mappings

If you need to sync WeGive data that is not covered by the default mappings (for example, anonymous flags, tribute details, processing fees, or UTM tracking), you can create custom fields in Salesforce and add mapping rules in the Mapping Rules tab.

To add a custom mapping:

Create the custom field on the appropriate NPC object in Salesforce
In WeGive, go to Settings > Integrations > Salesforce Nonprofit Cloud Setup > Mapping Rules
Find the relevant object section (e.g. Gift Transactions)
Click Add Rule
Select the Salesforce NPC field and the WeGive field to map
Choose the sync direction
Click Save

Keep in mind that if WeGive ships a managed package with fields for the same data in the future, manually created fields could result in duplicates.