Migrate from HighQ to Pipedrive

HighQ People map directly to Pipedrive Persons. Name, email, phone, job title, address, and owner all translate field-for-field. HighQ person records without an email address are flagged for manual review before migration — Pipedrive requires at least one unique identifier.

HighQ Organizations map to Pipedrive Organizations, translating company name, domain/website, industry, employee count, and annual revenue directly. Parent‑child hierarchies in HighQ become the 'Parent organization' field on the child org record; if an org has multiple parents, secondary parent links are stored in a custom field. During planning, a value‑mapping table aligns HighQ industry pick‑list values to Pipedrive’s industry pick‑list, defaulting unmatched entries to ‘Other’.

HighQ links between People and Organizations translate as Pipedrive's org_id field on the Person record. If a HighQ person is linked to multiple organizations, the most recently updated organization is set as primary in Pipedrive and secondary links are noted in a custom field.

HighQ projects or deal-level records map to Pipedrive Deals. Deal name, expected value, stage, owner, and close date translate to Pipedrive Deal fields. HighQ deal status (active, closed won, closed lost) maps to Pipedrive stage names using a value-mapping table defined before migration.

HighQ iSheets are the primary extensibility mechanism with no Pipedrive equivalent. Each iSheet column becomes a Pipedrive custom field on the entity the iSheet is associated with (Person, Organization, or Deal). Multi-column iSheet rows with one-to-many relationships are decomposed into delimited custom field strings or stored as JSON in a single long-text custom field.

HighQ task records with type (call, meeting, to-do) map to Pipedrive Activity records of the corresponding type. Task subject, due date, completed date, owner, and notes translate directly. HighQ rule-based task reassignments do not migrate — Pipedrive activities are owner-assigned at record creation.

HighQ files attached to Person, Organization, or Deal records are downloaded and re-uploaded to Pipedrive Files, linked to the corresponding Pipedrive entity. Folder hierarchy from HighQ is lost — document context from folder names is preserved in a custom field or note on the file.

HighQ Workflow rules (reassignment triggers, date-change actions, multi-step sequences) have no Pipedrive equivalent and do not migrate. FlitStack exports workflow definitions as a structured JSON reference document. Your Pipedrive admin uses this to rebuild logic in Pipedrive Automations (available on Advanced+ plans) or Sequences (Professional+ plans).

HighQ Sites and Workspaces are permission containers with no direct Pipedrive equivalent. Pipedrive uses visibility groups and sharing settings for data access control. Site-level user permissions map to Pipedrive visibility group assignments, but Workspace-specific access rules require manual configuration in Pipedrive after migration.

HighQ user accounts (name, email, role) map to Pipedrive Users. Owner assignment on migrated records uses email matching against Pipedrive user email addresses. Unmatched HighQ users are flagged before migration — either invite them to Pipedrive first or reassign their records to a fallback Pipedrive user.

HighQ stores client-specific metadata fields at the organization or site level that are not part of the standard Person or Organization schema. These migrate as custom fields on the corresponding Pipedrive Organization record. Metadata field types (date, number, picklist) are matched to Pipedrive custom field types during the field-mapping phase.

HighQ notes and comments attached to tasks, documents, or people migrate as Pipedrive Notes linked to the corresponding Person, Organization, or Deal. Author and timestamp are preserved in the Note record. HighQ's rich-text formatting is simplified to plain text where formatting cannot be represented in Pipedrive Notes.