Ensuring that HubSpot and Salesforce are connected and synced to share data between them is absolutely critical for maintaining a single customer view, avoiding confusing situations, and improving your marketing campaigns and personalization automation.
Unfortunately, due to differences in the two systems, many companies often find that the integration between them leads to some unintended consequences. They can’t always move, merge, reconcile, or alter data in the way that they would have liked. Certain data issues can also cause the sync between the two platforms to break, causing further data-related issues. Usually, companies don’t realize how cumbersome these issues can be until the integration is already in place. Then they are left scrambling for a solution.
Fortunately, Insycle is designed to solve some of the most common problems that come from HubSpot + Salesforce integration. In this article, we’ll cover some of the most common issues that companies run into with the integration and provide a quick overview of how Insycle can help you to remedy them.
Stop Bad Data from Breaking the HubSpot/Salesforce Sync
Avoid Bad Picklist Values When Importing Data in HubSpot
Merge Duplicate Companies After teacher database Connecting HubSpot and Salesforce
Stop Existing Salesforce Duplicate Leads from Syncing to Hubspot
Reconcile HubSpot and Salesforce Records to Find When Sync is Broken
Clean Data in Both Platforms At Once
Manage Complex Company Parent-Child in HubSpot to match Salesforce Accounts Hierarchies
A Simple Solution to a Complex Problem
Stop Bad Data from Breaking the HubSpot/Salesforce Sync
One of the biggest issues that companies have when they sync their HubSpot and Salesforce accounts is bad data breaking the sync. A common reason for this comes from the “State/Region” and “Country” properties.
In HubSpot, these properties should be converted from single-line text into dropdown select and contain standard values that will pass validation for Salesforce, in order to keep the sync from breaking. Both the “State/Region” and “Country” properties in HubSpot must be completely standardized, or else the sync will break. A common issue with the type conversion is dealing with historical values. After converting the field type to a dropdown, new values will get mapped properly, but any existing historical values will remain in the contact or company property, and if any of these values is not standard in Salesforce the contact or company records will not sync.
The sync between HubSpot and Salesforce breaking is no small deal, either. All sorts of problems can arise from the sync breaking including workflow rules, validations, assignments, and lead scoring. In short, a broken integration can lead to further data issues that must be resolved before the sync is truly back in place and operational. This leads to a lot of wasted time and resources dealing with these issues.
You can remedy this problem with Insycle, using the “Fields Cleanse” feature. With that, you can explore the existing values in HubSpot and identify inconsistencies. Then, you can migrate legacy values and standardize those inconsistencies with just a few clicks. Insycle can help you to ensure that unplanned sync breaks don’t happen due to bad data and ensure that “State/Region” and “Country” properties remain consistent.
