Data Reference
The donor and gift properties CRMConnect writes into HubSpot, and how codes, dropdowns, and custom fields work.
What syncs
| Properties | HubSpot object | Synced from | |
|---|---|---|---|
| Donors | ~148 properties | Contact | DonorPerfect donor record |
| Gifts | ~72 properties | Deal (associated to the donor's contact) | DonorPerfect gift record |
The full property-by-property list is maintained as a spreadsheet and shared with you during onboarding - see the link on the main guide. It covers both standard donor fields (contact info, salutation, gift totals and dates, compliance flags) and standard gift fields (amount, date, campaign, solicitation, payment type, pledge/record type, acknowledgement status).
Codes and dropdowns
DonorPerfect represents many fields - campaign, solicitation, general ledger code, gift type, donor type, and others - as short internal codes rather than the readable labels your team enters them under. CRMConnect resolves these automatically:
- The description (the readable label) is written to HubSpot alongside the code, so reporting and dashboards read naturally rather than showing raw codes.
- The first time a new code appears in DonorPerfect, CRMConnect adds it as a new option on the matching HubSpot dropdown property - your HubSpot property list stays in sync with your DonorPerfect configuration without any manual maintenance.
- The same handling applies to DonorPerfect flags, which are multi-select and can be freely customized per organization - flags sync as a multi-select HubSpot property, with new flag options appearing automatically.
Custom fields and objects
If you use a DonorPerfect field outside the standard property set - for example a custom gift-screen field you use for attribution or reporting - it can be carried through to a matching HubSpot property. This is enabled per account rather than on by default; tell your APIANT contact which custom field(s) you want synced and to which HubSpot property.
Contact log
DonorPerfect's contact-log entries (calls, letters, visits recorded against a donor) are not part of the standard CRMConnect property set and are out of scope for this integration.
Questions about a specific field? Contact APIANT support at support@apiant.com.