Please open up the sync functionality with Dynamics 365 so that Contacts from Hubspot with a Lifecycle Stage of "Marketing Qualified Lead" can sync to Leads in Dynamics.
We qualify to MQL within HubSpot and then handoff those contacts to Sales (in Dynamics). I'm not sure why you'd handoff a Subscriber or Lead before qualifying?
We are stuck without a solution for this until the functionality is updated, as most third party services have shut down their solutions due to the growth of Operations Hub.
The feature is called "Improved lifecycle stage filtering in lead and contact syncs" and it's actually tied to another feature that went into beta, namely the general ability to customize lifecycle stages generally .
@Nina_R The idea is to allow you to sync over any lifecycle stage as either leads or contacts (but your selection will be mutually exclusive, i.e. when you say SQLs are leads, you can't also sync them over as contacts, as doing so would severely pollute your database).
Thanks for the clarification. So instead of promoting all the way to MQL, is it not possible to keep it inside of Lead? While it is in lead, you'd instead granularly work off of a different property (like lead status) to distinguish the 'new' from the 'ready to sync' leads? I totally acknowledge that if MQL is very incrusted in all kinds of workflows already, this is not really an easy nor acceptable workaround!
We needed to draw an arbitrary line in which lifecycle stages sync as leads and contacts to force two distinct sync 'buckets'
The current logic is that a 'Lead' or 'Subscriber' are the only two lifecycle stages that should sync to Dynamics as leads - and you'd subsequently qualify them inside of Dynamics (converting them to contacts).
For the contacts sync, we'd imagine you'd want to at least select 'Opportunity' or 'Customer' as stages, in order for HubSpot to trigger directly creating a contact inside of Dynamics should it not yet exist.
That still leaves MQL & SQL, where the generalized assumption was that if you're doing qualification inside of HubSpot, and you'd hence consider someone Marketing qualified or Sales qualified - they are de facto qualified. They would no longer need to be qualified inside of Dynamics. We definitely are now realizing that not everyone follows this logic and that you would like to 'requalify' leads in Dynamics - still as leads.
We're planning to give more control over what lifecycle stages can sync as leads. Since this feature is dependent from a couple of other core segmentation functionality inside HubSpot, it still takes some time to rollout.
Is it not possible to, in the meantime, keep whatever you like to sync to Dynamics in the stage of "Lead"? There's still control through the filter by setting up an inclusion list.
We needed to draw an arbitrary line in which lifecycle stages sync as leads and contacts to force two distinct sync 'buckets'
The current logic is that a 'Lead' or 'Subscriber' are the only two lifecycle stages that should sync to Dynamics as leads - and you'd subsequently qualify them inside of Dynamics (converting them to contacts).
For the contacts sync, we'd imagine you'd want to at least select 'Opportunity' or 'Customer' as stages, in order for HubSpot to trigger directly creating a contact inside of Dynamics should it not yet exist.
That still leaves MQL & SQL, where the generalized assumption was that if you're doing qualification inside of HubSpot, and you'd hence consider someone Marketing qualified or Sales qualified - they are de facto qualified. They would no longer need to be qualified inside of Dynamics. We definitely are now realizing that not everyone follows this logic and that you would like to 'requalify' leads in Dynamics - still as leads.
We're planning to give more control over what lifecycle stages can sync as leads. Since this feature is dependent from a couple of other core segmentation functionality inside HubSpot, it still takes some time to rollout.
Is it not possible to, in the meantime, keep whatever you like to sync to Dynamics in the stage of "Lead"? There's still control through the filter by setting up an inclusion list.
Thank you for your response. We pre-qualify to MQL in HubSpot, and hand off to sales to further qualify. This is why we need MQL to be the lifecycle stage that gets handed off. We do not hand off leads, as they are not yet warm enough for our sales team to reach out to.
Ultimately, we're really frustrated in finding some way to connect between these two systems. No one seems to be able to help us. We need both systems - and we need them to talk back and forth to each other.
Thanks for the clarification. So instead of promoting all the way to MQL, is it not possible to keep it inside of Lead? While it is in lead, you'd instead granularly work off of a different property (like lead status) to distinguish the 'new' from the 'ready to sync' leads? I totally acknowledge that if MQL is very incrusted in all kinds of workflows already, this is not really an easy nor acceptable workaround!
Also, we have certain reporting in place that would be very hard to translate - we use MQL to report a lot on marketing initiatives and KPIs, and this would create a huge organizational shift that we don't want to have to undertake.
Thanks for the update, even if it isn't what I expected to hear. To make another clarification: In some customer companies you can't change the whole lead process to adapt the way HubSpot works, but it is expected that the software adapts to the needs.
The MQL is the marketing qualified lead that gets handed over to sales (and Dynamics) where they qualify them under sales needs. That will be the SQL.
@steviecald maybe I have a workaround for you. We have a workflow in place that dequalify a MQL to Lead, than this contact is synchronized to Dynamics and after 10 minutes that contact gets the MQL status again.
Hi, it's great to read that this feature in progress! Our business need is slightly different: we need SQLs to sync to Dynamics 365 Leads. It's not entirely clear to me from this threat wether or not this will also be included in the update. @FransLeys Can you shed some light on this please?
@Nina_R The idea is to allow you to sync over any lifecycle stage as either leads or contacts (but your selection will be mutually exclusive, i.e. when you say SQLs are leads, you can't also sync them over as contacts, as doing so would severely pollute your database).
When is this update rolling out? @steviecald is on point.
We are contracted to bring MQLs to our client's sales team. The client is using MS Dynamics 360. We had the client purchase Marketing Professional and add Operations Hub specifically to handle this.
Prospects are nurtured in HubSpot with Workflows and Scoring. Once the threshold is reached the Lead (In Progress) becomes an MQL and is added to a List "HubSpot to MS Dynamics". The MQL is then sent to MS Dynamics 360 as a Lead with Status "New", Lead Source "MQL from HubSpot".
When the client's sales team qualifies the MQL as an SQL, Dynamics creates the Opportunity and we simply want that conversion information synced back to HubSpot thus updating the MQL in HubSpot to an SQL.
Has anyone come up with a workaround @Carsten ? We specked this work with Pie Sync 1 Year ago and we are not any closer, today!
The feature is called "Improved lifecycle stage filtering in lead and contact syncs" and it's actually tied to another feature that went into beta, namely the general ability to customize lifecycle stages generally .
