🚀 Customizable Field Mapping
FIND OUT HERE IF YOU ARE ELIGIBLE TO USE THIS NEW FEATURE.
We now sync all your fields! This brand new feature allows you to create custom mappings, defining which contact fields should be kept in sync between your applications, including standard and custom fields.
You can set up the customizable field mapping below the default field mapping in the configuration. You can add an unlimited amount of mappings and remove, enable/disable them anytime. In case you add a custom field in the apps you are syncing, just click the refresh button and the field will appear in the custom mappings list.
Below is an example of how these custom mappings could look. Of course, this is dependent on the apps you connect and which fields you have available in each of them.
Custom fields are fields that are not part of the standard fields offered by the applications you are syncing. In most cases, they are added by the customer.
Two fields* (standard or custom) kept in sync, defined by the user.
*Some standard fields are already synced in the default field mapping.
The custom mappings will sync in the direction you have set up in the configuration of your connection, so this could be two-way or one-way.
However, there are some exceptions where a custom mapping can only sync one-way:
When certain contact fields are not allowed to be modified through a third-party (PieSync).
Below is an example of a field that can't be modified through a third-party and therefore only syncs one-way (→).
Bear in mind that, when you have your connection configured in the other direction (←), that direction will win.
Why are my custom fields not showing in the custom mappings dropdown?
Each field can only be mapped once.
Fields that are used in the built-in mappings (default field mapping), can not be used in the custom mappings.
Fields in a custom mapping must be of the same or a similar type. You can’t sync a numeric field to a date field for example. When selecting fields in a custom mapping, the list on the other side will only show the fields that can be mapped, unavailable mappings are either not visible or grayed out.
Some types of custom fields are technically not able to sync. Custom fields we don’t support are not shown in the list of fields you can sync when creating a custom mapping.
List fields can’t be synced in a custom mapping. In some cases, they are synced in the default field mapping. With list fields, we mean fields that have multiple values. Usually fields such as emails, phone numbers and addresses are lists and each value has a label to differentiate between ‘home’, ‘work’ and ‘other’ for example.
This could be caused by one of the following reasons:
- All standard fields were already mapped by default, and/or there are no custom fields available.
- The connection you are using wasn’t in the first wave of the roll-out. However we are currently in the middle of rolling out this feature for each connector app, so it will be part of the second wave in the next coming weeks.
- Customizable Field Mapping is available from the Medium Plan onward.