Skip to main content

​
Donor & Household Data Mapping

This page covers how WeGive Donor and Household records map to StudioEnterprise Accounts. StudioEnterprise Object: Account Sync Direction: Bidirectional (pull on by default; push optional, off by default)

​
Account Type Routing

StudioEnterprise’s Account Type code determines how an account is imported into WeGive: On push, the reverse mapping applies: a WeGive company-type donor is sent as type O; anything else is sent as type I.

​
Core Identity Fields

​
Name Fields

An individual donor’s name and salutation are sent when creating or updating the account.
Organization-type accounts send the organization name only; individual name fields don’t apply.

​
Contact Information

​
Email & Phone

StudioEnterprise requires a defined type code on every email and phone record. WeGive maps its fixed contact-info fields to configurable type codes (set in your integration’s Configuration Options):
A field is only sent if it has both a value AND a configured type code. An unconfigured slot is simply omitted — it doesn’t cause a sync error.
Phone number formatting: WeGive stores phone numbers in whatever format they were entered; StudioEnterprise requires digits-only, up to 10 digits. The integration strips formatting characters and a leading US country code (1) automatically before sending.

​
Address Information

The donor’s mailing address is sent as the account’s primary address.
StudioEnterprise only strictly requires a Country value to accept an address. If a donor has no mailing address on file in WeGive, a default country is sent rather than omitting the address block entirely.
A configured billing address (separate from mailing) is added as a secondary address on the account when present.

​
Households

Households are imported from StudioEnterprise’s Family grouping (Account Type F) — there’s no separate household endpoint; household membership is derived from the Account data itself.

​
Not Yet Supported

Splitting a donor’s contact info out to StudioEnterprise’s own multiple typed contact-method records (rather than mapping WeGive’s fixed email/phone slots to a single type per slot) is planned for a later phase.
Syncing communication/do-not-contact preferences between the two systems is not yet built.
StudioEnterprise supports custom account codes and typed dates (such as birthdate). These are not yet part of the WeGive sync.

Data Mapping Overview

See how all objects map together

Transaction Mapping

Learn how gifts link back to donor accounts
For additional help with donor data mapping, contact our support team at [email protected].