Match Salesforce integration with email and custom property

[Egoi]

I am currently using HubSpot - Salesforce integration so that data can be shared between both platforms. The problem I have encountered is that in Salesforce the same email can be used for different contacts whereas HubSpot does not allow this.

In this situation, sharing data between HubSpot and Salesforce its a problem as I need to check with a second property (i.e. Salesforce contact ID) which contact has to be updated. Is this even possible with the native integration?

Thanks in advance!

[RBozeman · Accepted solution]

Definitely agree with @SteveHTM with his best practices recommendation. When you can have the same email on contacts and leads, its going to get messy with the sync turned on. 

Also wanted to mention that Insycle can help a lot with this. Full disclosure, I work for them. But Insycle helps with a lot of common HubSpot+Salesforce sync problems. 

Here's the bullet points:

• You can dedupe across HubSpot and Salesforce, without having to turn the sync off or anything, using the synced platforms IDs. 
• Any field in your database as a potential unique ID matching field. 
• Set rules for determining the master record that duplicates will all merge into. For example, if you have 3 duplicates in a duplicate group, you can set rules for determining the master record, such as the earlier created create, highest deal amount, or most recently updated.
• Further, you can set rules for retaining data down to the individual field level. So in your use case, you could instruct Insycle to append data to specific fields during the merge so that it is not lost.
• Fully automate your deduplication templates. You can run them on a set schedule or even inject them into Workflows so that deduping happens automatically after your contact (or any record type) is created.

[SteveHTM]

@RBozeman - I actually use Incycle on a few projects. I agree that it has some sophisticated features and functinality goes way beyond de-dup.

Steve

[SteveHTM]

@Egoi - it actually can be worse than you think because Salesforce allows Contact and Lead objects to have the same email address. When this happens the synce process can go into wild oscillations between the data held on on SFDC record and the other!

On a more optimistic note, the system disparities can be reduced or eliminated by:

- setting the sync process up to operate on a contact<>contact basis and eliminating the use of lead objects

- using effective de-duplication tools inside SFDC to detect and address possible duplicates. Ringlead is a good 3rd party option for example.

With the right approach in place, the sytems can operate smoothly together.

Hope this is helpful.

Steve