Field Mapping connects Enginy fields with the Contacts, Leads and Accounts fields in Zoho. It also controls whether Enginy can replace an existing value.

Note: Zoho does not have general bi-sync in Enginy. Changes made directly in Zoho do not come back into Enginy through Field Mapping.

Opening Field Mapping

Go to Integrations.
On the Zoho card, click Configure.
Open Field mapping.
Choose Contacts, Leads or Companies.

Companies corresponds to Zoho's Accounts module.

Initial mappings

When you connect Zoho, Enginy prepares these mappings.

Contacts

Enginy field	Zoho field
First name	First_Name
Last name	Last_Name
Professional email	Email
Mobile phone	Phone
Job title	Title
Contact country	Mailing_Country

Leads

Enginy field	Zoho field
First name	First_Name
Last name	Last_Name
Professional email	Email
Mobile phone	Phone
Company name	Company
Website	Website
Description	Description

Companies

Enginy field	Zoho field
Company name	Account_Name
Website	Website
Description	Description
Phone number	Phone

You can add, change or remove mappings according to your organization's configuration.

Available sections

Contacts and Companies include Field Mapping, Custom fields, Fixed value fields, Manual export fields and Engagement fields. Leads includes the same sections, except Engagement fields.

Fixed value fields always sends the same value.
Manual export fields asks for a value when you open the export.
Engagement fields updates a field when Enginy logs a compatible activity.
Custom fields lets you manage additional fields used by Enginy.

Important: Changes made inside Custom fields can be saved immediately. Discard does not necessarily undo a creation, edit or deletion made in that section.

Choosing the overwrite rule

Sync with Zoho

When creating a record, Enginy can send the configured value. When updating an existing one, it keeps the content Zoho already has and fills the field in if it is empty.

This name does not mean Zoho sends the value back to Enginy. It also does not turn on a two-way sync.

Enginy overwrites Zoho

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

Understanding the icons

The blue check inside the selector marks the chosen option. On its own it does not confirm that the types are compatible.
A yellow warning flags a possible type or options incompatibility.
A red x means the option is not available in that selector. Read the reason shown before choosing another field.

Zoho does not give Enginy all the metadata needed to reliably detect every read-only field. The absence of a warning also does not guarantee that a boolean or other special type is compatible.

Picklists and field types

Connect equivalent types wherever possible:

Enginy value	Recommended Zoho field
Text, email or URL	A compatible Text, Email or URL field
Number	A compatible Number field
Date	Date
Date and time	DateTime
Selection	Picklist or MultiSelect with compatible options

Zoho only accepts values allowed by its picklists. Test the mapping if the visible label, the translation or the internal value do not match.

Required fields

Zoho requires at least Last_Name for Contacts and Leads, and Account_Name for Accounts.

Your organization may have other required fields through layouts or configuration. If one is missing, Zoho can reject the whole record even when the rest of the mappings are correct.

Saving and validating

Click Save Changes.
Export a single record.
Check the result in Zoho.
Review Activity > Prospecting if a field was skipped or failed.
Test keeping and overwriting separately before exporting a full list.

Which records Enginy may create

Two settings decide whether Enginy creates a record in Zoho 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 Zoho when no match is found
Create companies in Zoho 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 Zoho 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 Zoho 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.

Important: There is one list for contacts, not one per module. "Contact" here means the Enginy entity, so the same required fields apply whether your contacts export to the Zoho Contacts module or to Leads.

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 Zoho.

This is separate from Zoho's own required fields. A field Zoho marks as mandatory still has to be filled for the record to be accepted, whether or not you tick it here.

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 resolve warnings in Zoho