Why does the HubSpot sync error "Entity is synced already" occur?

Related Scenarios

• What causes the "Entity is synced already, but no match found in third party" error during HubSpot and Chargebee sync?
• How to resolve sync issues when entities are deleted or merged in HubSpot?

Solution

This error typically occurs when an entity, such as a company, was deleted or merged in HubSpot after the initial sync, causing subsequent sync attempts to fail. To resolve this issue, follow these steps:

1. Rerun the Sync: Attempt to rerun the sync process from Chargebee to HubSpot.

   • Navigate to Apps > HubSpot in Chargebee.
   • Click on Sync Now to initiate the sync process again.

2. Check Entity Status in HubSpot: Verify if the entity (e.g., company) exists in HubSpot.

   • If the entity was deleted or merged, recreate or update the entity as needed.

3. Field Mapping in Chargebee: Ensure that the mapping from Chargebee is correctly set.

   • Go to Apps > Select Manage within Hubspot > View sync log.
   • Check if the fields are correctly mapped according to your sync rules.
   • Update any mappings that may have changed due to entity modifications in HubSpot.

4. Verify HubSpot Fields: Ensure that all necessary fields in HubSpot are correctly configured.

   • Check for any discrepancies in field names or types that might affect the sync.

5. Contact Support if Issue Persists: If the error continues after following these steps, contact Chargebee support for further assistance.

Important Notes

• Ensure that any changes in HubSpot entities are reflected in Chargebee mappings.
• Regularly review and update field mappings to prevent sync issues.
• Consider setting up alerts for changes in HubSpot that might affect sync processes.