When you integrate Marketo with SFDC instances that have been used for a while, it may happen that leads and contacts what a similar field (same name / same API name). Marketo will automatically map them (i.e. create only 1 field in Marketo that sync's with both the lead and contact field).
Other situations are when SFDC admins make errors in creating new fields and you end up with one field in Marketo that maps with 2 SFDC (1 lead / 1 contact) fields but one of them needs to be deleted in SFDC and recreated.
So we would need to be able to "tell" Marketo that these 2 fields are not the same one and "unmap" them, which would create a second Marketo field mapped to contact or account, while the first one remains mapped to the lead.
On the other end, I would also need to be able to map (merge 2 Marketo fields that were created from sync with 2 SFDC fields with different API names) fields myself.
Of course, all this can be done by support but:
1/ the time taken to create a ticket and have it resolved is a slowdown in the project
2/ this is unnecessary burden for the Support team
3/ Support will only accept to map / unmap a few fields and after a while will ask that we go through PS, which give the customer impression that Marketo is charging for product weaknesses.
This idea has to be combined with others:
At the end of the day, what we would need on this is to make the Self-mapping and self-healing capabilities really complete and in addition let the Marketo admin have all the tools in hands to correct any issue that a fully automated system would create because of the potentials flaws in the source system (i.e. Salesforce) data schema.
.png)