SOLVED

Marketo vs SFDC mapping field

Go to solution
Channel_Expansi
Level 2

Marketo vs SFDC mapping field

Hello everybody,

do you know if it is possible to change/add/adapt mapping between Marketo and Salesforce field once "Sync NOW" button has been already pressed?

We introduced new Salesforce fields to be mapped into existing Marketo fields.

Thanks in advance

Dario

Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Robert_Solis1
Level 4

Re: Marketo vs SFDC mapping field

Hi Dario,

It sounds like you've found the answer but I'll still summarize the options.  After the initial sync has been initiated, the only options for adjusting the field mapping between Marketo and Salesforce is through Marketo Support.  Once the new field in Salesforce is created and shows up in Marketo, Marketo Support has two approaches that can be taken, either merge the new custom field with the pre-existing one or move the mapping from the new custom field onto the original field.  Before a Support Case is created it's best to do a little field prep first.  You'll want to populate the new custom field with the values your Leads already have from the original field.  This is allow the system to queue up and sync the values to Salesforce.  If a field merge or remap is done without the values being prepped it can results in values in Marketo not being pushed up for records.

For the difference between a field merge and remapping, it's really personal preference but I definitely prefer field merge.  This is a cleaner approach as the two fields will be combined resulting in a single field with the Salesforce mapping.  If a remapping is performed you'll still be left with two fields, just the mapping has been moved so then the discarded field will remain and need to be hidden or re-purposed.  Field merges can only be performed on two custom fields.  If one of the fields in question is a Marketo Standard Field then a remapping will have to be performed.  I hope this helps to shed some light on the situation!

View solution in original post

4 REPLIES 4
Channel_Expansi
Level 2

Re: Marketo vs SFDC mapping field

I read all the document that you kindly sent us and saying YES to my question is not so true...

It seems that Marketo map automatically new fields and admin cannot unmap apart asking support to Marketo

Thanks again, have a nice day

Chris_Johnston
Level 8

Re: Marketo vs SFDC mapping field

Which is why yes is true, in that yes it is possible if you talk to support. Your question was vague as to if a Marketo field was mapped already to Salesforce or just existed in Marketo and thus didn't need unmapping which is why I provided the support including where you can run into issues.

Robert_Solis1
Level 4

Re: Marketo vs SFDC mapping field

Hi Dario,

It sounds like you've found the answer but I'll still summarize the options.  After the initial sync has been initiated, the only options for adjusting the field mapping between Marketo and Salesforce is through Marketo Support.  Once the new field in Salesforce is created and shows up in Marketo, Marketo Support has two approaches that can be taken, either merge the new custom field with the pre-existing one or move the mapping from the new custom field onto the original field.  Before a Support Case is created it's best to do a little field prep first.  You'll want to populate the new custom field with the values your Leads already have from the original field.  This is allow the system to queue up and sync the values to Salesforce.  If a field merge or remap is done without the values being prepped it can results in values in Marketo not being pushed up for records.

For the difference between a field merge and remapping, it's really personal preference but I definitely prefer field merge.  This is a cleaner approach as the two fields will be combined resulting in a single field with the Salesforce mapping.  If a remapping is performed you'll still be left with two fields, just the mapping has been moved so then the discarded field will remain and need to be hidden or re-purposed.  Field merges can only be performed on two custom fields.  If one of the fields in question is a Marketo Standard Field then a remapping will have to be performed.  I hope this helps to shed some light on the situation!