# Import a Donor

The **Donors Import** feature allows you to add a large number of donors to the system at once, instead of entering them individually. This is ideal for importing existing donor lists or onboarding donors in bulk.

### Accessing the Donors Import

* In the left sidebar, navigate to **List**.
* Under the **List** category, click **Donors**.
* On the top-right corner of the Donors screen, click the **three-dot (More Actions) icon**.
* Select **Import**.
* Choose **Import Donors**.

### Import Method Overview

Donors are imported using an **Excel template**. The system automatically recognizes each column and creates donor records based on the data you provide.

To ensure a successful import, it is critical to use the provided template exactly as instructed.

### Excel Template Structure

* In the Import Donors window, click **Download Excel Template**.
* The file will automatically download to your computer’s Downloads folder.
* Open the file in Excel.
* Click **Enable Editing** to begin entering data.

{% hint style="info" %}
NOTE!&#x20;

* **Rows 1 and 2** cannot be **deleted** or **edited**, as they are required for the system to import the file correctly.
* **Rows** **3 and 4** in the spreadsheet contain **example entries,** and are provided as a formatting guide.
  {% endhint %}

### Column descriptions

Work from **left to right**, using the example rows as a guide for formatting.

#### <mark style="color:$primary;">Donor Account Number</mark>

* Enter a **unique donor account number**.
* This number **must not already exist** in your donor list.
* If an existing account number is used, **all donor information for that account will be** [**updated**](/overview/lists/donors/update-a-donor.md).
* The account number acts as the donor’s primary identifier.

{% hint style="info" %}
**NOTE:** Account numbers for imported donors cannot start with **DNR**. The **DNR** prefix is reserved for donors created directly in the DRM, where the system automatically assigns a default account number starting with **DNR**.
{% endhint %}

***

#### <mark style="color:$primary;">Donor Name (English)</mark>

* **Title (English)**: e.g., Mr., Mrs., Miss, Rabbi
* **First Name (English)**
* **Last Name (English)**

***

#### <mark style="color:$primary;">Donor Name (Hebrew / Yiddish)</mark>

* **Title (Hebrew/Yiddish)**: e.g., Harav
* **First Name (Hebrew/Yiddish)**
* **Last Name (Hebrew/Yiddish)**
* **Suffix (Hebrew/Yiddish)**: e.g., Shlita

***

#### <mark style="color:$primary;">Home Address</mark>

* **House Number**
* **Street**
* **Apartment**
* **City**
* **State**
* **ZIP Code**
* **Country**

Use the example row to ensure proper formatting.

{% hint style="success" %}
To customize the address label[^1], update the text **after the colon** in the column header.

For example: HouseNum:Home TO HouseNum:Office

**Important!** The label must be updated across ALL corresponding address columns for the import to process correctly.
{% endhint %}

***

#### <mark style="color:$primary;">Phone Numbers</mark>

**Home Phone**

* **Home Phone Country Code -** If left blank, the default is **USA**
* **Home Phone**&#x20;

**Cell Phone**

* **Cell Country Code -** If left blank, the default is **USA**
* **Cell Phone**&#x20;

Additional phone columns (e.g., Cell 2, other) can be used as needed.

{% hint style="info" %}
**Country Code** identifies the country associated with the phone number and ensures messages are sent with the correct international dialing code. For example, an Israeli phone number must use the **ILS** country code so the system knows to apply Israel’s dialing prefix when sending texts.
{% endhint %}

{% hint style="success" %}
To customize the Phone Number label[^1], update the text **after the colon** in the column header.

For example, CountryCode:Home **TO** Countrycode:Office

**Important!** The label must be updated in both the country code AND phone columns for the import to process correctly.
{% endhint %}

***

#### <mark style="color:$primary;">Email Addresses</mark>

* **Personal Email**
* **Business Email**

{% hint style="success" %}
To customize the email label[^1], update the text **after the colon** in the column header.

For example, Email:Business **TO** Email:Home
{% endhint %}

***

#### <mark style="color:$primary;">Family Tree Information</mark>

Family relationships appear on the donor card’s [**Family Tree**](/overview/lists/donors/add-a-donor.md#family-tree-tab) section.

<i class="fa-hand-point-right">:hand-point-right:</i> **Plain Text Entry**

* To display a name only, use the **Donors Father** and **Donors Father-in-law** columns. These fields are **display-only**—if they are filled in, the father or father-in-law will **not be linked** to the donor and will appear as text only.

<i class="fa-hand-point-right">:hand-point-right:</i> **Linked Donor Accounts**

* To display a linked name, use the **Donors Father Account Number** and **Donors Father-in-law** **Account Number** columns. The referenced account numbers can belong to donors listed anywhere in the import file (for example, in another row) and do **not** need to be pre-existing donors in the DRM.&#x20;
* Enter the **related donor’s account number**.
* This creates a **clickable hyperlink** to that donor’s card.

<details>

<summary>See family tree in Donors card:</summary>

<figure><img src="/files/BNjK6guBigXEX5SiKQYB" alt=""><figcaption></figcaption></figure>

</details>

***

#### <mark style="color:$primary;">Custom Fields</mark>

The template includes predefined [custom field](/cloud-drm/getting-started/setup-and-configuration/advanced-fields.md#custom-fields-features) columns.

* To **rename** a custom field:
  * Edit the column header **after the colon**.

{% hint style="info" %}
This will create a new custom field in the DRM
{% endhint %}

***

#### <mark style="color:$primary;">Tags</mark>

* You may assign **multiple** [**tags** ](/cloud-drm/getting-started/setup-and-configuration/advanced-fields.md#tags-features)to a donor.
* Separate tags with a **comma**.

{% hint style="info" %}
This will create a new tag in the DRM
{% endhint %}

***

#### <mark style="color:$primary;">Location IDs</mark>

* Enter the **Location ID** (not the location name).
* Please contact Customer Support to obtain the required Location IDs.
* Multiple [locations ](/overview/lists/donors/add-a-donor.md#locations-tab)may be assigned by separating IDs with commas.

***

#### <mark style="color:$primary;">Business Address</mark>

If applicable, fill in:

* **Business Name**
* **House Number**
* **Street**
* **Apartment**
* **City**
* **State**
* **Zip Code**
* **Country**

{% hint style="info" %}
The **business address** will be used for **tax** purposes if the donor requires a receipt issued to their business.
{% endhint %}

***

#### <mark style="color:$primary;">Adding Additional Addresses</mark>

* To add more addresses:
  * Copy columns **AI through AP**
  * Paste them starting in column **AQ** and onward
* Each copied set represents an additional address.

***

### Uploading the File

1. Save and close the completed Excel file.
2. Upload it through the Import Donors window.

Once the upload begins:

* The system processes the file automatically.
* The user who initiated the import will receive an **email notification** with the import status.
* If any errors occur, the email will include details.

[^1]: A category for a phone number, email, or address that defines its type. In example: **Home**, **Business** etc.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.donary.com/overview/lists/donors/add-a-donor/import-a-donor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
