1 of 1 people found this helpful
It's important to remember that MSI and MLM are two separate packages. It's very easy to get them mixed up.
- MSI stands for Marketo Sales Insight. Sales teams tend to use it a lot.
- MLM stands for Marketo Lead Management. It really doesn't do anything for anyone.
The MSI package creates a set of fields that MSI uses like Interesting Moments. Those fields get installed when MSI is installed and they will still keep getting installed moving forward with new MSI installations. Those fields remain unchanged. The MSI package can stay right where it is. It doesn't need to be uninstalled or anything--the patch we sent out automatically updated it so that it keeps on working just like it should.
The MLM package, however, created the 16 fields inside of SFDC, like Lead Score, and those are the ones that are affected here. Now, the MSI package used to reference the MLM package in a very minor way, but the patch we sent out removed that dependency so again, MSI is good to go as is, but the MLM package is where the fun is here.
So the MLM package created these fields and the configuration change is going to cut off data syncing into those fields. The question is, do you need that information inside of SFDC? If you do, recreate the fields, but if you don't, then don't worry about recreating them and save yourself the trouble. Lead Score is still visible within the view of MSI in Salesforce, so the data is still there, accessible to your sales teams. It's the other fields that tend to be the question. Do your sales teams ever need to know what the Acquisition Program was? (That's the only other field that is commonly used, though the rest sometimes get some attention) If your sales teams don't need the data from those other fields, save yourself the trouble. If they do need it, then yes, go ahead and recreate the fields.
I hope that helps. If you have any other follow up questions at all, please don't hesitate to ask! Happy to help.
I followed the instructions above to a T (created new custom fields, did mapping, then uninstalled the MLM package) and now my lead score, flames and stars are all blank. I sincerely hope I haven't lost data. Can you please help me troubleshoot?
Actually, there are like 20 records with a score, but it's 8. I had hundreds of leads scored with scores from -10 to 80. This is a disaster.
Group 2 here. So I've read through all the documentation and am comfortable with the upcoming changes. However the only thing I can't seem to find anywhere is what the actual API names need to be on the new fields we create. I plan to recreate probably 14 or the 16 fields, so I just need to know what the naming convention should be for them, thanks!
I did not see that we had to wait until our window to create the new fields so i created 3 of them already. I have questions/concerns:
1. Will the sync use our salesforce API calls? I am worried we will max out on API calls due to the sync. It needs to sync real slow if this is the case.
2. I already have the "Lead Score" field in salesforce of course. When I go to map the lead field to the contact field it gives me 2 fields with the exact names name to map to "Lead Score". It is the same problem with Acquisition fields. Is there a trick to determine the correct one to choose?
When wanting to choose the new fields, I found I needed to choose the second of the 2 duplicates in the picklist.
If you've already created any of the fields, then your instance is already going through the backfill process and resulting resync now. Best to avoid that in general so we can stick to the schedule, but it's not any kind of critical problem. Just be aware that it's already running for those three fields. Probably ought to wait for the scheduled time to recreate the other fields though. You can do them now if you need to--the trade off here is that any leads who have already done the backfill and then the resulting resync from SFDC back to Marketo will have to go through that same process again. Not the end of the world, but since it's outside of the schedule, it could put a small drain on the others in the current schedule. We planned ahead with a buffer for these type of scenarios though.
You're not the first person we've heard from that had that same confusion about how the field creation is what actually starts the backfill process. I don't think that point was clear enough in our documentation, so I just went back through and added some notes about that in multiple locations. Sorry for the confusion on that part.
In terms of the backfill process, this data passes through a separate "pipeline" outside of the normal SFDC sync, so it won't conflict with your regular sync and it also won't use up your SFDC API calls.
With the field names, one trick I heard another customer try was changing the friendly name / friendly label for the older existing fields to something a little different so that it's easily identifiable as the one you don't want to choose. Try that and let me know if that helps.
10 of 10 people found this helpful
I've run through the process with one instance so far. Overall, the process worked great. I wanted to provide some feedback/suggestions for others from my experience.
- Disable the sync to SFDC in Marketo before you start to create the new fields in SFDC. Once all the new fields are created, then re-enable the sync in Marketo.
- Take the opportunity to really think about whether you need all those fields syncing. If they aren't being used in SFDC then you probably should not recreate them. You can always sync additional fields at a later time.
- Once the new fields exist in SFDC, create an SFDC Lead report and a separate SFDC Contact report that you can use to compare the old and new fields. This will allow you to make sure that the backfill completed properly. As an example, I used the following filter in the Lead report so only those that don't match are shown. Make sure to change for the fields you created.
The SFDC reports allowed me to see that I had an issue where most but not all of the fields were properly backfilled in Leads. I am fairly certain that it had to do with timing on creation of the new fields across multiple standard sync cycles. Hence, my recommendation to disable the sync while you are creating the fields. The good news is that a simple sync of the leads where the backfill wasn't fully completed and everything was fine.
- Don't forget to update any places in SFDC that refer to the old fields with the news ones. Obvious is page layouts and reports. But don't forget formula fields and workflows too!
Hope others find this useful.
Hi Mike Reynolds,
We have a customer which accoutn stream starts with a "t". Apparently, the lead score does not sync any longer (I have done quite some testing both ways. The lead sync works perfectly well for all fields, but the lead score). And yet, per the release schedule, they belong to group 6. Is this normal? Should we anticipate the change to the fields?
Thx for your help.
The sync of data to the fields will keep going until January 31st, 2017. That's the cut off date when the sync stops. Whether you recreate the fields or not, data still passes to the old fields until that date--no change has been made there yet. So, if you're seeing problems with values syncing, it's got to be caused by something else. My first suspicion is permissions on the SFDC side, but if you're not seeing the trouble, you probably ought to Contact Marketo Support so we can dig in deeper.
the weird thing is that only the lead score field seems to have a problem.