Field Mapping tells Enginy what data to send to Pipedrive Persons and Organizations during an export, and what should happen when the destination field already contains a value.

Note: Pipedrive does not offer a general two-way field sync in Enginy. Field Mapping controls the output from Enginy. Changes made directly in Pipedrive do not flow back into Enginy automatically.

Opening Field Mapping

Go to Integrations.
Find PipeDrive and click Configure.
Open Field Mapping.
Choose Contacts or Companies.

Contacts are exported as Persons and companies as Organizations. There is no Leads tab. The Create Leads from Contacts and Create Leads from Companies options can create additional Leads, but they do not let you map custom fields on the Lead object.

Initial mapping

When you connect Pipedrive, Enginy prepares these mappings:

Contacts

Enginy field	Pipedrive field
First name	first_name
Last name	last_name
Professional email	email
Mobile phone	phone

Companies

Enginy field	Pipedrive field
Company name	name

Add Website, LinkedIn profile URL or other fields if you are going to use them for matching or exporting.

Field Mapping sections

Field Mapping

Connects an Enginy field with a Pipedrive field. To add a relationship:

Open Contacts or Companies.
Add a row.
Select the Enginy field.
Select the Pipedrive field.
Choose the overwrite rule.
Click Save Changes.

Custom Fields

Use this section when you need to create or manage a field specifically for the integration.

Important: Changes made from Custom Fields can apply immediately. Discard does not guarantee they will be undone. Review the name and the type before confirming the creation.

Fixed Fields

Always sends the same value to the Pipedrive field. For example, you can set Enginy as the value of a source custom field for every record included in the mapping.

Manual Export Fields

Asks for a value every time you open Export to CRM. It is useful for data that changes per operation, such as a region, a source or a category.

Engagement Fields

Updates a field when Enginy logs a related activity. Use it for engagement data that should reflect the most recent activity.

Choosing compatible fields

Connect equivalent types wherever possible:

Enginy value	Recommended Pipedrive field
Text or URL	varchar, text or varchar_auto
Number	double, monetary or a compatible numeric type
Date	date or datetime, after testing
Single select	enum
Multiple select	set

The blue check inside a selector marks the selected option. On its own it does not prove that the two types are compatible.

A yellow warning flags a possible incompatibility. You can review the mapping, but it is worth testing it with one record before exporting a list.

An option with a red x is disabled for that selection. Read the reason shown in the interface and choose another field. Do not assume every red x means Pipedrive considers the field read-only.

Pipedrive does not expose equivalent types for every Enginy value. If you work with URLs, booleans or conversions between types, use a compatible field and validate the result.

enum and set fields

Pipedrive uses enum for single select and set for multiple select.

Choose the options from the dropdown. Enginy sends the numeric IDs Pipedrive expects.

Do not type internal names or labels manually if the selector lets you pick the value. An AI Variable or a text column does not automatically become a valid option either.

If a value cannot be resolved to an allowed option, Enginy skips that field and continues with the rest of the record. Check the Export Report to identify it.

Date fields

Do not assume Enginy will always convert the date into a specific text format. Test with one record and check how Pipedrive receives the value.

If a warning appears or Pipedrive rejects the value, use a different field type or contact Support before a bulk export.

Choosing the overwrite rule

Each mapping can offer two behaviors.

Sync with Pipedrive

Enginy fills the field in if the destination is empty. If Pipedrive already has a value, it keeps it.

The name does not mean the value comes back from Pipedrive into Enginy, and it does not turn on a two-way sync.

Enginy overwrites Pipedrive

Enginy can replace the existing Pipedrive value during the export. Use it only when Enginy should be the source of truth for that field.

The initial configuration keeps existing values. On each export you can also decide which specific fields should be overwritten, from Overwrite existing values.

Saving and validating

Click Save Changes.
Confirm with Save.
Export a single record.
Check the fields written in Pipedrive.
Review the Export Report.
Test the keep and overwrite rules separately.
Move on to more records when the result is correct.

Solving common problems

A Pipedrive field does not appear

Check that it belongs to the right object, Person or Organization, and that the Integration user can see it. Reopen Pipedrive Setup. If it still does not appear after changing permissions or creating the field, reconnect.

A yellow warning appears

Review both field types. If they are not equivalent, create a compatible custom field in Pipedrive, or use text when you do not need a conversion.

The record exports, but a field stays empty

Check that Enginy has a value, that the mapping is in Contacts or Companies as appropriate, that the Pipedrive option still exists, that an enum or set received a valid option, and that the Export Report does not show the field as skipped.

There is no Leads tab

That is expected. Field Mapping only includes Contacts and Companies for Pipedrive.

Which records Enginy may create

Two settings decide whether Enginy creates a record in Pipedrive that it could not match. They are the most common reason a contact "never arrived".

The creation toggles

In Sync configuration you will find two switches, both on by default:

Create contacts in Pipedrive when no match is found
Create companies in Pipedrive when no match is found

Turn one off and Enginy updates what it matches and skips the rest. Nothing new is created for that entity.

Required fields for creation

Each row in the Field mapping table has a checkbox in the Required column. Tick it and a record missing that field is skipped instead of created.

Good to know: This never blocks an update. A record that already exists in Pipedrive keeps being updated as usual, because the rule only gates creation.

Three things worth knowing before you use it:

One configuration covers every CRM. The check runs on the Enginy values, before they are translated into Pipedrive field names. If you connect a different CRM later, the same rules apply.
0 and false count as filled in. A field is only missing when it is empty, contains nothing but spaces, or is an empty list.
Turning creation off does not erase your selection. The list stops applying while the toggle is off, and comes back untouched when you turn it on again.

The checkbox is disabled while creation is off for that entity. Enable the matching toggle in Sync configuration first.

The rule that always applies

Always: A contact with no email, no phone, no LinkedIn URL and no CRM ID cannot be exported at all, whatever you configure here. Enginy would have no way to match or identify it in Pipedrive.

Where you see the effect

Export to CRM checks your selection before running and tells you how many records are missing required fields. If every record in the selection would be skipped, it blocks the export with None of these contacts will be created in your CRM.

These rules also apply to automatic campaign syncs, not just manual exports.

Configure Field Mapping and overwrite rules in Pipedrive