Page cover

HubSpot

Two-way sync between HubSpot and your other systems.

Supported Objects

Stacksync lets your 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

Campaigns

πŸ•˜ Coming soon

Events

πŸ•˜ Coming soon

Feedback Submissions

❌ Not supported

Need to sync other objects ? Email us at [email protected] and we can add support for them in no time!

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 object Audit.

  • Custom Objects are only supported in 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

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 backup data in HubSpot as well but we still recommend using a robust backup/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 constrains for allowing only numeric values, not allowing any special characters, 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.

Last updated