Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Changing Sync Direction: It is recommended that the sync direction for Accounts, Contacts and Leads is not changed after it has been set. This can, in some cases, result in duplicates being created in either system.

Changing Sync Hubspot Contacts to Sugar: It is recommended this selection is not changed after it has been set. This can, in some cases, result in duplicates being created in either system.

...

Info

License Info Email Alert: If the Hubspot bridge detects any issue with the license key info an email will be sent to the Hubspot Bridge user alerting them.

At the bottom of the Integrations screen you’ll find the Connection Status buttons. These allow you to check the status of the connection with SugarCRM and Hubspot.

...

Once you are done configuring the settings in the Integrations area remember to click SAVE to apply the changes.

...

IMPORTANT: Saving the integration settings with the connections and synchronization settings enables will start the sync between the two systems immediately.

...

Once you are ready to set up your custom mapping click on the + icon to create a custom mapping

...

Note

One of the most common reasons for errors are due to new dropdown/picklist values being added in one system and then not added to the corresponding dropdown in the other.

Logs

...

Info

Mismatched Values Email Alert: Once a day the Hubspot bridge will check Sugar and Hubspot values in mapped dropdown fields comparing them to make sure they match. If a mismatch is identified an email alert will be sent to the Hubspot Bridge user alerting them so that they may take action.

Logs

While the Dashboard will keep you informed of sync activity at a high level the Logs area allows you to drill down to further to inspect activity of each individual sync run and the individual records the Hubspot bridge attempted to sync.

There are three areas to explore within the Hubspot Bridge logs, we’ll cover each of those below so you can understand the information they serve up and how that information might help you identify and troubleshoot any issues.

...

Sync cycles are shown in chronological order with breakdowns for how many records were synced in either direction and the sync status. Let's take a look at each section of the sync run info:

...

Image: Shows recent sync runs for a one way sync from Hubspot to SugarCRM

  • Job started at: Displays the date and time the sync cycle began

  • Steps progress: Shows the steps that the sync cycle needs to process in order to complete each sync cycle. The Steps listed here may vary depending on your integrations configuration. Completed processes are indicated with a check mark symbol.

  • Records statistics: The looking glass icon next to each entry allows you to drill into the specific Sync Log entries for the events processed in that section of the sync run. For example, if you see that 120 accounts were synced from Hubspot → Bridge → SugarCRM then you can drill in to see the individual sync logs for each of the 120 company records that were processed.

  • Importing to bridge: Shows the number of records that were imported into the Hubspot bridge to be processed.

  • Exporting from bridge: Shows the number of records the Hubspot bridge successfully exported (created or updated) in the target instance (Hubspot or Sugar)

  • Status: Displays the status of the sync run. this will indicate if it Finished, Completed with errors or is in the process of Running. An info tooltip icon may provide additional info as necessary.

...

A. The Sugar-Hubspot integration only supports the synchronisation of Accounts, Leads, Contacts and Target lists. Synchronising other records may be possible with customisation of the Hubspot bridge, please contact your Faye Account executive or sales@fayebsg.com if you are interested in a estimate for custom work.

Q. I’m seeing “Parent account not found” errors when syncing Contacts, what does that mean?

A. When syncing a new Contact from Sugar to Hubspot information including the Contacts related Account name is passed. If you get this error it is likely because the contacts related account does not exist in Hubspot for some reason, i.e.

  • The corresponding Company record may have been deleted in Hubspot

  • The Contacts Account may have attempted to sync to Hubspot but failed to create there due to some error.

Example scenario: Elon Musk of Tesla

  • Tesla account was marked to sync but failed to create in HS because of a field mapping error.

  • Elon Musk was also marked to sync so it tried to sync him after the account, when it did no company record was found for Tesla and a “Parent not found” error returned.

Q. An account is not syncing because of a “domain: "parkerindustries.net[unset]" is an invalid domain” error

A. When synchronising Sugar Account records to Hubspot the website value is passed to the Companies “domain” field. Unlike the website field in Sugar that will accept almost any text string the domain field in Hubspot expects well formatted values. In this case a “domain is invalid” error is returned because the website value being passed includes some invalid formatting on the end “parkerindustries.net[unset]".

In this example if the Sugar records website value is corrected to parkerindustries.net then it should synchronize fine the next time it tries.

Q. What happens if I delete a synced record in Hubspot?

A. The integration does not sync deletions of records so deleting a record in Hubspot will not cause the corresponding record in Sugar to be deleted however it may provoke some changes in previously paired Sugar record.

When a record is synced and paired between sugar and hubspot the Sugar record will have its “Sync to Hubspot” field checked and will also have a “hubspot ID” value for the paired record in Hubspot. If that hubspot record is deleted then the next time the Sugar record attempts to sync it will not be able to find the paired record, should this happen the Sugar records “Sync to hubspot” field will be automatically unchecked and the “Hubspot ID” value reset to null. Effectively this will prevent the record from attempting to sync again unless it is later checked to sync again.

Q. What happens if I delete a synced record in Sugar?

A. The integration does not sync deletions of records so deleting a record in SugarCRM will not cause the corresponding record in Hubspot to be deleted however it may provoke some changes in previously paired Hubspot record.

When a record is synced and paired between sugar and hubspot the Hubspot record’s “SugarCRM ID” property will contain the ID value of its paired Sugar record. If that sugar record is deleted then the next time the Hubspot record attempts to sync it will not be able to find the paired record. Should this happen the the Hubspot records “Sugar ID” value will be updated to the value of DELETED and will be ignored for future sync cycles so that the record is not recreated in Sugar.