HS/SF Integration - Routing some contacts directly to SF Contacts?
SOLVE
1 Accepted solution
HS/SF Integration - Routing some contacts directly to SF Contacts?
SOLVE
You're not going to be able to do this with the native integration, as you can't create rules about which object HubSpot syncs to - you can only set that in the one place.
I think the solution is to build a process, potentially automated, on the salesforce side.
Assuming you've got all contacts associated with the named account syncing to Salesforce as leads, and you've got a flag on the contact that indicates they belong to a named account, you may be able to use Process Builder in Salesforce to automatically convert those leads into contacts. Not sure if that would also be able to associate them with accounts, but I think that might sync up with HubSpot later anyway...
Hope this help.
@SebastianWyatt wrote:
Hi ,
Have a question about the best way to achieve an exception to the general way in which our SF/HS integration is set up.
We push HS Contacts in SF Leads as MQLs and then once further qualified by the Sales team these are converted into Contacts and Opportunities, so typically data only gets added to SF if they engage with marketing first and then gets added as a Lead. This process works well.
However we also have Sales teams that focus on prospecting for key accounts in Salesforce (called Named Accounts). As the Sales teams work only in Salesforce I would like to push all contact data that we have for Named Accounts directly into SF Contacts (bypassing Leads) so they have visibility of our entire position in that Account.
I have fields that flag which Accounts are Named Accounts but am struggling to find a way to build an exception to the integration setup. One thought I've had is that if the Named Account field is checked that this contirbutes to the Lead Score. This would still put them in SF Leads, but the Sales rep owner could convert them into a Contact themselves if they hold a position which is relevant.
If anybody in the community has thought about this before, or even implemented a solution. I'd love to hear about it!
HS/SF Integration - Routing some contacts directly to SF Contacts?
SOLVE
You're not going to be able to do this with the native integration, as you can't create rules about which object HubSpot syncs to - you can only set that in the one place.
I think the solution is to build a process, potentially automated, on the salesforce side.
Assuming you've got all contacts associated with the named account syncing to Salesforce as leads, and you've got a flag on the contact that indicates they belong to a named account, you may be able to use Process Builder in Salesforce to automatically convert those leads into contacts. Not sure if that would also be able to associate them with accounts, but I think that might sync up with HubSpot later anyway...
Hope this help.
@SebastianWyatt wrote:
Hi ,
Have a question about the best way to achieve an exception to the general way in which our SF/HS integration is set up.
We push HS Contacts in SF Leads as MQLs and then once further qualified by the Sales team these are converted into Contacts and Opportunities, so typically data only gets added to SF if they engage with marketing first and then gets added as a Lead. This process works well.
However we also have Sales teams that focus on prospecting for key accounts in Salesforce (called Named Accounts). As the Sales teams work only in Salesforce I would like to push all contact data that we have for Named Accounts directly into SF Contacts (bypassing Leads) so they have visibility of our entire position in that Account.
I have fields that flag which Accounts are Named Accounts but am struggling to find a way to build an exception to the integration setup. One thought I've had is that if the Named Account field is checked that this contirbutes to the Lead Score. This would still put them in SF Leads, but the Sales rep owner could convert them into a Contact themselves if they hold a position which is relevant.
If anybody in the community has thought about this before, or even implemented a solution. I'd love to hear about it!
