Matching defines how Enginy recognizes the Persons and Organizations that already exist in Pipedrive before exporting. A reliable configuration reduces duplicates and avoids associating a contact with the wrong company.
Note: Matching is applied during exports from Enginy. It does not keep both systems synced in real time. To bring data from Pipedrive into Enginy, start an import.
Opening Sync Configuration
Go to Integrations.
Find PipeDrive.
Click Configure.
Open Sync Configuration.
Configure the company identifier first. Matching contacts by name also needs to locate the associated Organization.
Choosing the Contact Identifier
You can choose between three strategies.
First name + Last name + Company name
Enginy looks for a Person by their full name within the corresponding Organization.
This option works best when:
The first and last names are complete.
The contact has a company associated in Enginy.
The Organization already exists or can be identified correctly.
The name match is exact. If Enginy cannot locate the company, it cannot complete this Person search.
LinkedIn profile URL or First name + Last name + Company name
This option requires a Person field in Pipedrive that stores the LinkedIn URL.
Identify or create that custom field in Pipedrive.
Open Field Mapping.
Connect LinkedIn profile URL with the Pipedrive field.
Save your changes.
Go back to Sync Configuration and select this identifier.
The behavior matters:
If the contact has a LinkedIn URL, Enginy searches by that URL.
If it has no URL, it searches by first name, last name and company.
If it has a URL but no match is found, Enginy does not fall back to searching by name and company.
Check that the URLs have a consistent format in both systems before using this option at scale.
Custom Mapping
Connects a single Enginy contact field with a Pipedrive Person field.
Matching looks for an exact match. Choose a stable and, if possible, unique value, such as an external identifier. Avoid job titles, company names or other values that can change or repeat.
Choosing the Company Identifier
The Company Identifier determines how Enginy looks for an Organization before creating one.
Website or company name
This is the initial option and usually the most flexible. Enginy tries to use Website and can fall back to the company name.
For the Website part to work, you must map that value to a Pipedrive Organization field. The initial configuration only includes Company name, so if you do not add Website in Field Mapping, matching will normally depend on the name.
Website
Use this option when your Enginy companies have a Website, Pipedrive stores that value in an Organization field, and both fields are connected in Field Mapping.
If the mapping is missing, Enginy has no Pipedrive field to compare against.
Custom Mapping
Connects a single Enginy company field with a Pipedrive Organization field.
The match is exact. This option is useful when both systems share a stable identifier that does not depend on the name or the website.
Domain and Domain or company name
These options also appear in the selector. Before relying on them as your only protection against duplicates, test them with real records from your account.
If Domain does not find the matches you expect, use Website, Website or company name, or Custom Mapping. They are more controllable alternatives for the current configuration.
Check for any domain widens the search by removing the domain extension and using a looser match. It can help when a company uses several extensions, but it also increases the risk of linking different Organizations. Turn it on only after testing a sample.
Configuring associations
Sync Configuration includes two preferences:
When exporting contacts, associate them with companies in Pipedrive.
When exporting companies, associate them with contacts in Pipedrive.
When you export, also review the association options in the Export to CRM modal. That modal controls what will be included in that specific operation.
Important: Pipedrive stores a single primary Organization in each Person's org_id field. If you associate an existing Person with a different Organization, the previous association can change.
If you do not want to change an existing association, turn that option off for the export and check the result with one record before continuing.
Saving and testing
Click Save Changes.
Confirm with Save.
Export a related company and contact.
Check that Enginy reused the correct records.
Review the Organization associated with the Person.
Check the Export Report.
Move on to a larger selection only if the result is correct.
If duplicates appear
Check whether:
Enginy could not identify the contact's company.
The Person's name differs between Enginy and Pipedrive.
You chose LinkedIn, but the field is not mapped.
The LinkedIn URLs do not match.
You chose Website, but it is missing from Field Mapping.
The Custom Mapping value is empty, repeated or written differently.
The Integration user cannot see the existing record.
Changing the identifier does not merge duplicates that were already created. Fix or merge those records before repeating a large export.