How to Set Up Microsoft Dynamics Field Mappings

Learn how to set up Microsoft Dynamics field mappings in Cognism to control exports, map data correctly, and manage update rules.

This guide explains how to map Cognism data to the correct fields in Microsoft Dynamics, configure export behaviour, and manage update rules. With the right setup, you can ensure consistent data, accurate reporting, and better CRM data quality.

Prerequisites

Before you start, you should:

  • Have Microsoft Dynamics connected to Cognism
  • Be an admin or have permission to configure integrations
  • Understand how you want Cognism data to appear in Dynamics

Open the Microsoft Dynamics field mapping settings

  1. In Cognism, click Integrations in the left-hand menu. 
  2. Select Microsoft Dynamics
  3. Click Setup
  4. Follow the setup steps until you reach Map data fields

Field mappings are configured during the Microsoft Dynamics integration setup flow.

Configure export behaviour

Navigate to Export Rules Tab to set export rules

Update rules to define what happens when Cognism finds an existing lead, contact, or account in Dynamics.

You can choose to:

  • Update existing prospect and related account records
  • Not update any existing records

These rules apply when exporting both new and existing data.

Syncing rules

Syncing rules control how prospects are created in Dynamics.

You can export prospects as:

  • Leads and Contacts
  • Leads only
  • Contacts only

Bulk export rules

Bulk export rules control whether account data is exported alongside leads and contacts during bulk exports.

Map Lead and Contact fields

Use the Lead/Contact step to map Cognism person data to Microsoft Dynamics fields.

For each Cognism field, select the Dynamics field you want to map it to from the dropdown.

All standard, out-of-the-box Dynamics fields are supported.

Available Lead and Contact mappings

Cognism fieldDescription
First NamePerson’s first name
Last NamePerson’s last name
EmailPerson’s primary email address
Company NamePerson’s company name
Job TitlePerson’s job title
Office PhonePerson’s office phone number
Mobile PhonePerson’s mobile phone number
CityPerson’s city
StatePerson’s state
CountryPerson’s country
StreetCompany street address
Zip CodeCompany postcode
WebsiteCompany website
IndustryIndustry the person works in

Map Account fields

Use the Account step to map Cognism company data to Dynamics account fields.

All standard Dynamics account fields are supported.

Available Account mappings

Cognism fieldDescription
Company NameCompany name
Company AliasCompany alias
Company WebsiteCompany website
Number of EmployeesEmployee count
IndustryCompany industry
Company TypeOrganisation type
Company CountryCompany country
Company StateCompany state
Company CityCompany city
Company AddressCompany headquarters address
Company PostcodeCompany headquarters postcode
Company PhoneCompany headquarters phone number
Company Year FoundedYear the company was founded

Use static value mappings

Additional mappings let you populate Dynamics fields with static values.

Static values apply the same value to every exported record. A common example is mapping a field such as Lead Source to a fixed value like Cognism.

Set update rules for individual fields

Each mapped field includes an update rule.

You can choose to:

  • Apply if blank – Cognism updates the field only if it is empty 
  • Always overwrite – Cognism updates the field every time you export or sync 

These settings can affect reporting and data accuracy.

 

Expected results

After configuring field mappings:

  • Cognism exports data to the correct Dynamics fields
  • Existing records are updated based on your rules
  • Static values are applied consistently
  • Field visibility and edit access are controlled during Chrome Extension exports

Next steps

  • Test exports with a small number of records
  • Review update rules to protect CRM data quality
  • Align field mappings with your Dynamics data standards
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.