Sync HubSpot users and accounts

What HubSpot users and accounts sync does

Set up separate HubSpot User and Account integrations to bring CRM context into Enterpret:

• Users synced from HubSpot Contacts

• Accounts synced from HubSpot Companies

If your user or account data lives in a custom object, contact your Enterpret team to confirm a supported mapping before configuring it. A custom object appearing in the selector does not confirm that it can sync as Users or Accounts.

To analyze customer feedback stored in HubSpot objects, use Import HubSpot feedback. Updating configured HubSpot deal fields uses the separate HubSpot Deals Writeback setup.

Synced HubSpot records provide CRM context for feedback after the relevant matching rules and relationships are configured and processed. You can use available user and account properties, such as lifecycle stage, plan type, ARR or industry, once the corresponding records and fields are available in Enterpret.

These User and Account integrations read CRM data into Enterpret. Their sync workflow does not write, modify, or delete HubSpot records. Deal writeback is configured separately.

A few things to note:

• It's a separate integration from HubSpot Feedback sources (tickets, conversations), which are covered by other Enterpret integrations.

• User data and Account data are set up as two separate integrations, even when they share the same HubSpot portal. This lets you sync just one or both depending on what you need.

• The sync requests available non-archived standard and custom properties on Contacts or Companies. The fields you can use in Enterpret depend on the values returned for imported records and subsequent processing. Metadata visibility controls let you hide fields from view; they do not select a smaller HubSpot property list for the sync.

Before you begin

You'll need the following:

• A HubSpot user account with permission to install third-party apps on your portal. In most HubSpot accounts, this is restricted to users with the Super Admin role or those who have been explicitly granted App Marketplace access. If you're not sure, check with your HubSpot admin. If you can't install the Enterpret app during setup, you'll need someone with the right permissions to do it on your behalf. The person installing doesn't need to be the same person who uses Enterpret afterwards. Once installed, the integration works for your whole Enterpret workspace.

• Admin access to your Enterpret workspace.

• The HubSpot integration enabled on your Enterpret account. If you don't see HubSpot as an option on the Integrations page, reach out to your CSM. It's a quick flip on our side.

If you want to connect multiple HubSpot portals, you'll need to repeat the setup for each one as separate integrations.

What permissions does Enterpret request, and why?

Review the permissions on the HubSpot consent screen for your connection. The capabilities below explain how CRM read access relates to User and Account sync; they are not a universal permission list for every HubSpot flow.

View contacts and their properties

• What it lets Enterpret do: read Contact records and the property values available to the connection.

• Why we need it: so Enterpret can ingest Contacts as Users when that's the object your team uses for user data.

View contact property definitions

• What it lets Enterpret do: read the available standard and custom Contact property definitions.

• Why we need it: Enterpret uses property definitions to request the available Contact fields, including custom properties.

View companies and their properties

• What it lets Enterpret do: read Company records and the property values available to the connection.

• Why we need it: so Enterpret can ingest Companies as Accounts when that's the object your team uses for account data.

View company property definitions

• What it lets Enterpret do: read the available standard and custom Company property definitions.

• Why we need it: Enterpret uses property definitions to request the available Company fields, including custom properties.

View Custom Objects and their schemas

• What it lets Enterpret do: read the list of Custom Objects on your portal and the records and properties within them.

• Custom objects may appear during object discovery. For User or Account sync, confirm a supported mapping with your Enterpret team before selecting one; discovery alone does not establish successful ingestion.

View owners

• What it lets Enterpret do: read the list of users in your HubSpot portal who can be assigned as owners.

• Owner access can support HubSpot workflows, but this User and Account sync can retain owner IDs as property values. Confirm any owner-name or email mapping separately.

Scope of User and Account sync

• The User and Account sync workflow reads Contacts or Companies into Enterpret. It does not configure HubSpot deal updates; those require the separate Deals Writeback setup and authorization.

• This guide covers Contacts or Companies for CRM context. Feedback ingestion from other HubSpot objects and Deals integrations are separate workflows; choose the integration that matches your task.

• Enterpret will never share your data outside your workspace. Your HubSpot data is stored within your Enterpret instance with the same security controls as all your other Enterpret data.

About tokens and storage

• Enterpret stores your HubSpot access token and refresh token encrypted at rest.

• Access tokens are automatically refreshed in the background. You don't need to re-authorize manually unless you actively revoke the app or HubSpot invalidates the connection.

• You can revoke Enterpret's access at any time from your HubSpot portal settings (HubSpot → Settings → Integrations → Connected Apps). In Enterpret, admins can deactivate the integration from the Integrations page. Permanent deletion is not available in the user-facing UI; contact Enterpret Support to request it.

Setting up the integration

Step 1: Start the connection

1. In Enterpret, go to Settings → Integrations.

2. Click on New Integrations and search for Hubspot
   

3. Choose between User or Account Integration.
   

4. Click Connect.

Tip: if you want to sync both user and account data from HubSpot, you'll set them up as two separate integrations. Start with one, then repeat the flow for the other.

Step 2: Authorize Enterpret on HubSpot

1. You'll be redirected to HubSpot's authorization screen.
   

2. If you're logged into multiple HubSpot portals, pick the one you want to connect.
   

3. Review the permissions Enterpret is requesting (see the permissions section above for details on each).
   

4. Click Install.

Enterpret will redirect you back to your Enterpret dashboard.

Step 3: Pick which HubSpot object to sync

After authorization completes, a configuration drawer will open automatically. Here you select which HubSpot object Enterpret should sync.

The selector is grouped into two sections:

• Standard. Contacts for a User integration, or Companies for an Account integration.

• Custom. Custom objects may appear. Confirm a supported User or Account mapping with your Enterpret team before using one.

Enterpret pre-selects a sensible default:

• For a User integration, Contacts is selected by default.

• For an Account integration, Companies is selected by default.

If your team uses the standard Contacts and Companies objects for user and account data, just accept the defaults and click Save.

If your CRM stores user or account data in a custom object, stop here and confirm the supported setup with your Enterpret team. Do not assume that selecting it will sync the same way as Contacts or Companies.

Click Save when you're done.

Step 4: Syncing begins

After you save the object configuration, Enterpret schedules background syncing. Check the integration status and sync information to follow its progress.

What happens next:

• The normal initial window starts at the beginning of the month 36 months earlier. Your organization can have a different backfill window. HubSpot User and Account imports select records by their last-modified timestamp, so an older record can be included if it changed within the window, while an unchanged record outside the window can be absent.

• Subsequent pulls normally use a four-hour interval. Job configuration can change that interval, and actual freshness also depends on the eligibility buffer, API access, queued work and processing.

• Records and metadata become available as they are fetched and processed. During initial processing, check the integration status and available record and metadata information.

• Initial processing time varies with portal size, the records included in the window, HubSpot API limits and the processing backlog. Contact your Enterpret team if you need a different history window or help checking progress.

What data gets synced

For the standard setup, Enterpret discovers non-archived property names and requests those fields on Contacts or Companies. Custom properties on those standard objects are distinct from a separate custom object. Available fields can include:

• Standard properties that HubSpot returns for the selected object

• Calculated properties, when returned by HubSpot

• Hidden properties, when returned by HubSpot

• Custom properties on Contacts or Companies that HubSpot makes available to the connection

Check the available properties and sample imported records in Enterpret before relying on a field for analysis.

Examples of what comes through on Contacts

• Identity properties, such as email, name, job title or country, when populated and returned on the Contact

• Marketing or lifecycle properties, when populated and returned on the Contact

• Engagement summary properties, when populated on the Contact; separate activity records are not traversed by this sync

• Ownership properties, such as owner or team IDs, when present on the Contact

• Custom Contact properties, such as plan type or user role, when available to the connection

Examples of what comes through on Companies

• Company properties, such as domain, industry, country, employee count or annual revenue, when populated and returned

• Lifecycle or sales context stored on the Company itself; an associated Deal stage requires an actual Company property or a separate supported workflow

• Ownership properties, such as owner or team IDs, when present on the Company

• Custom Company properties, such as contract dates, segment tags or account health, when available to the connection

Before using a custom object for Users or Accounts

• Contact your Enterpret team with the custom object name and the fields that represent your users or accounts.

• Confirm the supported mapping, required identifiers, and available properties before relying on that setup.

Data availability and limits

• Archived property definitions are excluded from field discovery.

• Null values are skipped during metadata processing. Empty strings can still be retained, so a blank-looking value and an absent value can behave differently. Field availability reflects the records actually imported and processed.

• Associated records. This sync reads Contact or Company properties and does not traverse related Deals, Tickets, Notes or Email records.

• Activity content. Text copied into a Contact or Company property can still be imported when that property is returned. Use a separate supported workflow for the activity records themselves.

A few things to be aware of

• Enumeration properties can retain HubSpot internal keys rather than the labels displayed in HubSpot. Inspect the imported values before building filters.

• Owner fields can contain owner identifiers rather than names or email addresses. Check the imported value and field type before using an owner property.

• Values can arrive as strings, including values that look numeric or Boolean. Check the Enterpret field type and sample values before using a field in a numeric calculation or Boolean filter.

How your HubSpot data connects to feedback

Syncing CRM records and linking them to feedback are separate stages. Confirm the matching rules for each feedback source with your Enterpret team, then check example synced records and linked feedback.

Users. Feedback can link to a User through identifiers available on both sides, such as email fields when that matching rule is configured. HubSpot record IDs and email values are different identifiers. Check that the selected values are populated and use compatible formats.

Accounts. Account links depend on configured identifiers or relationships. A Company domain can be used when the corresponding value is available in the feedback source and the rule is configured. A User-to-Account relationship also needs a supported mapping; importing a Contact email and a Company domain alone does not establish that relationship. Missing, inconsistent or duplicate identifiers can prevent or complicate matching.

Common use cases

• Prioritize by revenue. Filter feedback to only customers above a certain ARR threshold.

• Segment by lifecycle. Compare feedback themes between trial users, paid users, and churned accounts.

• Focus on specific industries or personas. See how feedback differs between healthcare customers and retail customers, or between engineers and marketers.

• Track specific account cohorts. Build a cohort of your top 20 accounts by ARR and see their feedback in one view.

• Attribute feedback to owners. See which accounts and their feedback are owned by which CSM or AE.

For a detailed guide on how to link user and account data to feedback across all your integrations, see Syncing Users and Accounts

Managing your integration

Viewing your integration

On the Integrations page, you'll see your HubSpot integration listed under either User Data or Account Data depending on what you connected. Click into it to see:

• The connected HubSpot portal name

• The HubSpot object being synced: Contacts for Users, Companies for Accounts, or details of any custom mapping confirmed with your Enterpret team

• Record count and last sync timestamp

• The metadata fields that are actively being ingested. You can choose what to hide by following the steps mentioned here Managing Metadata.

• Connection status

Disabling an integration

If you want to temporarily pause syncing without losing your setup:

1. Open the integration detail page.

2. Toggle the integration to Disabled.

Disabling pauses new scheduled pulls while keeping the integration configuration. After re-enabling, confirm that sync activity resumes. Contact your Enterpret team if it does not or if you need help checking for gaps.

Re-authorizing or disconnecting

When you'll need to re-authorize

HubSpot may invalidate Enterpret's access in a few situations:

• You uninstall the Enterpret app on HubSpot's side.

• A HubSpot admin revokes the Enterpret app's permissions.

• A security event on your HubSpot account rotates credentials.

When this happens, your next Enterpret sync will fail, and you'll see a banner on the integration tile:

Connection expired. Click to re-authorize.

How to re-authorize

1. Click the banner on the integration tile (or the Reconnect button on the integration page).

2. You'll be redirected to HubSpot's authorization screen. Same flow as the initial setup.

3. Click Install to re-grant access.

After re-authorizing, confirm the selected object, connection status and subsequent sync activity. Saved sync state can support incremental continuation, but connection recovery alone does not establish that all missed data has been imported. Ask your Enterpret team whether a replay or additional backfill is needed.

Frequently asked questions