Who this is for: Admins setting up field mappings.
Getting the most out of Field Sync starts with mapping the right fields, not all of them. Here's what to think through before you turn on a mapping.
Map fields that describe the same person, not the same role. Title, company, and contact info make sense to sync because they're facts about a person. Pipeline-specific fields like a hiring stage usually don't, because a candidate's hiring stage and a contact's deal stage aren't the same thing
Start with system fields before custom fields. System fields use Recruiterflow's built-in logic out of the box. Get those mapped and confirmed first, then layer on custom fields once you're confident in how sync behaves
Avoid mapping fields different teams "own." If your BD team and your recruiting team would disagree about what a field should say at any given moment, sync will force one team's edit onto the other team's record, every time
Re-check your mappings whenever you add a new custom field type. A field that looked safe to map as single-select can become a problem once someone changes it to multi-select
Don't map anything you're not ready to lose independent control over. Once mapped, an edit on either side updates the other immediately. There's no review step or warning before the overwrite happens