Before creating a record, Enginy tries to find out whether it already exists in Dynamics. Accurate matching reduces duplicates and avoids updating the wrong record.
Note: The matching described here is used when searching for records in Dynamics. The Match with existing contacts or Match with existing companies option in an import searches for matches inside Enginy and follows different logic.
When the record is already linked
When identifying a Contact, Lead, or Account, Enginy stores its Dynamics ID. Later operations use that ID.
Matching criteria are needed again when the Enginy record does not yet have an associated ID. Enginy can only find records visible to the user who connected Dynamics.
Where to configure it
Go to
Integrations.Open Microsoft Dynamics with
Configure.Go to
Sync configuration.Review
Contact identifierandCompany identifier.Save with
Save Changes.
The Contacts or Leads option determines which entity is searched for people.
Contact and Lead matching
If the Enginy contact has Professional email, Enginy always uses it as a possible match, even when you select another identifier.
Contact identifier selector in Dynamics configuration
First name, Last name, and Company name
Enginy tries to find a match through any of these paths:
Exact Professional email.
First name, last name, and company.
The company can match through the ID of an already linked Account or through its name. For Dynamics Leads, it can also use companyname when there is no Parent Account.
First name must match exactly. For a multi-word last name, Enginy accepts a match with the first term or a match that contains the full last name.
LinkedIn Profile URL or name and company
Enginy tests these independently:
Exact Professional email.
Exact LinkedIn Profile URL.
First name, last name, and company.
To use LinkedIn Profile URL, first map that data to the correct Dynamics field. Without that mapping, Enginy does not know which field to search for the URL.
Custom mapping
Custom matching configuration for Contacts or Leads
You can create several groups of conditions:
Fields in the same group are combined with
AND.Groups are combined with
OR.Professional email is still tested as an additional condition when available.
Fields used in custom matching must also exist in Field mapping. Choose data that is unique and consistently populated.
Why not every criterion has to match
The main paths are combined with OR. If a person matches by Professional email, Enginy may select that person even if their LinkedIn Profile URL, name, or company do not also match.
This helps when data is missing, but it makes it important to keep emails and URLs unique in Dynamics.
Account matching
Enginy Companies are always searched in Dynamics Accounts.
Company identifier selector in Dynamics configuration
Website
Enginy searches for Accounts whose websiteurl contains the Enginy Website. This is not an exact URL comparison, so protocol, subdomain, or additional text can affect the result.
Website or Company name
Enginy searches through either of these paths:
websiteurlcontains the Enginy Website.The Account name exactly matches the Company name.
Custom mapping
Within a group, conditions are combined with AND. Different groups are combined with OR. Custom comparisons are usually exact, except for the special Website handling explained below.
What Check for any domain does
This option extracts the domain without its extension and searches for that text inside websiteurl. It can help match variants such as .com and .es, but the search is broader than equivalence between extensions.
A short or generic domain could appear inside another company's URL. Enable it only after reviewing that risk.
If Dynamics returns several results
Enginy uses the first returned record. There is no screen to choose between candidates, and Dynamics order should not be used as a deduplication method.
Before exporting in volume:
Review duplicate Professional emails in Contacts or Leads.
Review Accounts with the same name or Website.
Check that LinkedIn Profile URL is unique.
Test matching with a few records.
If no match is found
During an export, Enginy creates a new Contact, Lead, or Account according to the configuration. If associations are enabled, it can also create the related object and set the Parent Account.
Recommended configuration
Data quality | Recommended option |
Complete and unique professional emails | Keep Professional email mapped correctly. Enginy tests it automatically. |
Reliable LinkedIn Profile URL in both systems | Use the LinkedIn option and map the URL. |
Normalized company Websites | Use Website or Company name. |
Several extensions for the same brand | Consider |
Your own unique identifier | Use Custom mapping with fields that are always populated. |