Why can't I custom map my (custom) fields?
Let's have a look at some possible reasons:
Each field can only be mapped once.
The fields are mappable, but the data types of the selected fields don’t match.
Example: you want to match a number field in app A with a date field in app B. There is no way we can make a field mapping for that, so the fields are considered to be incompatible.
Some types of custom fields are technically not able to sync (e.g. drop-down fields / radio buttons / checkboxes).
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 (see image below).
When a field is read-only: Certain contact fields in your applications are not allowed to be modified through a third-party integration such as PieSync
Below is an example of a field that can't be modified through a third- party and therefore only syncs one-way (→). More in-depth information can be found here.
Bear in mind that the general direction of the sync decides your syncing behaviour. When you have your connection configured as a one way sync in the other way (←), the following message will pop up.
- There is an issue with the partner API that is preventing us from exposing this field properly. Mostly this is due to their API returning the data type inconsistently (and a consistent data type is a requirement for us to do a proper sync).
Example: syncing Mailchimp phone fields to Copper
You will not be able to sync a Mailchimp phone field directly into a Copper phone field because of 2 limitations in our sync engine:
- Copper never stores just one unique phone number but always does so in a group of mobile, home, work, ... numbers
- Mailchimp does not offer a phone field out of the box, but only offers it as a custom field, making it an unpredictable field for our sync engine.
The workaround solution :
Assuming the idea is to capture phone numbers through Mailchimp landing pages - you should set up a mapping from Mailchimp's phone field towards a Copper custom field. Name this custom field something like "Phone (entered through MC)". We understand this may not be ideal, but it will at least make the necessary data appear in Copper.
Note that PieSync will have no issues syncing between Google and Copper, since these both store phones in a group. Similarly, there are no issues either syncing the phone from Copper to Constant Contact, which holds a phone field out of the box available.