If you're doing this as part of the recreation of the fields for the changes to the SFDC Sync configuration change, the recreation of the fields will kick off a backfill process to pull existing data from the Marketo fields over into the newly created SFDC fields.

Even if you aren't creating the fields for that purpose (like for a brand new setup instead), it will still pull over all of the existing values from Marketo into these SFDC fields automatically. Since these are brand new fields in SFDC, no lead/contact records will have any values in them, so a quick report looking for any records that do have a value will show you the records that have been updated so far (assuming you have some leads in Marketo that have a value there to be pulled over). Give it a little time to get some fields updated - it pushes data at roughly 10k records per hour, but it shouldn't take long to at least get some records updated.

Thanks,

Mike

Once this is configured, how do we see / know it's working properly?

Just keep checking to see if the new fields are populated?

Thanks, that's what I figured, but wanted to be sure.

(It could be made more explicit in the instructions. :^)

Hi @David Howard​,

The goal here is to get these new custom fields to match up to the existing Marketo fields. Those API names are what the sync cycle is looking for in order to know to map the fields together, so the specific API name in the doc does need to be entered as it is there in order for that mapping to take place.

Marketo actually does the same thing when creating a new field - it enters a default value just so that there's something in place for the API name in the right formatting it needs for use with APIs, but it can be edited as needed while being created. So, best thing to do is to enter the API name into SFDC as it's listed here (including that prefix) so that all the fields match up the way they should.

Hope that helps!

-Mike

Is the prefix "mkto71_"  as shown in the example required?

By default, Salesforce creates it's own API name, which doesn't have this prefix.

The Contact fields would be created with the same process as the Lead fields, but just on the Contact object instead. It's not required to create the fields on both Lead and Contact, but it is highly recommended.

Where are the contact fields required?

Yes, as soon as the new custom fields are created, that kicks off a backfill process that will automatically update all leads and contacts in the database. It starts on the next sync cycle automatically as soon as the fields are recreated.

An important thing to note here is that creating the new custom fields is what starts the backfill process, so please be sure to only do that during the Group's window when scheduled. Since the backfill process also initiates a global resync of leads with SFDC, we want to avoid any traffic jams of data passing through in order to minimize the impact on other customers (and also to keep your resync moving quickly).

Thanks,

Mike

Hi Mike,

If we delete the existing fields, will the custom fields be populated for all leads/contacts that we currently have in our system? For example if John Doe is a lead in our system and I delete the old Lead Score field and create this custom Lead Score field, will the information from the old Lead Score somehow we moved to the new Lead Score field? Thanks.

Hi @Daniel Jue​

You can delete them, or you can leave them there. It's up to you. They'll be obsolete, so many customers will want to remove them to clean up their SFDC instance. The fields can be removed by uninstalling the MLM package from SFDC, but keep in mind that if you have any workflows or reports or anything else that reference these fields, you'll have to remove those references to the fields before SFDC will let you uninstall it. All of the fields and connections in SFDC that were made by the MLM package will be removed by uninstalling it, but custom ones you've created will need to be manually removed.

Hope that answers your question!

Thanks,

Mike