We are running into an issue with the lifecycle stage syncing between salesforce and hubspot on Contacts. This is what's happening:
A new contact record is created in HS when someone fills out a "demo request" form
their lifecycle stage is set to "Marketing Qualified Lead" through our MQL workflow
due to our bi-directional sync, the record is then created in salesforce and the "lifecycle stage" field on the salesforce record is correctly updated to "Marketing Qualified Lead"
At the exact same time, the sync from Salesforce back to Hubspot is resetting the lifecycle stage to blank (which is causing this contact to be removed from our salesforce inclusion list)
I can't figure out why the sync would succeed in updating the SF lifecycle field, but would simultaneously clear that same field on the hubspot record. Has anyone experienced this? Any recommendations for fixing it??
**Edited to add: We just changed out salesforce setup to only use Contacts, and that is when this issue began. We used to use Leads and didn't have this issue, but we have since converted all of our leads to contacts.
Thanks for reaching out to help! I was able to figure it out - the API names in salesforce for marketing qualified lead and sales qualified lead had underscores where the spaces are (salesforce's default) instead of listing it as all one word (i.e. "marketingqualifiedlead" which is hubspot's way) so it wasn't recognizing the correct picklist option because the API names didn't match up. Appreciate you trying to help!
I would like to tag in some of our experts in on this @Drew_Cohen, @lynton and @Aakar. Can you please provide some advice to @TBrodie on the roadblock with Salesforce they are experiencing.
Thanks for reaching out to help! I was able to figure it out - the API names in salesforce for marketing qualified lead and sales qualified lead had underscores where the spaces are (salesforce's default) instead of listing it as all one word (i.e. "marketingqualifiedlead" which is hubspot's way) so it wasn't recognizing the correct picklist option because the API names didn't match up. Appreciate you trying to help!
Hello, we have been facing this same issue and fixed the picklist API values to match Hubspot but we have the exact same error still. Did you do anything else to solve this problem?
Do you use both Leads and Contacts in Salesforce? That was part of our problem as well - the picklist options were correct on the lead object but weren't on the contact object. Since hubspot doesn't differentiate between the two, it was defaulting to the wrong object (we wanted it to set the lifecycle stage on the contact object) so I just had to double check that and make sure everything matched.
You could try a test (this is how I found our issue): Update the lifecycle stage in hubspot for one of your records that isn't working, resync it to salesforce and then check the backend of that object in salesforce - see if it created an inactive picklist value on the lifecycle stage for that object. If it did - then you need to activate that picklist value. You can change the field label and merge it with your previous one that wasn't working, but you should keep the api name since you know that's the one that is working.
Hello! This is the solution indeed! It works now for us after creating the options again. We use a global picklist in salesforce so that might be the reason why it didn't work immediately by just renaming the API of these options.
Hi, thanks a lot for your answer. No new option gets created when we sync the record. The field we have is a global picklist used on accounts, contacts, and leads. We have opened a ticket with Salesforce and Hubspot. I will post here once we get it solved.
.png "HubSpot Employee"){kind=icon}
