> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Donor & Household Data Mapping

> Detailed field mapping for donor and household profiles between WeGive and StudioEnterprise

# 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:

| StudioEnterprise Type | WeGive Record |
| - | - |
| `I` (Individual) or `S` | Individual Donor |
| `O` (Organization) | Company Donor |
| `F` (Family) | Household |

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

| WeGive Field | StudioEnterprise Field | Notes |
| - | - | - |
| `donor_direct_id` | Account Number | Primary correlation key |
| — | Family ID | Used to group individual accounts into households on pull |

## Name Fields

<AccordionGroup>
  <Accordion title="Individual Donors">
    | WeGive Field | StudioEnterprise Field |
    | - | - |
    | `first_name` | First Name |
    | `last_name` | Last Name |
    | `address_me_as` | Salutation |

    An individual donor's name and salutation are sent when creating or
    updating the account.
  </Accordion>

  <Accordion title="Organization Donors">
    | WeGive Field | StudioEnterprise Field |
    | - | - |
    | `name` | Account Name |

    Organization-type accounts send the organization name only; individual name
    fields don't apply.
  </Accordion>
</AccordionGroup>

## 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](/external/onboarding/donordirect/configuration-options)):

| WeGive Field | Maps via config field |
| - | - |
| `email_1`, `email_2`, `email_3` | `email_1_type`, `email_2_type`, `email_3_type` |
| `mobile_phone`, `office_phone`, `home_phone`, `other_phone` | `mobile_phone_type`, `office_phone_type`, `home_phone_type`, `other_phone_type` |

<Note>
  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.
</Note>

**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.

| WeGive Field | StudioEnterprise Field |
| - | - |
| `address_1` | Address Line 1 |
| `address_2` | Address Line 2 |
| `city` | City |
| `state` | State |
| `zip` | Postal Code |
| `country` | Country |

<Note>
  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.
</Note>

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

<AccordionGroup>
  <Accordion title="Typed StudioEnterprise contact records">
    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.
  </Accordion>

  <Accordion title="Do-not-contact preferences">
    Syncing communication/do-not-contact preferences between the two systems is
    not yet built.
  </Accordion>

  <Accordion title="Custom account attributes and dates">
    StudioEnterprise supports custom account codes and typed dates (such as
    birthdate). These are not yet part of the WeGive sync.
  </Accordion>
</AccordionGroup>

## Related Documentation

<CardGroup cols={2}>
  <Card title="Data Mapping Overview" href="/external/onboarding/donordirect/data-mapping/overview">
    See how all objects map together
  </Card>

  <Card title="Transaction Mapping" href="/external/onboarding/donordirect/data-mapping/transaction">
    Learn how gifts link back to donor accounts
  </Card>
</CardGroup>

For additional help with donor data mapping, contact our support team at
[support@wegive.com](mailto:support@wegive.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.