I'm using the standard SalesForce integration to sync with HubSpot. Most of the install went very smoothly, but in SalesForce I have no annualrevenue field for Contacts (we're B2B so even an individual user would be better served by creating a stub company record for them). Of course, creating this field counts as a custom field and yields annualrevenue__c which HubSpot does not recognize and, since this is a standard mapping, I can't edit it to point to a new field.
Does anyone have any workarounds for this? It looks like it assumes that "Person Accounts" are enabled on the SalesForce side, but that could lead to a lot of broken reports and bifurcation of data on our SalesForce side.
Sadly, I can't enable the contact sync until this problem is cleared and setting the field to never sync doesn't seem to work. Has anyone found a workaround for this? The field under contacts is useless for us (we'd only use the Company annual revenue) so any of the following would work:
Some hidden trick to remove it from the list entirely or force enablement of contact sync despite the error.
Some way to remap it to annualrevenue__c (or anything else).
Some minimally invasive configuration in SalesForce that would create the field.
I see When setting-up the custom property at Salesforce (contacts) is not recognized by the HS native Anuall Revenue Fiedl (Contact) - sounds like a pain in the neck
Here's the some stuff I would try:
Try the "Don't Sync" Option AGAIN and Ask HubSpot tech support on why it won't work
HS <> SFDC integration is Built and maintained by HubSpot product team so they should be able to support
Try running a test sync (in test environments) with the similar config and see what's the output
I see When setting-up the custom property at Salesforce (contacts) is not recognized by the HS native Anuall Revenue Fiedl (Contact) - sounds like a pain in the neck
Here's the some stuff I would try:
Try the "Don't Sync" Option AGAIN and Ask HubSpot tech support on why it won't work
HS <> SFDC integration is Built and maintained by HubSpot product team so they should be able to support
Try running a test sync (in test environments) with the similar config and see what's the output