HubSpot (v4)
Last updated: 9/15/2026This integration is powered by Singer's HubSpot tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Support.
HubSpot integration summary
Stitch’s HubSpot integration replicates data using the HubSpot REST API. Refer to the Schema section for a list of objects available for replication.
HubSpot feature snapshot
A high-level look at Stitch's HubSpot (v4) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status |
Released on September 9, 2025 |
Supported by
|
|
|
Stitch plan
|
Standard |
API availability
|
Available
|
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
|
Anchor Scheduling
|
Supported
|
Advanced Scheduling
|
Supported
|
|
Table-level reset
|
Supported
|
Configurable Replication Methods
|
Unsupported
|
| DATA SELECTION | |||
|
Table selection
|
Supported
|
Column selection
|
Supported
|
|
Select all
|
Supported
|
||
| TRANSPARENCY | |||
|
Extraction Logs
|
Supported
|
Loading Reports
|
Supported
|
Connecting HubSpot
HubSpot setup requirements
To set up HubSpot in Stitch, you need:
-
For HubSpot CRM or Marketing products: Administrator permissions in HubSpot. Note: To replicate email events, you’ll need to have Super Admin permissions in HubSpot.
-
For the HubSpot Sales product: Sales Administrator permissions in HubSpot.
More information about HubSpot user roles and permissions can be found in HubSpot’s documentation.
Step 1: Add HubSpot as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the HubSpot icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch HubSpot” would create a schema called
stitch_hubspotin the destination. Note: Schema names cannot be changed after you save the integration.
Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your HubSpot integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond HubSpot’s default setting of 30 days. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
HubSpot integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 4: Authorize Stitch to access HubSpot
- Next, you’ll be prompted to sign into your HubSpot account.
-
After you log into HubSpot, a screen with a list of your HubSpot accounts will display. Click the account you want to connect to Stitch.
Note that Stitch will only ever read your data. Stitch will never modify or delete any data in your HubSpot account.
- After the authorization process is successfully completed, you’ll be directed back to Stitch.
- Click All Done.
Step 5: Set objects to replicate
The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For HubSpot integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
The Track all Tables and Fields menu in the Tables to Replicate tab - Click the Finalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up HubSpot, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Removing the HubSpot integration
To completely disconnect Stitch from your HubSpot account, you need to delete the integration from Stitch, and uninstall the Stitch app from HubSpot.
Disconnecting HubSpot from Stitch will stop the replication of HubSpot data to your Stitch destination. There will be no impact to the HubSpot data, as Stitch is a read-only integration with HubSpot. All data that has already replicated to your Stitch destination will be maintained and under your control.
Step 1: Deleting your HubSpot integration
To delete your HubSpot integration from your Stitch account:
- Log in to your Stitch account and open the Integrations tab.
- Click your HubSpot integration and click Settings.
- Scroll down to the bottom of the page and click Delete.
- Click Delete to confirm.
Step 2: Uninstalling Stitch in your HubSpot account
To uninstall Stitch in your HubSpot account:
- Log in to your HubSpot account and click the Marketplaces account in the navigation bar.
- Under Manage, click Connected apps.
- Click the Actions drop-down menu in the Stitch app, and click Uninstall.
- In the dialog box that appears, enter
uninstallin the text field and click Uninstall to confirm.
HubSpot table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 4 of this integration.
This is the latest version of the HubSpot integration.
Custom HubSpot field replication
Custom object properties, or fields, are supported by Stitch’s HubSpot integration. Stitch will query the properties list for each object and, if custom fields are available through HubSpot’s API, replicate them to your destination.
The data types of these fields will be the same as the data type in HubSpot. For example: A custom field containing date data will be a date field in your destination.
This is applicable to any object that supports custom fields in HubSpot.
HubSpot date/date-time values & UNIX timestamps
HubSpot uses UNIX-formatted timestamps in milliseconds to store date and datetime data. Stitch doesn’t perform any transformation during the replication process, meaning these values won’t be converted to timestamps before they’re loaded into your destination.
To account for this, consider creating a user-defined function to perform the conversion or building views on top of the raw data.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.
campaigns
The campaigns table contains info about the campaigns in your HubSpot account.
|
Full Table |
|
|
Primary Key |
id |
| Useful links |
companies
The companies table contains info about the companies your HubSpot contacts belong to.
|
Key-based Incremental |
|
|
Primary Key |
companyId |
| Useful links |
contact_lists
The contact_lists table contains info about the contacts lists in your HubSpot account. Contact lists are used to segment contacts into groups, and there are two types: dynamic (smart lists) and static.
Note: You might need to create new connections to continue to replicate contacts_lists data after April 30th 2026. For more information, see HubSpot’s documentation.
|
Key-based Incremental |
|
|
Primary Key |
listId |
|
Replication Key |
updatedAt |
| Useful links |
contacts
The contacts table contains info about individual contacts in HubSpot.
Note: You might need to create new connections to continue to replicate contacts data after April 30th 2026. For more information, see HubSpot’s documentation.
Contact properties
If properties have been set for the contact, additional fields beginning with properties__ will be included in the table. Note: Contacts will only have an entry for a property if that property has been set for the contact’s record.
HubSpot always types the value of properties fields as STRING despite the property type. Refer to HubSpot’s documentation for more info.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
updatedAt |
| Useful links |
contacts_by_company
The contacts_by_company table contains contact and company ID pairs, allowing you to join contacts to relevant company data.
To replicate data from this table, you must also select the parent companies table.
|
Full Table |
|
|
Primary Keys |
contact-id company-id |
| Useful links |
custom_objects
Tables for custom CRM objects in your HubSpot account will have the same name as the object. For example, if you have a custom object named cars, the table will be named cars.
The fields listed below are standard fields; they are included in every custom object table. A field will be added for each property you select when configuring the table. The property names will be prefixed with property_. For example, if you have a property named model, it will appear as property_model.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
updatedAt |
| Useful links |
deal_pipelines
The deal_pipelines table contains info about the deal stage and pipeline properties.
|
Full Table |
|
|
Primary Key |
pipelineId |
| Useful links |
deals
The deals table contains info about the deals in a HubSpot portal.
|
Key-based Incremental |
|
|
Primary Key |
dealId |
| Useful links |
email_events
The email_events table contains info about email events and how recipients interact with content.
Email events and HubSpot permissions
Replicating this table requires Super Admin permissions in HubSpot. The Super Admin role is different than the Admin role, which you can read more about in HubSpot’s documentation.
If this table is selected and you don’t have Super Admin permissions in HubSpot, an error similar to the following will surface in the integration’s Extraction Logs:
tap - ERROR b'{"status":"error","message":"This oauth-token (**********) does not have proper permissions! (requires any of [email-access])", [...]
|
Key-based Incremental |
|
|
Primary Key |
id |
| Useful links |
engagements
The engagements table contains info about all the engagements in a HubSpot portal.
|
Key-based Incremental |
|
|
Primary Key |
engagement_id |
|
Replication Key |
lastUpdated |
| Useful links |
forms
The forms table contains info about your HubSpot website forms.
|
Key-based Incremental |
|
|
Primary Key |
guid |
|
Replication Key |
updatedAt |
| Useful links |
owners
The owners table contains info about the owners that exist in your HubSpot portal. Owners are created and updated in HubSpot when new users are added or when owners are synced from Salesforce to HubSpot.
|
Key-based Incremental |
|
|
Primary Key |
Id |
|
Replication Key |
updatedAt |
| Useful links |
subscription_changes
The subscription_changes table contains info about changes made subscriptions.
|
Key-based Incremental |
|
|
Primary Key |
recipient portalId timestamp |
| Useful links |
tickets
In HubSpot, tickets represents customer requests for help.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
updatedAt |
| Useful links |
workflows
The workflows table contains info about the workflows in your HubSpot portal.
Note: The workflows stream only supports contact-based workflows.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
updatedAt |
| Useful links |