Docs

Admin Guide

Admin Guide / Integrations / HubSpot

Syncing with HubSpot

Understand how Rox synchronizes HubSpot CRM data, maps fields and deal stages, matches records, and determines which accounts users can access.

Rox brings HubSpot Companies, Contacts, and Deals into the platform to support account research, prospecting, and revenue workflows.

In Rox, HubSpot Companies appear as Accounts, and HubSpot Deals appear as Opportunities.

What syncs between HubSpot and Rox

Rox synchronizes supported HubSpot objects and their configured fields into the platform.

HubSpot object

Rox equivalent

Sync direction

Companies

Accounts

HubSpot → Rox

Contacts

People / Contacts

HubSpot → Rox

Deals

Opportunities

HubSpot → Rox

Owners

Users / Account ownership

HubSpot → Rox

The integration supports reading CRM data into Rox. General CRM record writeback is not currently supported through the standard integration.

Sync frequency

Rox synchronizes HubSpot data every 30 minutes.

Changes made in HubSpot may take up to the next scheduled synchronization to appear in Rox.

HubSpot activity data does not have a separate five-minute synchronization interval.

Supported fields

Rox supports mapping standard and custom properties on supported HubSpot objects.

The fields available in Rox depend on the integration's configuration and the properties selected for synchronization.

Properties added in HubSpot after initial setup may need to be refreshed and mapped before they become available in Rox.

Email preferences

Rox can map HubSpot contact email preferences to the corresponding fields in Rox.

For example, HubSpot's Do not allow Emails (donotemail) property maps to Opt out email in Rox.

Review contact preferences before using synchronized contacts for outreach.

Deal pipelines and stages

HubSpot organizes Deals into pipelines, each with its own stages.

Rox uses the configured HubSpot pipeline to populate Opportunities and their corresponding deal stages.

The integration supports one selected deal pipeline.

If your organization uses multiple HubSpot pipelines, choose the pipeline your sales team primarily works with, or discuss your requirements with your Rox account team.

Deals from other pipelines are not included in the configured Rox opportunity pipeline.

Field mappings

Field mappings determine which HubSpot properties populate corresponding fields in Rox.

Organization Admins can review and configure mappings for supported CRM objects.

Review existing mappings

  1. Open Settings → Integrations → HubSpot.

  2. Open CRM Mappings.

  3. Select the relevant object, such as Company, Contact, or Deal.

  4. Review the existing mappings between HubSpot properties and Rox fields.

Required mappings should remain in place. Optional mappings can be adjusted according to your organization's requirements.

Map custom properties

Rox supports custom properties on supported HubSpot objects.

To map a custom property:

  1. Open CRM Mappings for the relevant object.

  2. Identify the HubSpot property you want to synchronize.

  3. Select or create a compatible Rox field.

  4. Configure the mapping between the HubSpot property and the Rox field.

  5. Save the mapping.

Ensure that the Rox field's data type is compatible with the corresponding HubSpot property.

Refresh available properties

If a property was added in HubSpot after the integration was configured, select Refresh fields to retrieve the latest available properties.

You can then map the new property to an appropriate Rox field.

Custom HubSpot objects are not supported through the standard integration. Contact your Rox account team if your workflow requires them.

Entity resolution and record matching

Rox uses record matching to connect HubSpot records with the corresponding entities in Rox.

Once records are matched, their HubSpot identifiers are used to maintain the connection.

Object

Matching information

Accounts

Company domain

Contacts

Email address and associated account

Opportunities

Linked using their HubSpot identifiers after initial synchronization

Users

Email address

Accounts with multiple possible matches

Some CRM configurations require additional review.

Examples include:

  • Multiple HubSpot Companies sharing the same domain.

  • A company represented by several records with different domains.

  • Contacts associated with multiple Companies.

  • Multiple Contact records sharing an email address.

When a Contact is associated with multiple Companies, Rox uses the primary association.

If your HubSpot data includes these scenarios, review the matching configuration with your Rox account team.

Account assignment and access

Account assignment controls which synchronized HubSpot Accounts each Rox user can access.

HubSpot record permissions and Rox account assignment are separate.

Connecting HubSpot authorizes Rox to synchronize data within the integration's permitted scope. Individual users' access to Accounts in Rox is determined by Rox assignment rules rather than their HubSpot record visibility.

Configure assignment rules

Organization Admins can configure assignment rules using HubSpot owner fields and optional account filters.

A rule can include:

  • Owner fields: HubSpot properties that associate Accounts with users, such as Account Owner or supported custom owner fields.

  • Account filters: Additional conditions that restrict which Accounts a user can access.

  • Default rules: Assignment settings for users without individual configurations.

Multiple owner fields can be combined to grant access when a user matches any of the selected owner fields.

An additional account filter can further restrict the assigned Account set.

Review user access

Before rolling out the integration:

  1. Review the owner fields and account filters used for assignment.

  2. Confirm the default assignment rule.

  3. Test access with representative users.

  4. Verify that each user can see the expected Accounts and associated Contacts.

Users without an applicable matching assignment rule may not see any Accounts, even when the underlying HubSpot data has synchronized successfully.

Writeback support

The HubSpot integration is primarily read-only. Rox synchronizes supported CRM data from HubSpot into Rox but does not support general CRM record writeback.

People List writeback is supported, allowing users to write supported People List data to HubSpot.

Other CRM writeback operations are not currently supported through the standard HubSpot integration.

Limitations and considerations

Review these limitations when planning your HubSpot integration.

Area

Consideration

Deal pipelines

One HubSpot deal pipeline is supported.

HubSpot Leads

The HubSpot Leads object, including its pipelines, stages, and lead-specific properties, is not synchronized.

Custom objects

Not supported through the standard integration.

Contacts

Contacts should be associated with a Company for reliable account matching.

Meetings

HubSpot meeting activities are not read or written through the integration.

Account creation

Rox does not automatically create HubSpot Companies by default.

Writeback

General CRM writeback is not supported. People List writeback is available.

Sync frequency

HubSpot data synchronizes every 30 minutes. There is no separate five-minute activity sync.

HubSpot Leads

Rox synchronizes HubSpot Contacts, not the separate HubSpot Leads object.

If a HubSpot Lead is associated with a Contact, the underlying Contact can still be synchronized into Rox, along with its associated Company.

However, Lead-specific information such as lead stages, owners, and pipeline properties is not imported as a separate object.

Data storage and handling

Rox uses Fivetran to ingest HubSpot data into a managed Snowflake warehouse.

The integration synchronizes data within its authorized scope and configured object and field mappings.

If your organization has specific requirements for data residency, retention, or deletion, review them with your Rox account team before connecting HubSpot.

This is particularly important when considering how previously synchronized data should be handled after a mapping is removed or an integration is disconnected.

Related documentation

For questions about supported objects, custom mappings, or your organization's configuration, contact your Rox account team or help@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.