> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Blinq Microsoft Dynamics field reference

> Contact field mapping, custom fields, and deduplication behavior for the Blinq Microsoft Dynamics integration.

<Info>
  Blinq syncs contact data to fields on the Dynamics Contact record, and to the Lead record when you enable Lead creation. Blinq creates the custom fields it needs automatically when you connect the integration.
</Info>

## Contact field mapping

If the following information is present on the Blinq contact, Blinq syncs it to the corresponding Dynamics field.

| Blinq contact field         | Dynamics field                                     |
| --------------------------- | -------------------------------------------------- |
| First name                  | firstname (required)                               |
| Last name                   | lastname (required)                                |
| Job title                   | jobtitle                                           |
| Company                     | companyname (Lead) / Parent account link (Contact) |
| Email (first/primary)       | emailaddress1                                      |
| Email (secondary)           | emailaddress2                                      |
| Email (tertiary)            | emailaddress3                                      |
| Phone number                | telephone1                                         |
| Mobile phone                | mobilephone                                        |
| Additional phone numbers    | telephone2, telephone3                             |
| Company website/URL (first) | websiteurl                                         |
| Notes                       | Notes (on the Contact or Lead record)              |

To customize which fields Blinq syncs and how they map, see [Blinq field mapping](/features/field-mapping).

## Custom fields created by Blinq

<Info>
  You can only map fields that exist on **both** the Contact and Lead entities.
</Info>

Blinq creates the following custom fields in Dynamics when you connect the integration, and uses them to sync tags and campaign attribution.

| Field name           | Description                               |
| -------------------- | ----------------------------------------- |
| Blinq Contact Tags   | Contact-level tags applied in Blinq       |
| Blinq Workspace Tags | Workspace-level tags                      |
| Blinq Campaign Tags  | Campaign tags from linked Blinq campaigns |
| Blinq Campaigns      | Names of linked Blinq campaigns           |
| Blinq Card Link      | A direct link to the contact's Blinq card |

## Deduplication

When you export a Blinq contact to Dynamics, Blinq looks for an existing record with the same email address (or phone number if there's no email) across both Contacts and Leads.

If Blinq finds a record it already manages, it updates it. If it finds a record created elsewhere, Blinq leaves it untouched to avoid overwriting another source's data. Blinq never merges Leads and Contacts; combining them is a Dynamics action.

Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely.

<hr />

### Need help?

For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).