Migrate from Advantage HITS to Pipedrive

Advantage HITS Contact records map to Pipedrive Person. All standard contact fields (name, email, phone, address) migrate directly. We preserve any custom contact properties as text fields in Pipedrive. Email address serves as the dedupe key during import.

Advantage HITS Company records map to Pipedrive Organization. Industry, address, employee count, and annual revenue fields migrate directly. Organization is created before Person records so that the organization_id lookup is satisfied at the moment of Person insert.

Advantage HITS Deal records map to Pipedrive Deal. Deal name, value, close date, owner, and stage migrate. Pipeline stage is resolved by name via the pre-agreed crosswalk (see gotchas) since Advantage HITS stores stages as free text without stable IDs.

Advantage HITS pipeline definitions export separately from deal records. We export the full pipeline structure (stage names, stage order, stage probabilities) and configure Pipedrive Pipelines and stages accordingly before Deal import. Each stage name becomes a Pipedrive stage entry with matching probability percentage.

Advantage HITS stores emails, calls, meetings, and tasks as activity logs within a single export. We split these by the activity type field: emails become Pipedrive email activities, calls become call activities with duration and disposition, meetings become meeting activities with start and end time, and tasks become task activities with status and due date.

User-defined fields on Advantage HITS Contacts enumerate from the UI metadata panel. We map each field by name and type (text, number, date, dropdown) to a Pipedrive Person custom field. Dropdown values on the source map to Pipedrive options list entries.

Deal-level custom fields from Advantage HITS migrate to Pipedrive Deal custom fields via the /dealFields endpoint. Complex field types (multi-select, currency with specific formatting) are mapped case-by-case during scoping.

Tags applied to contacts or deals in Advantage HITS export as comma-separated lists per record. We expand these into individual tag assignments in Pipedrive using the activity_type value 'tag' and the tag_name field. Pipedrive's tagging model is per-record, not per-field.

File attachments linked to records are downloaded during extraction using authenticated requests, preserving original filenames. We re-upload them to the destination Pipedrive record using the attachment API endpoint. Attachments over 50 MB each are flagged for manual handling to avoid session timeout during extraction.

Advantage HITS user accounts export with name, email, role, and active/inactive status. Owner assignments on records remap to Pipedrive User by email match. Users without a matching Pipedrive account enter a reconciliation queue for admin provisioning before record import.

Advantage HITS lifecycle stages and status values export as enumerated picklist fields. We map them to Pipedrive's person_type field or a custom lifecycle stage property, flagging any values without a direct Pipedrive equivalent for the customer to resolve.

Advantage HITS does not expose custom objects via any documented public API endpoint, so custom data structures built by the customer in the UI cannot be programmatically enumerated or migrated. We flag any identified custom object usage during discovery and document it as out-of-scope for the customer to handle separately.