Customizable Field Mapping

Updated a month ago ​by Sanne Stevens

What is Customizable Field Mapping? 

Customizable Field Mapping allows you to create custom mappings so you can define which contact fields should be kept in sync between your applications, including custom fields.

Customizable Field Mapping is available from the Pro or Medium Plan and onward only.

You can set up customizable field mappings 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 after. 

Below you see an example. Of course, this is dependent on the apps you have connected and which (custom) fields you have available on both sides.

What are Custom Fields?

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

What is a custom mapping?

Two fields* (standard or custom) kept in sync, defined by the user.  

*Some standard fields are already synced in the default field mapping.

Are custom mappings always two-way? 

The custom mappings will sync in the direction you have set up in the configuration of your connection, so this could be either 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 integration such as PieSync.
  • When it's technically not possible to read from or push to a particular field.
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. 


IMPORTANT SIDE NOTES

Why are my (custom) fields not showing in the custom mappings dropdown OR  greyed out?

  1. Each field can only be mapped once.

  2. Fields that are used in the built-in mappings (default field mapping), can not be used in the custom mappings.

  3. 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 greyed out. 

  4. Some types of custom fields (and app & integration dependent) are technically not mappable (drop-down, lists, multiple values)

  5. Fields with multiple values (see example below) can’t be synced in a custom mapping. In some cases, they are synced in the default field mapping. With multiple values, we mean fields such as emails, phone numbers and addresses where each value has a label to differentiate between ‘home’, ‘work’ and ‘other’ for example.

Why can't I set up any custom mapping? 

This could be caused by one of the following reasons: 

  • All standard fields were already mapped by default
  • There are no other (custom) fields available/left to map
  • There are no compatible fields left to map
Don’t forget to read our Blog Post about our Customizable Field Mapping feature! 

How did we do?