Migrate from HighQ to HubSpot

HighQ iSheets that store person-level records (names, emails, phone numbers, job titles, addresses, LinkedIn profiles) map directly to HubSpot Contacts. Each iSheet row becomes one Contact record. The iSheet column names map to HubSpot standard and custom properties. Any HighQ user reference columns that point to contacts within the same iSheet are resolved to ensure the correct contact associations are preserved during migration.

iSheets tracking organizational data — company name, domain, industry, employee count, annual revenue, and address fields — map to HubSpot Companies. Multi-column company records collapse into one Company record per unique organization name. We validate uniqueness by company name and domain to prevent duplicate Company records from being created during the bulk import process.

iSheets tracking transaction value, deal stage, close date, and assigned owner map to HubSpot Deals. HighQ's stage-status column maps to HubSpot deal stage via value mapping. The deal owner resolves by email match to a HubSpot user. Any unmatched owners are flagged for manual resolution before the migration batch commits to production.

HighQ sites representing distinct business units or matters map to a HubSpot custom object (Enterprise tier) or to a Company record annotated with a Site_Name__c custom field. The mapping approach depends on your HubSpot subscription level and whether you need hierarchical site relationships that custom objects provide versus the simpler flat structure of Company records.

HighQ iSheets with domain-specific columns that don't map to Contact, Company, or Deal become HubSpot custom objects on Enterprise plans. Each iSheet column becomes a custom property on that object. Associations between iSheets (parent-child relationships) become custom object associations in HubSpot. We create the custom object schema before importing any records.

Files attached to HighQ iSheet rows or document workspaces re-upload to HubSpot Files. Files are associated to the corresponding HubSpot CRM record by reference to the source iSheet row ID. Inline images embedded in documents are downloaded and rehosted in HubSpot's file store with the same association logic applied.

HighQ workflow rules (event-driven task reassignment, due-date triggers, iSheet state-change actions) have no HubSpot equivalent at the automation level. They must be rebuilt in HubSpot's workflow builder. We export the workflow rule definitions as a reference document for your HubSpot admin.

HighQ user accounts (name, email, role) migrate to HubSpot Users. The email address is the matching key for owner resolution — each HighQ user with an assigned iSheet record must have a corresponding HubSpot user account, or records are assigned to a fallback owner flagged for review.

HubSpot's CreatedDate is set at import time. To preserve historical record creation dates from HighQ, we map the original iSheet row creation timestamp to a custom datetime property (e.g., HighQ_Created_Date__c) on the target CRM object. This ensures historical reporting continuity and allows you to filter or sort by the original creation date in HubSpot after migration completes.

HighQ's granular per-site and per-document permission roles cannot migrate to HubSpot's profile and team-based sharing model. Post-migration, your HubSpot admin configures access based on HubSpot's native permission hierarchy. We export the original HighQ permission structure as a permission-matrix document so your admin can reference the original settings when rebuilding access controls in HubSpot.

HighQ document workspaces containing multiple files map to a HubSpot Files folder structure. Each file retains its original name and upload date. A custom text property (Source_HighQ_Workspace__c) tags files that originated from a shared workspace, allowing you to filter or report on file origins post-migration. This preserves workspace context without requiring separate folder hierarchies in HubSpot.

HighQ iSheet columns that reference another user (e.g., an 'Assigned To' column) map to a HubSpot user lookup property if the reference is an internal HighQ user. If the reference points to an iSheet contact record rather than a system user, we map to a Contact property. The column type detection in the pre-migration audit determines which property type to create.