Import Reference Tables
When preparing a spreadsheet for import into DonorDock, you can map columns in your file to standard DonorDock system fields as well as eligible Custom Fields created by your organization.
The fields available for mapping depend on the type of import you are completing.
This guide provides reference tables for:
Contacts
Gifts
Activities
Notes
Pledges
Campaigns
Appeals
Funds
For step-by-step instructions on uploading, mapping, reviewing, and processing a file, see the Step-by-Step Import Guide.
Before You Begin: Donor ID vs. Account Number
Two fields that appear frequently throughout imports are Donor ID and Account Number. While both can identify an existing Contact, they serve different purposes.
Field | Purpose |
|---|---|
Donor ID | A unique identifier automatically created and assigned by DonorDock when a Contact is created. Use the Donor ID when updating existing DonorDock records whenever possible. |
Account Number | An identifier that can be assigned to a Contact. This field is appropriate for storing an ID or account number from a previous CRM, accounting system, or other outside database. |
If you are preparing a change file to update existing Contacts in DonorDock, including the Donor ID is the most direct way to identify exactly which Contact to update. You may also use Account Number when your organization maintains unique Account Numbers.
If neither Donor ID nor Account Number is available, DonorDock may use other Contact information to identify a possible existing record. See Detecting Duplicate Contacts During Import for details about Contact matching and Composite Matching.

Contact Import Fields
The Contact Import is used to create Contact records in bulk or update existing Contacts.
When creating a new Contact, at least one of the following must contain a value:
Account Number
Company/Household Name
First Name
Last Name
For individual Contacts, including First Name and Last Name is strongly recommended so DonorDock can create an appropriate display name. When updating existing Contacts, include Donor ID or Account Number whenever possible.
DonorDock Field | Description | Accepted Value or Format | Required |
Donor ID | Unique Contact ID automatically assigned by DonorDock. Recommended when updating an existing Contact. | DonorDock-generated alphanumeric ID | Existing Contacts only |
Account Number | Contact account number. May also store an identifier from another system. | Alphanumeric | Conditional |
Contact Status | Status of the Contact. | Active, Inactive, Archived | No |
Contact Type | Type of Contact record. | Individual, Organization, Household | No |
Company/Household Name | Name of an Organization or Household Contact. | Alphanumeric | Conditional |
First Name | Contact's first name. | Alphanumeric | Conditional |
Middle Name | Contact's middle name. | Alphanumeric | No |
Last Name | Contact's last name. | Alphanumeric | Conditional |
Contact's primary email address. | Valid email address | No | |
Main Phone | Contact's main phone number. | Valid phone number | No |
Address Line 1 | First line of the primary address. | Alphanumeric | No |
Address Line 2 | Second line of the primary address. | Alphanumeric | No |
Address Line 3 | Third line of the primary address. | Alphanumeric | No |
City | City for the primary address. | Alphanumeric | No |
State or Province | State or province for the primary address. | Alphanumeric | No |
Postal Code | Postal or ZIP code for the primary address. | Alphanumeric | No |
County | County for the primary address. | Alphanumeric | No |
Country | Country for the primary address. | Alphanumeric | No |
Owner | DonorDock user assigned as the Contact owner. | Valid email address for a DonorDock user | No |
Title | Honorific or title for the Contact. | Alphanumeric | No |
Addressee | Name format used in an address block or mail merge. | Alphanumeric | No |
Salutation | Name or greeting used when addressing the Contact in correspondence. | Alphanumeric | No |
Suffix | Name suffix, such as Jr., Sr., or PhD. | Alphanumeric | No |
Nickname | Contact's preferred nickname. | Alphanumeric | No |
Former Name | Name previously used by the Contact. | Alphanumeric | No |
Birthday | Contact's birth date. | MM/DD/YYYY | No |
Secondary Address | Secondary address field available for mapping in addition to the individual secondary address components. | Alphanumeric | No |
Secondary Address Line 1 | First line of the secondary address. | Alphanumeric | No |
Secondary Address Line 2 | Second line of the secondary address. | Alphanumeric | No |
Secondary Address Line 3 | Third line of the secondary address. | Alphanumeric | No |
Secondary City | City for the secondary address. | Alphanumeric | No |
Secondary State or Province | State or province for the secondary address. | Alphanumeric | No |
Secondary Postal Code | Postal or ZIP code for the secondary address. | Alphanumeric | No |
Secondary County | County for the secondary address. | Alphanumeric | No |
Secondary Country | Country for the secondary address. | Alphanumeric | No |
Business Phone | Contact's business phone number. | Valid phone number | No |
Mobile Phone | Contact's mobile phone number. | Valid phone number | No |
Fax | Contact's fax number. | Valid phone number | No |
Website | Contact's website. | Valid URL | No |
Facebook Username | Contact's Facebook username. | Alphanumeric | No |
Instagram Username | Contact's Instagram username. | Alphanumeric | No |
LinkedIn Username | Contact's LinkedIn username. | Alphanumeric | No |
Twitter Username | Contact's Twitter/X username. | Alphanumeric | No |
Spouse First Name | Spouse's first name. | Alphanumeric | No |
Spouse Last Name | Spouse's last name. | Alphanumeric | No |
Spouse Email | Spouse's email address. | Valid email address | No |
Spouse Mobile Phone | Spouse's mobile phone number. | Valid phone number | No |
Spouse Business Phone | Spouse's business phone number. | Valid phone number | No |
Spouse Birthday | Spouse's birth date. | MM/DD/YYYY | No |
Number of Children | Number of children associated with the Contact. | Numeric value | No |
Do Not Solicit | Indicates that the Contact should not be solicited. | True/False value | No |
Bad Address | Indicates that the Contact's address is known to be incorrect. | True/False value | No |
Deceased | Indicates that the Contact is deceased. | True/False value | No |
Unsubscribed | Indicates that the Contact is unsubscribed from marketing email. | True/False value | No |
SMS Unsubscribed | Indicates that the Contact is unsubscribed from SMS messaging. | True/False value | No |
Description | General description of the Contact. | Alphanumeric, up to 1,500 characters | No |
Affiliation | Affiliation associated with the Contact. | Alphanumeric | No |
Badges | Badges to assign to the Contact. Multiple badges may be included. | Comma-separated badge names | No |
Marketing Lists | Marketing Lists that should include the Contact. | Comma-separated list names | No |
Household | Household the Contact belongs to. If no matching Household exists, a new Household may be created. | Alphanumeric | No |
Household Role | Contact's role within the Household. | Alphanumeric | No |
Job Title | Contact's job title. | Alphanumeric | No |
Employer | Employer associated with the Contact. If no matching Employer exists, you may create a new Employer. | Alphanumeric | No |
Special Circumstances | Internal information or instructions related to engaging with the Contact. | Alphanumeric, up to 1,500 characters | No |
Gift Import Fields
A Gift Import can include both Contact fields and Gift fields. This allows DonorDock to identify or create the Contact associated with each Gift while importing the transaction.
When creating a Gift, the import must contain:
Gift Date
Gift Amount
Enough identifying Contact information to determine which Contact the Gift belongs to
You may also map Contact fields listed in the Contact Import Fields section during a Gift Import as long as each row ALSO contains enough information to create a gift.
DonorDock Field | Description | Accepted Value or Format | Required |
Gift ID | Unique identifier for the Gift. Use when working with an existing Gift. | Alphanumeric | No |
Gift Date | Date the Gift was received. | MM/DD/YYYY | Yes |
Campaign | Campaign associated with the Gift. DonorDock uses the Campaign name to locate the related record. | Alphanumeric | No |
Appeal | Appeal associated with the Gift. DonorDock uses the Appeal name to locate the related record. | Alphanumeric | No |
Fund | Fund associated with the Gift. DonorDock uses the Fund name to locate the related record. | Alphanumeric | No |
Gift Type | Type of Gift. | Donation, Membership, Event Ticket, Grant | No |
Gift Status | Status of the Gift. If omitted, the Gift defaults to Received. | Pledged, Received, Canceled | No |
Payment Type | Method used to make the payment. | Cash, Credit Card, Check, In Kind, Stock, ACH, PayPal, Payroll, Other | No |
Soft Credit Parent ID | Identifier for the parent Gift associated with a soft credit. | Alphanumeric | No |
Soft Credit Amount | Amount of the soft credit. | Decimal value greater than or equal to 0 | No |
Gift Amount | Amount of the Gift. | Decimal value greater than or equal to 0 | Yes |
Fee Amount | Processing fee associated with the Gift. | Decimal value greater than or equal to 0 | No |
Fees Covered | Indicates whether the processing fees were covered. | True/False value | No |
Matched Gift Parent ID | Identifier for the parent Gift associated with a matching Gift. | Alphanumeric | No |
Pledge ID | Identifier for the Pledge associated with the Gift. | Alphanumeric | No |
Pledged Amount | Amount associated with a pledged Gift. | Decimal value greater than or equal to 0 | No |
Non-Deductible Amount | Portion of the Gift that is not tax deductible. | Decimal value greater than or equal to 0 | No |
Check Date | Date shown on the check when Payment Type is Check. | MM/DD/YYYY | No |
Deposit Date | Date the payment was deposited. | MM/DD/YYYY | No |
Batch Name | Batch the Gift should be associated with. | Alphanumeric | No |
Payment ID | Payment identifier, such as a check number or transaction ID. | Alphanumeric | No |
Is Tribute | Indicates whether the Gift is a tribute. | True/False value | No |
Tribute Type | Specifies whether the tribute is in honor or memory of someone. | Honor, Memorial | Required for applicable tribute Gifts |
Tribute Message | Description or message associated with the tribute. | Alphanumeric | No |
Honoree Name | Name of the person being honored or memorialized. | Alphanumeric | No |
Dedication Contact Name | Name of the person who should be notified of the tribute Gift. | Alphanumeric | No |
Dedication Contact Address Line 1 | Address for the dedication Contact. | Alphanumeric | No |
Dedication Contact City | City for the dedication Contact. | Alphanumeric | No |
Dedication Contact State or Province | State or province for the dedication Contact. | Alphanumeric | No |
Dedication Contact Postal Code | Postal or ZIP code for the dedication Contact. | Alphanumeric | No |
Dedication Contact Country | Country for the dedication Contact. | Alphanumeric | No |
Dedication Contact Email | Email for the dedication Contact. | Valid email address | No |
Treat as Anonymous | Indicates whether the Gift should be treated as anonymous. | True/False value | No |
Tracking Code | Tracking code associated with the Gift. | Alphanumeric | No |
Payment Note | Internal note associated with the payment or Gift. | Alphanumeric | No |
Membership Type | Membership type associated with a Membership Gift. | Alphanumeric | No |
Membership Start Date | Start date of the Membership. | MM/DD/YYYY | No |
Membership End Date | End date of the Membership. | MM/DD/YYYY | No |
Receipt Sent | Indicates whether a receipt has already been sent for the Gift. | True/False value | No |
Gift Tags | Tags associated with the Gift. | Comma-separated tag names | No |
Activity Import Fields
Activity Imports can add completed or incomplete Activities to Contact records.
When creating an Activity, the import must contain:
Activity Type
Activity Date
Activity State
Subject
Enough identifying Contact information to associate the Activity with the correct Contact
DonorDock Field | Description | Accepted Value or Format | Required |
Donor ID | DonorDock-generated ID for the Contact associated with the Activity. | DonorDock-generated alphanumeric ID | Conditional |
Account Number | Account Number for the Contact associated with the Activity. | Alphanumeric | Conditional |
Company/Household Name | Organization or Household name used to identify the Contact. | Alphanumeric | Conditional |
First Name | First name used to identify the Contact. | Alphanumeric | Conditional |
Last Name | Last name used to identify the Contact. | Alphanumeric | Conditional |
Primary email used to identify the Contact. | Valid email address | Conditional | |
Secondary Email | Secondary email used to identify the Contact. | Valid email address | Conditional |
Activity ID | Unique identifier for the Activity. May be an ID from an external system. | Alphanumeric | No |
Type | Type of Activity being imported. | Email, Phone Call, Letter, Meeting, Task, Event Attendance, Volunteer, Ask, Receipt, Log Email, Log Text | Yes |
Subject | Subject or title of the Activity. | Alphanumeric | Yes |
Body | Body or description of the Activity. | Alphanumeric | No |
Activity Date | Date of the Activity. For future Activities, this may represent the scheduled date. | MM/DD/YYYY | Yes |
Due Date | Due date associated with the Activity when applicable. | MM/DD/YYYY | No |
Location Address | Location associated with a Meeting or other Activity. | Alphanumeric | No |
Hours | Number of hours associated with a Volunteer Activity. | Numeric value | No |
Activity State | Current state of the Activity. | Complete, Incomplete, Canceled | Yes |
Probability | Probability associated with an Ask when applicable. | Numeric value | No |
Ask Amount | Amount associated with an Ask. | Decimal value | No |
Planned Ask Amount | Planned amount associated with an Ask. | Decimal value | No |
Ask Board | Ask Board associated with the Activity. | Existing or mapped Ask Board name | No |
Ask Stage | Ask Stage associated with the Activity. | Existing or mapped Ask Stage name | No |
Project Board | Project Board associated with the Activity. | Existing or mapped Project Board name | No |
Project Stage | Project Stage associated with the Activity. | Existing or mapped Project Stage name | No |
Campaign | Campaign associated with the Activity. | Alphanumeric | No |
Appeal | Appeal associated with the Activity. | Alphanumeric | No |
Add to Action Board | Indicates whether the Activity should appear on the assigned owner's Action Board. | True/False value | No |
Completion Notes | Notes recorded when the Activity was completed. | Alphanumeric | No |
Completion Date | Date the Activity was completed. | MM/DD/YYYY | No |
Owner | DonorDock user assigned to the Activity. | Valid email address for a DonorDock user | No |
Notes Import Fields
Notes Imports allow you to add Notes to Contact records in bulk.
Your spreadsheet should include enough identifying Contact information to associate each Note with the correct Contact.
DonorDock Field | Description | Accepted Value or Format | Required |
Donor ID | DonorDock-generated ID for the Contact associated with the Note. | DonorDock-generated alphanumeric ID | Conditional |
Account Number | Account Number for the Contact associated with the Note. | Alphanumeric | Conditional |
Company/Household Name | Organization or Household name used to identify the Contact. | Alphanumeric | Conditional |
First Name | First name used to identify the Contact. | Alphanumeric | Conditional |
Last Name | Last name used to identify the Contact. | Alphanumeric | Conditional |
Primary email used to identify the Contact. | Valid email address | Conditional | |
Secondary Email | Secondary email used to identify the Contact. | Valid email address | Conditional |
Body | Content of the Note. | Alphanumeric | Yes |
Note Date | Date associated with the Note. | MM/DD/YYYY | No |
Owner | DonorDock user associated with the Note. | Valid email address for a DonorDock user | No |
Pledge Import Fields
Pledge Imports allow you to add Pledges to Contact records in bulk.
The import must contain enough information to associate the Pledge with the correct Contact. Whenever possible, use Donor ID or Account Number for the most reliable matching.
For a new Pledge, the following Pledge information is required:
Pledge Start Date
Pledge Status
Pledged Amount
DonorDock Field | Description | Accepted Value or Format | Required |
Pledge ID | Unique identifier for a Pledge. Include when identifying an existing Pledge. | Alphanumeric | Conditional |
Donor ID | DonorDock-generated ID for the Contact associated with the Pledge. | DonorDock-generated alphanumeric ID | Conditional |
Account Number | Account Number for the Contact associated with the Pledge. | Alphanumeric | Conditional |
Email address used to identify the Contact associated with the Pledge. | Valid email address | Conditional | |
Pledge Start Date | Date the Pledge begins. | MM/DD/YYYY | Yes |
Pledge Status | Current status of the Pledge. | Cancelled, Received, Pledged | Yes |
Pledged Amount | Total amount of the Pledge. | Decimal value greater than or equal to 0 | Yes |
Pledge Payment Interval | Frequency at which Pledge installments are expected. | Annual, Just Once, Monthly, Quarterly, None | Yes |
Number of Installments | Number of installments expected to fulfill the Pledge. | Whole number greater than or equal to 0. If not specified, will default to 1. | No |
Campaign | Campaign associated with the Pledge. | Alphanumeric | No |
Appeal | Appeal associated with the Pledge. | Alphanumeric | No |
Fund | Fund associated with the Pledge. | Alphanumeric | No |
Notes | Notes associated with the Pledge. | Alphanumeric | No |
Campaign Import Fields
Campaign Imports allow you to create Campaign records in bulk.
DonorDock Field | Description | Accepted Value or Format | Required |
Campaign Name | Name of the Campaign. | Alphanumeric | Yes |
Description | Description of the Campaign. | Alphanumeric | No |
Goal | Fundraising goal associated with the Campaign. | Decimal value | No |
Start Date | Campaign start date. | MM/DD/YYYY | No |
End Date | Campaign end date. | MM/DD/YYYY | No |
Type | Campaign Type associated with the Campaign. | Alphanumeric or mapped Campaign Type | No |
Record Status | Record status for the Campaign. | Valid DonorDock record status | No |
Appeal Import Fields
Appeal Imports allow you to create Appeal records in bulk.
DonorDock Field | Description | Accepted Value or Format | Required |
Appeal Name | Name of the Appeal. | Alphanumeric | Yes |
Description | Description of the Appeal. | Alphanumeric | No |
Goal | Fundraising goal associated with the Appeal. | Decimal value | No |
Start Date | Appeal start date. | MM/DD/YYYY | No |
End Date | Appeal end date. | MM/DD/YYYY | No |
Appeal Type | Type associated with the Appeal. | Alphanumeric or mapped Appeal Type | No |
Campaign | Campaign associated with the Appeal. | Alphanumeric | No |
Fund | Fund associated with the Appeal. | Alphanumeric | No |
Number Solicited | Number of individuals solicited through the Appeal. | Numeric value | No |
Solicitation Goal | Solicitation goal associated with the Appeal. | Numeric or decimal value | No |
Record Status | Record status for the Appeal. | Valid DonorDock record status | No |
Fund Import Fields
Fund Imports allow you to create Fund records in bulk.
DonorDock Field | Description | Accepted Value or Format | Required |
Fund Name | Name of the Fund. | Alphanumeric | Yes |
Description | Description of the Fund. | Alphanumeric | No |
Accounting Number | Accounting or external reference number associated with the Fund. | Alphanumeric | No |
Class Name | Accounting class associated with the Fund. | Alphanumeric | No |
Goal | Fundraising goal associated with the Fund. | Decimal value | No |
Fund Status | Status associated with the Fund. | Valid DonorDock Fund status | No |

Importing Custom Fields
The tables above list the standard system fields available in DonorDock. Your organization may also have additional Custom Fields available during an import.
Custom Fields let you import information specific to your organization's processes that isn't represented by a standard DonorDock field.
Depending on the import type, you may be able to map spreadsheet columns to:
Contact Custom Fields
Gift Custom Fields
Activity Custom Fields
For example, if your organization has a Contact Custom Field named Volunteer Interest, you can map a column in your Contact Import containing volunteer interest information directly to that Custom Field.
You must create a Custom Field in DonorDock before beginning the import.
The Import tool cannot create a new Custom Field from a spreadsheet column. If the field does not already exist, create it in your organization's Custom Fields settings before completing the import.
The values in each spreadsheet row will then be imported according to the type and configuration of that Custom Field.
Available Custom Field formats include:
Custom Field Type | Expected Data |
Text | Letters, numbers, or other text |
Number | Numeric values |
Checkbox | True/False values |
Date | Date values, typically MM/DD/YYYY |
Select | One available selection |
Multiselect | One or more available selections |
