Skip to main content

Candidate-Contact Field Sync: Limits and Known Behaviors

Plan gating, same-type mapping rules, two-way sync, and two open behaviors not yet confirmed by Product (duplicate emails, parent-child custom fields).

Written by Amogh Balikai

Who this is for: All users.

Limit or behavior

What happens

Plan availability

Field Sync is only available on Platform and AIRA plans. It won't appear on lower-tier plans

Admin-only setup

Only Admins can enable sync and create or edit mappings. Other roles can trigger a sync by editing a mapped field, but can't configure mappings themselves

Same-type custom field mapping only

A custom field can only map to another custom field of the identical type (single-select to single-select, and so on). Mapping across different field types isn't supported

New option values get added, not rejected

If you pick a new value on a mapped single- or multi-select field, that value gets added to the matched field's option list on the other entity rather than being blocked

Sync runs in both directions

Editing either the candidate or the contact side updates the other. There's no one-way sync option

Did this answer your question?