Hubspot & Salesforce Integration-Contact Limits

Hello we are working on a Salesforce & and Hubspot integration. Today, our recruiters and account managers use TargetRecruit built on Salesforce.

As we start looking into the HubSpot and Salesforce integration, we’ve found a bunch of technical resources that we can work with which is great, but we came across one issue and I thought someone might be able to offer some quick advice as we are still waiting to connect with our US HubSpot team next week.

We came across one issue with our Candidate pool (these are basically a group of applicants to our positions grouped by certain skills) – which in Salesforce is a very large account (although in the Hubspot realm of things, it’s really not an “account at all” .. the only reason it exists in Salesforce is because you HAVE to have an account to be a contact. The issue is that Hubspot doesn’t want to see more than 50,000 contacts associated to a single account – of which we are already above that limit.

I can’t imagine we’ve been the first customer they’ve seen to have this problem, so I’d like to ask if you have come up with any creative solutions or workarounds for this issue in the past?

Thank you, for any advice-it will be much appreciated!

Hi @RMolloy, I hope that you are well!
I love this question, thank you for asking the Community!
I understand that you’d like to associate more than 50 000 contacts to a single object (one company here). If that’s not the case, please let me know.
There is indeed, at the moment, a current limit of 50 000 contacts association for one same object.
You could use maybe a child company (which would be linked to the parent one) to associate the additional contacts? I know that this is not exactly what you are looking for but I hope this helps in a way.
I’d like to invite our top experts to this conversation: Hi @mangelet, @CateDuarte and @Mike_Eastwood do you know of any other workarounds to help @RMolloy associate more than 50 000 contacts to one same company, please?
Also, if anybody else has anything to add and/or share, please feel free to join in the conversation :slightly_smiling_face:
Thank you for your contributions :heart: and have a fabulous day!
Best,
Bérangère

Thank you for your input @BérangèreL! I’m workign with @RMolloy and if it helps at all - this really isn’t an “account” or a real “company” for us at all ( its more of a way of classifying ‘freelance’ contacts), so if there was a possible solution to “not attach” these types of contacts to that paticular account, that would probably be a suitable workaround as well. Problem is, we haven’t really found any way to insert logic into the salesforce connector process that might help us ‘make a decision’ like this.

We’ve seen the aforementioned idea of multiple ‘child accounts’, but that would probably drive a lot of change in our salesforce environment that we’re hoping to avoid.

Thanks again!

A lot of companies use this workaround to get past orphan Contacts (not associated with an Account) not being visible to anyone but the owner. They need an Account to be associated with Salesforce at large.

Ideas to work around this:

  • Don’t sync Accounts/Companies in the integration
  • Create multiple Accounts for Freelancers (US Freelancers, CA Freelancers, etc) and have a Flow in Salesforce reassociate them to Accounts based on their location