Data Mapping Overview
Object mapping
| WeGive object | HubSpot object | Notes |
|---|---|---|
| Donor (individual) | Contact | Email is the natural key when one is present. |
| Donor (company) | Company | wegive_entity_type = company. |
| Household | Company | wegive_entity_type = household, with Household association label. |
| Transaction | Deal (Donations pipeline) | One deal per gift. Stage reflects WeGive transaction status. |
| Scheduled Donation | Deal (Recurring Donations pipeline) | One deal per recurring plan. Linked to gift deals via Recurring Plan label. |
Associations
WeGive provisions two custom association labels in HubSpot during setup:
- Household — links Contacts (household members) to a Company (the household).
- Recurring Plan — links Donation deals (one-time gifts that were generated from a plan) to their Recurring Donations parent deal.
Standard HubSpot associations are also maintained:
- Contact → Company (primary employer or household)
- Deal → Contact (donor for the gift)
- Deal → Company (company donor or household)
Field-level reference
Contact Donor → Contact field mapping, including lifetime giving rollups.
Company Company and household → Company field mapping.
Deal — Donation Transaction → Deal mapping in the Donations pipeline.
Deal — Recurring Donation Scheduled donation → Deal mapping in the Recurring Donations pipeline.
Sync direction legend
In the field tables on each page:
- ↔ — bidirectional. WeGive will push edits to HubSpot and pull edits from HubSpot.
- → — push-only. WeGive writes this field to HubSpot; HubSpot edits to it are ignored on pull.
Financial fields and lifetime rollups are always → to keep WeGive’s reporting authoritative.