Importing Gifts

Prev Next

Gifts can be imported into Slate in batch using the Upload Dataset tool. At a minimum, the required fields for creating a gift are:

  1. Gift Fund

  2. Gift Amount

  3. Gift Status

  4. Gift Type

  5. Sufficient matching criteria to associate the gift with the correct constituent record (such as Slate ID, Dataset Key, or a combination like First + Last + DOB/Email).

As a best practice, institutions should include as many additional gift data points as possible in the import. This may include data such as Gift Date, Campaign, Appeal, soft credit handling, user, and other relevant details to ensure accurate reporting and downstream processing.

📝 Important Note on Tributes

Tributes can be included as part of a gift import; however, it is important to review the Importing Tributes article to ensure they are structured and mapped correctly.

The following mapping destinations are intentionally excluded from the table below:

  • Gift - Occasion

  • Gift - Honoring

  • Gift - Tribute

The following mapping destinations are specifically for received Gifts. Planned Gift intentions and Pledges are imported with similar but distinct destinations, and should be imported before importing associated gifts to ensure proper connection.

Gift Mapping Destinations

Description

Gift - Amount

The total monetary amount of the gift.

Gift - Anonymous

This destination uses Value Mappings—on the Value Mappings tab, select Yes (gift should be anonymous) or No (gift should not be anonymous).

Gift - Appeal

Connect an Appeal to the gift using the Appeal Name. This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate Appeal.

Gift - Appeal (Key)

Connect an Appeal to the gift using the Appeal Key.

Gift - Campaign

Connect a Campaign to the gift using the Campaign Name. This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate Campaign.

Gift - Campaign (Key)

Connect a Campaign to the gift using the Campaign Key.

Gift - Date

Mapping a date field to this destination sets the date of the gift. If a date is not mapped, the current date is used instead.

Gift - Date (day only)

Use when the gift date is split across multiple columns in your file:
(Day Only): Maps the day portion of the date.

Gift - Date (month only)

Use when the gift date is split across multiple columns in your file:
(Month Only): Maps the month portion of the date.

Gift - Date (year only)

Use when the gift date is split across multiple columns in your file:
(Year Only): Maps the year portion of the date.

Gift - External ID

External ID is a unique identifier used to match an existing gift.

  • If a gift is matched using another method (GUID or Identity), this mapping updates or sets the External ID.

  • If no match is found, the value is applied to the new gift record.

Gift - Fair Market Value

The fair market value of the gift, if any.

Gift - Fulfillment External ID

Associates the gift with an existing Pledge or Planned Gift using External ID.

Gift - Fulfillment Identity

Associates the gift with an existing Pledge or Planned Gift using Identity.

Gift - Fulfillment Same Ordinal

If importing both pledge/planned giving and gift information in the same file (and pledge/planned gift #x should be fulfilled by gift #x), then this destination allows Slate to know that gift #1 is associated with pledge #1, gift #2 is associated with pledge #2, and so on.

Gift - Fund

Connect a Fund to the gift using the Fund Name. This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate Fund.

Gift - Fund (Key)

Connect a Fund to the gift using the Fund Key.

Gift - Identity (matching only)

The identity of the gift can be used as a unique field for matching a particular gift record. The identity will not be updated.

Gift - Notes

Allows for the import of gift notes (free text).

Gift - Opportunity External ID

Associates the gift with an existing Opportunity using External ID.

Gift - Opportunity Identity

Associates the gift with an existing Opportunity using Identity.

Gift - Reverse Gift

This destination uses Value Mappings—on the Value Mappings tab, select Yes (Reverse Gift).

Gift - Slate GUID (matching only)

The GUID of the gift can be used as a unique field for matching a particular gift record. The GUID will not be updated.

Gift - Status

This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate Gift Status prompt value.

Gift - Type

This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate Gift Type prompt value.

Gift - User

This destination uses Value Mappings—on the Value Mappings tab, map the incoming value to the appropriate User Record.

Gift - Apply Relationship Soft Credits

Controls how soft credits are assigned to related records when a gift is imported. This destination uses Value Mappings—on the Value Mappings tab, select one of the following options:

  • Apply to all suggested records

  • Apply to default records only

  • Do not apply soft credits

Gift - Apply Soft Credits by Slate ID

Map a person’s Slate ID (or dataset key) to apply a soft credit to a specific record. To apply multiple soft credits, provide a delimited list of IDs (e.g., 123456789|999666333), using a pipe, comma, semicolon, or similar separator.

Gift - Honoring /
Gift - Tribute

Tribute related mapping destinations are covered in Importing Tributes.

Gift: [Custom Field Name]

Gift-scope custom fields will appear next, labeled as Gift: [Custom Field Name]

Still looking for what you need?