> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/dynamics/dynamics-import.md).

# Dynamics - Import

Import contacts directly from your Microsoft Dynamics 365 Sales Marketing Lists, either as a standalone import or on the fly right before a campaign.

## Integration scope

* **Supported lists:** you can import from both Contact Marketing Lists and Lead Marketing Lists in Dynamics 365 Sales. Members of both list types are imported as eMarketeer contacts.
* **Imported fields:** eMarketeer imports the following core fields from Dynamics:
  * First Name
  * Last Name
  * Email Address
  * Company Name
  * Mobile Phone Number

## Method 1: standard import

Use this method to bring a Dynamics segment into eMarketeer for general database building or to group contacts into a specific eMarketeer list.

1. In eMarketeer, go to the **Contacts** section.
2. Click **Import contacts**.
3. Select **Microsoft Dynamics** as the import source.
4. In the search box, start typing the name of the Dynamics Marketing List you want to import.
5. Select the correct list from the dropdown of matching results.
6. Optional: choose whether the imported contacts should be added to a specific eMarketeer contact list.
7. Click **Import** to bring the contacts into eMarketeer.

## Method 2: import on the fly while sending an email

This is the fastest method. It lets you import a Dynamics segment and send a campaign in one step, without creating a standalone eMarketeer contact list.

1. When setting up a send-out in the eMarketeer UI, choose the option to select recipients.
2. Select the option to import from **Microsoft Dynamics**.
3. Search for and select your Dynamics Marketing List, as you would in the standard import.
4. eMarketeer imports the contacts and queues the campaign to send to that segment immediately.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/integrations/dynamics/dynamics-import.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.