This article explains which properties—both standard and custom—are exchanged between OfficeRnD and HubSpot, how they are matched or created, and how updates propagate. It also shows typical use cases where Companies or Members may be unlinked, matched, or fully updated in both systems.
Properties synced between OfficeRnD and HubSpot
The following properties are synced between OfficeRnD and HubSpot. The standard properties are synced by default and can't be configured or changed. The additional properties are based on your configuration and can be changed or skipped.
Standard properties
Companies
Name
URL (website)
Address (Street Address, Country, State, City, Zip Code)
Description
Members
Name
Email
Phone
Address (Street Address, Country, State, City, Zip Code)
Opportunities
Name
DealSize
Probability
StartDate (Expected close date)
Status
Additional properties (based on configuration)
Companies
Status (only from OfficeRnD to Hubspot)
Email
Custom properties created in OfficeRnD (Learn how to create custom properties →)
Members
Status (only from OfficeRnD to Hubspot)
Custom properties created in OfficeRnD (Learn how to create custom properties →)
Opportunities
Custom properties created in OfficeRnD (Learn how to create custom properties →)
Sync process for Companies and Members
After connecting HubSpot and OfficeRnD and syncing the data between them, the following events will occur:
Unlink
If any Company or Member was linked to a related entity in HubSpot, and that entity no longer exists in HubSpot, OfficeRnD will remove the obsolete link. See the example use case below ↓
Create and link
Try to match existing OfficeRnD Companies and Members with ones that come from HubSpot based on email or name.
If they match, OfficeRnD will "link" them and not create new entities.
If they don't exist, OfficeRnD will create new Companies or Members.
For accounts with multiple locations, the additional configuration must enable creating Companies and Members in appropriate Locations in OfficeRnD.
If some Companies or Members exist in OfficeRnD but don't exist in HubSpot, then these entities will not be created in HubSpot.
Update
OfficeRnD will sync the values of all configured properties for any linked entity.
A property can be synced either:
One-way from HubSpot to OfficeRnD.
One-way from OfficeRnD to HubSpot.
Two-way – Changes in one system will be reflected in the other. If there are simultaneous changes in both systems, OfficeRnD values will take priority.
Property sync direction (←, → and ↔) is configurable for each property.
If the sync direction is HubSpot to OfficeRnd (←), property changes will only be synced from Hubspot to OfficeRnD.
If the sync direction is Office to HubSpot (→), property changes will only be synced from OfficeRnD to HubSpot.
If the sync direction is Two-way (↔), property changes made in one system will propagate to the other. If there are simultaneous changes in both systems, OfficeRnD values will take priority.
By default, standard properties will be synced Two-way (↔).
Use cases
The following use cases provide examples of how a sync would work and what would happen in different scenarios after the sync is complete. These examples do not cover all possible cases.
1. Unlink
In the following example, Companies and Members linked to non-existing entities in HubSpot are "unlinked", and the linking references are removed.
Initial
OfficeRnD | HubSpot |
Company 1 hs_link: non-existing-1 |
|
Company 1 Member hs_link: non-existing-2 |
|
Member 1 hs_link: non-existing-3 |
|
After sync
OfficeRnD | HubSpot |
Company 1 |
|
Company 1 Member |
|
Member 1 |
|
2. Create and link
In the following example, non-existing Companies and Members are added to OfficeRnD; existing ones are linked. Companies and Members that exist in OfficeRnD but not in HubSpot are not created in HubSpot.
Initial
OfficeRnD | HubSpot |
| Company 1 id: 1 |
| Company 1 Member id: 2 |
| Member 1 id: 3 |
Company 2 | Company 2 id: 4 |
Company 2 Member | Company 2 Member id: 5 |
Member 2 | Member 2 id: 6 |
Company 3 |
|
Company 3 Member |
|
Member 2 |
|
After sync
OfficeRnD | HubSpot |
Company 1 hs_link: 1 | Company 1 id: 1 |
Company 1 Member hs_link: 2 | Company 1 Member id: 2 |
Member 1 hs_link: 3 | Member 1 id: 3 |
Company 2 hs_link: 4 | Company 2 id: 4 |
Company 2 Member hs_link: 5 | Company 2 Member id: 5 |
Member 2 hs_link: 6 | Member 2 id: 6 |
Company 3 |
|
Company 3 Member |
|
Member 2 |
|
3. Update
In the following example, updates to properties in HubSpot on linked Companies and Members are propagated to OfficeRnD.
Initial
OfficeRnD | HubSpot |
Company 2 hs_link: 4 Description: Descr 1 | Company 2 id: 4 Description: New Descr 1 (changed from Descr 1) |
Company 2 Member hs_link: 5 Phone: 111111111 | Company 2 Member id: 5 Phone: 22222222 (changed from 111111111) |
Member 2 hs_link: 6 Phone: 333333333 | Member 2 id: 6 Phone: 44444444 (changed from 333333333) |
After sync
OfficeRnD | HubSpot |
Company 2 hs_link: 4 Description: New Descr 1 | Company 2 id: 4 Description: New Descr 1 |
Company 2 Member hs_link: 5 Phone: 22222222 | Company 2 Member id: 5 Phone: 22222222 |
Member 2 hs_link: 6 Phone: 44444444 | Member 2 id: 6 Phone: 44444444 |