> For the complete documentation index, see [llms.txt](https://docs.neodove.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neodove.com/admin-portal/contacts/upload-contacts.md).
# How to Upload Contacts?
{% hint style="success" %}
The "**Uploading Contacts**" feature in the NeoDove portal serves the purpose of creating new campaigns and adding leads to them or rerouting leads to existing campaigns.
{% endhint %}
This functionality simplifies the process of initiating new campaigns or integrating leads into ongoing ones, providing a streamlined approach to lead management and campaign creation.
### Steps:
***
1. **Log in** to your NeoDove account ( )
2. Go to the **Contacts** Section.
3. Click the "**Upload Contacts**" option available at the top of the screen.
4. As soon as you click the button a **pop-up** will appear. Select your file containing all the leads.
5. Once you have selected the file, this will redirect you to select the **campaign**. There are two ways:
* **Creating a new campaign -** If you intend to initiate a new campaign using a specific file, you should select the option to "**Create a New Campaign**" within the NeoDove portal.
{% hint style="success" %}
This choice allows you to set up a **fresh campaign** specifically tailored to the leads contained in the file, ensuring an organized and targeted approach to your **campaign management**.
{% endhint %}
* **Add Leads in an Existing Campaign -** If your goal is to redirect the leads from the file to an **existing campaign**, you can choose this option within the NeoDove portal. During this process, you will be prompted to select the **specific campaign** to which you want these leads to be re-directed.
{% hint style="success" %}
This option allows for efficient lead distribution and ensures that the leads seamlessly integrate into the **ongoing campaign** of your choice.
{% endhint %}
6. Select the “**Campaign Type**”, if you want to create a new campaign while uploading the data.
7. Select the “**Campaign Name**”, if you want to add the leads in an existing campaign. Then after selection, click on the **Next button** to continue.
8. You will now have to **map the fields** or the **columns** from the data with the particular fields of the system.
9. Then select the "**Duplicacy Settings**" where there are four options to be chosen:
***
* **Ignore Duplicate -** All the duplicates will be ignored or deleted. It just won’t get uploaded.
* **Merge Duplicate -** All the duplicates will get merged and will show as one lead only. In that particular lead, all the details will be visible collectively.
* **Create Duplicate Leads -** There will be no checking of duplicates. All leads, including duplicates, will get uploaded as is, as independent leads.
* **Merge Duplicate and Reopen Closed Leads -** In the case of any closed lead, if a fresh inquiry comes in once again then the duplicates (fresh inquiry and already closed leads) will get merged and it would gradually reopen again and get assigned to the Users as a fresh lead**.**
10. After setting up the required **Duplicacy Settings**, then click on Next to proceed further.
11. Need to map the Custom Contact Properties **(CCP)** as well then with the fields from the data.
12. After clicking on “**Submit**”, the data will get uploaded with a **push notification**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.neodove.com/admin-portal/contacts/upload-contacts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.