Microsoft Dynamics sync -> leads and contacts separation
SOLVE
The database model regarding contacts is different between HubSpot and Dynamics. HubSpot only knows contacts where Dynamics differentiates between leads and contacts. To do a proper syncronization between the two system, HubSpots relies in the lifecycle property. Everything that is kead or less syncs to a Dynamics lead, everything MQL and above as a contact. So far so good, BUT...
Marketing works on leads and whenever they are marketing qualified the leads should be handed over to sales (Dynamics). Sales needs to qualify them (SQL) and works on them till they become a customer. That's the moment the Dynamics leads get added to an account and are transformed into a Dynamics contact. Pretty straight forward - isn't it.
But problem is, that Operations Hub isn't able to sync a MQL as a lead - only as a contact.
IDEA: make it possible to decide directly in the portal which lifecycle stages should be syncronized as leads or contacts. One additionaly variable in the settings of the app should be enough.
Microsoft Dynamics sync -> leads and contacts separation
SOLVE
Hey Carsten,
It's not only a good idea - it's actually something that's in the works right now.
The logic we followed in the current iteration is that one where a 'MQL' indicates that the lead has been qualified, to such an extent that it can sync over to Dynamics - and it no longer needs to be qualified in Dynamics, hence, it can directly become a contact.
We definitely acknowledge this doesn't cover all the nuances. While it helped most implementations, it doesn't cover all of them. Future: Making it possible for you in the sync setup to classify which leads make it over is going to give you that flexibility. We expect to release that this year still.
Microsoft Dynamics sync -> leads and contacts separation
SOLVE
Great to hear @FransLeys that you are already working on that issue and that we expect a solution soon. Keep on with the good work in evolving the operations hub.
Microsoft Dynamics sync -> leads and contacts separation
SOLVE
@FransLeys I completly agree with @Carsten , we are currently facing the same problem. Would be really good to have it solved quickly to not mess up the data in the systems.
Microsoft Dynamics sync -> leads and contacts separation
SOLVE
Hey Carsten,
It's not only a good idea - it's actually something that's in the works right now.
The logic we followed in the current iteration is that one where a 'MQL' indicates that the lead has been qualified, to such an extent that it can sync over to Dynamics - and it no longer needs to be qualified in Dynamics, hence, it can directly become a contact.
We definitely acknowledge this doesn't cover all the nuances. While it helped most implementations, it doesn't cover all of them. Future: Making it possible for you in the sync setup to classify which leads make it over is going to give you that flexibility. We expect to release that this year still.
