Unmapped Custom Field Cleanup

[Anonymous]

Hi All!

We're very new to Marketo over here, and I'm seeing some unmapped custom fields in our field mapping tree (all that were created in Salesforce not Marketo).  Several of these our primary marketo marketing user needs to use when creating his smart lists, etc.  I'm struggling to find any documentation regarding this specific issue.  

It's a field on our contact record in Salesforce - I just created it on the lead page in Salesforce and mapped those in the CRM to see if that would help.  Do I need to set up a new marketo field for this to map properly?  Those were the only troubleshooting ideas I came up with.  I appreciate it!

Cheers,
 

Ann

[Anonymous]

Hey Ann,

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.

[Jep_Castelein2]

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. 

[Josh_Hill13]

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.

[Anonymous]

Thanks gents! I'll give these recommendations a try!