Import Properties

How to get object-based properties added to HockeyStack

Schema:

These columns are required for this import type (column names are expected to match, for import to work properly)

Column	Required	Description
identity	✅	This can be an email or company domain (acme.com)
unique_id	✅	A unique identifier for the row. This guide on data grain helps determine how to come up with the value for this column.

Choosing an Object Type

HockeyStack's standard objects map from CRM objects (most popularly Salesforce and HubSpot). If your object type maps to a standard object type, you can select it and import as such:

HockeyStack Object	Salesforce	HubSpot
Company	Account	Company
User	User	Contact

Company property import example row:

This import is specifically used to add more properties to an existing company object

company_id	identity	Other columns
The company's ID from your CRM	The company's company domain	Other information you would like to import for a company

User property import example row:

This import is specifically used to add more properties to an existing user object

user_id	identity	Other columns
The user's ID from your CRM	The user's email	Other information you would like to import for a user

Custom Object Type:

You can also upload custom object types, which are data entities that extend beyond standard records. A custom object can represent any type of structured information that can be associated with a company or user, such as Outreach Call logs, App Usage details, or other domain-specific datasets.

To do this when configuring a properties import through DataSyncs, you would be able to select an object type and specify "Other".

Example of using Custom Object:

Let's say that you had some Gong call data to import. The table for that could look like this:

gong_call_id	identity	company_id	call_length	call_date
1234567	Email of the person that the Gong call was with	The person's company's ID on Salesforce	456	'2025-03-20T23:53:21.978Z'

Connecting your Custom Object to a Company or User:

• If you specify a company_domain column, this will allow for us to connect this data to the corresponding Company if it's already tracked in HockeyStack

• Specifying a user_id column will allow for us to connect this data to the corresponding User if it's already tracked in HockeyStack.