HubSpot
Two-way sync between HubSpot and your other systems.
Supported Objects
Stacksync lets you sync the following HubSpot objects:
| Object | Status |
|---|---|
| Contact | ✅ Supported |
| Company | ✅ Supported |
| Deal | ✅ Supported |
| Line Item | ✅ Supported |
| Product | ✅ Supported |
| Ticket | ✅ Supported |
| Quote | ✅ Supported |
| Goal | ✅ Supported |
| Owner | ✅ Supported |
| Pipeline | ✅ Supported |
| Stages | ✅ Supported |
| Audit | ✅ Supported |
| Subscriptions | ✅ Supported |
| HubDB | ✅ Supported |
| Forms | ✅ Supported |
| Calls | ✅ Supported |
| Communications | ✅ Supported |
| Emails | ✅ Supported |
| Meetings | ✅ Supported |
| Notes | ✅ Supported |
| Post Mail | ✅ Supported |
| Tasks | ✅ Supported |
| Marketing Emails | ✅ Supported |
| Invoices | ✅ Supported |
| Attachments | ✅ Supported |
| Custom objects (all) | ✅ Supported |
| Associations | ✅ Supported |
| Users | ✅ Supported |
| Services | ✅ Supported |
| Listings | ✅ Supported |
| Courses | ✅ Supported |
| Appointments | ✅ Supported |
| Commerce Payments | ✅ Supported |
| Email Events | ✅ Supported |
| Property History | ✅ Supported |
| Campaigns | 🕘 Coming soon |
| Feedback Submissions | ❌ Not supported |
Need to sync other objects? Email us at hello@stacksync.com and we can add support for them in no time!
All Associations between synced objects are supported. You can choose which associations to sync during the sync setup or sync update.
Things to keep in mind
HubSpot Account Type
The type of HubSpot Account can have restrictions on the supported objects.
- The free version of HubSpot Account does not support the Audit object.
- Custom Objects are only supported in the HubSpot Enterprise version.
Custom Fields
HubSpot allows the creation of custom fields with duplicate field names that can conflict with HubSpot system fields, such as the id field for example.
In cases where an object includes a custom field named id, it may conflict with HubSpot’s native record ID, which is also named id. HubSpot permits the creation of custom fields with duplicate names in any object due to its underlying data storage model, which does not enforce uniqueness of field names and lacks a logic layer to prevent such conflicts. To avoid ambiguity during data sync, any custom fields named id that conflict with native HubSpot fields will be ignored and excluded from synchronization.
Backup and Restore Capabilities
With two-way sync, we recommend using a professional backup/restore for your HubSpot CRM.
HubSpot does not have a native backup and restore functionality. Two-way syncing is powerful. A mistake in a connected App could have consequences on your HubSpot data as well. If you sync to another system that has backup capabilities built-in such as a modern database (e.g. Postgres), it could be used to back up data in HubSpot as well but we still recommend using a robust backup and restore service such as:
Q&A
Syncing columns with custom data constraints
HubSpot allows columns to have certain data constraints that may cause issues when the incorrect format of data is synced.
For example, the single-line text field can have constraints for allowing only numeric values, not allowing any special characters, and having a maximum or minimum character limit.
If you face an error regarding this, either modify the restrictions on the HubSpot column to allow the data to sync or modify the data to fit the format of the HubSpot column.