This content has been marked as final. Show 4 replies
Mapping of fields is something that support would be able to help you with. I would check in with them first before you start creating Mkto fields. If you ceate a number of them and it turns out you don't need them, you cannot delete them. You can hide them, but just dirties things up. Also, if the field already exists in Mkto, they can map an existing SFDC field to an existing Mkto field.
Ann, it is very common to have unmapped fields and it's usually not a bad thing. It just means that a particular field only exists on Lead, Contact or Account, but not on multiple objects.
However, if you have the same field on Lead/Contact or Lead/Account but the SFDC API name is different, then Marketo cannot automatically map those and you end up with 2 fields. In that case, contact Support to merge those fields.
You also need to remove references to those fields from ALL assets, lists, flows, etc.
So what I often recommend if this is a burden is to create new fields in SFDC that are properly mapped across Lead-Contact (for example) and then start using the new field in Marketo.
You can then use Marketo to migrate the OLD value to the NEW values if needed.
Thanks gents! I'll give these recommendations a try!