ZoomInfo Inbound Enrich Best Practices

[katherineladue]

I hope this isn't a dumb question... I'm setting up ZoomInfo Inbound Enrich for the first time for a client, and just wondering about some best practices.

I know in general it's advisable to create duplicate custom HS properties for ZoomInfo to overwrite so that teams in HS can tell the difference between the enriched data and the original data.

However, my client doesn't have a lot of faith in the quality of their existing data and will probably want to just go with the enriched version at least for this initial run. Is it common to set up the field mappings to overwrite at first and then change them to be "Complete if empty" for subsequent runs? Or would it be a better idea to go through the painful process of creating a million duplicate HS custom properties for ZI specifically, and then copy the data into the HS default properties?

I'm also confused about the Contact vs. Company field mappings. It looks like you can map ZoomInfo Company fields to HubSpot Contact fields as well as HubSpot Company fields... So for example, on the Contact mappings, there's a category in the list for Company Details where I can choose things like "Company Type", "Company Primary Industry" etc. but then I would have to map those to HS contact fields. Wouldn't I just want to map those under the Company mappings or is there a reason one would go with one over the other?? 

I've also reached out to ZI support but just wanted to see if anyone here had thoughts/opinions on this! And any other pitfalls or things to know about this integration!

[karstenkoehler · Accepted solution]

Hi @katherineladue,

If your client says that it's fine to overwrite existing information, assuming that the ZoomInfo data will be more accurate, then I would probably go with that decision. You can always export all contacts and companies before turning on the sync, as sort of a backup, in case something goes catastrophically wrong unexpectedly.

Creating duplicate properties might be a good idea for some of the fields that are critical to business processes (and not just informative) and used in central automation. If you for example have workflows for routing contacts based on industry, it might make sense to create a duplicate property first, check the information that is flowing in, create a report to compare your own and the ZoomInfo data before deciding to switch over entirely. I wouldn't do this for all properties but for those where new or wrong information could ripple through your portal.

Regarding the mapping: Use good judgement and map company attributes to the company object in HubSpot and contact attributes to contacts. I don't see a reason to do this differently and you can always create a sync property later should you really find that something needs to be displayed on a contact record, for example.

Hope this helps!

[katherineladue]

Thank you!! This is helpful. Quick follow up Q if I may: Our list of companies that we would be enriching definitely has duplicates in it and none of the records have company domains. Would it be a bad idea to even try to enrich that list knowing that there might be accuracy issues without the domains AND duplicate errors as well?