Migrate from HighLevel to Pipedrive

HighLevel Contacts map to Pipedrive People. Standard fields (first name, last name, email, phone, address) map directly. Lifecycle stage in HighLevel becomes a custom picklist field pipedrive_lifecycle_stage__c on Person. We export from the correct sub-account during scoping and resolve any duplicate email addresses before import to avoid creating duplicate People records in Pipedrive.

HighLevel Companies map to Pipedrive Organizations. HubSpot-style domain-field Company records transfer as Organization with Website field set. The Organization is created before any linked People import so that the Organization ID lookup is satisfied at insert time. Multiple Companies with the same domain deduplicate to one Organization.

HighLevel Opportunities map to Pipedrive Deals. Deal name, value (amount), expected close date, and stage migrate directly. The HighLevel Pipeline name becomes a Pipedrive Pipeline. We preserve the original Pipeline Stage label as a custom Deal field original_stage__c so the admin can audit the mapping after migration.

Each HighLevel Pipeline Stage maps to a Pipedrive Stage within the corresponding Pipeline. Stage probability percentages migrate from HighLevel to Pipedrive Stage probability. Stage names and order are preserved exactly. Pipedrive supports drag-and-drop stage ordering post-migration for any refinement the admin wants to apply.

HighLevel tags on Contacts transfer to Pipedrive Person tags as a comma-separated text field. Tags used for segmentation and Workflow triggers are exported as a flat list per Contact and imported as tags on the corresponding Person record. The tag vocabulary is preserved without transformation so the admin can use Pipedrive's tag-based filtering immediately after migration.

HighLevel Custom Objects (fully configurable via API) require schema introspection before migration. We introspect the custom object's field types, relationships, and constraints, then map to Pipedrive custom fields on Person/Organization/Deal, or to the Products module if the object behaves like a product or subscription record. Pipedrive has no native custom object API, so Products app and custom fields are the only available workarounds. We document the mapping and create the custom fields in Pipedrive during schema setup before data loads begin.

HighLevel Workflows do not migrate to Pipedrive Automation as code. Pipedrive Automation uses record-triggered and scheduled actions in its own builder that is structurally different from HighLevel's trigger-action chain. We export the full Workflow chain (triggers, conditions, action sequences, delays) and deliver a written automation inventory with a recommended Pipedrive Automation equivalent for each Workflow. The admin rebuilds automations in Pipedrive post-migration.

HighLevel Appointments (date, time, linked Contact, status, assigned User) export via API as activity records. These map to Pipedrive Activities (Tasks with type meeting or call) linked to the corresponding Person. Calendar booking link settings and calendar configuration do not transfer and must be recreated in Pipedrive manually.

HighLevel Campaign metadata (name, description, associated contacts) migrates as custom fields on Person or Organization records. Campaign performance metrics (open rates, click rates, bounce rates) and email/SMS content require file-based export and manual reference; they cannot be structured into Pipedrive's data model without a custom reporting module.

HighLevel Users export by email match to Pipedrive Users. We resolve hubspot_owner_id or HighLevel user ID to Pipedrive User ID during import. Any HighLevel User without a matching Pipedrive User goes to a reconciliation queue for the admin to provision before record import resumes. Inactive HighLevel Users are imported as inactive Pipedrive Users with the original email preserved for audit.

HighLevel file attachments on Contacts or Opportunities can be exported and linked to the corresponding Pipedrive Person or Organization record as a Note with an attachment, or uploaded as a Pipedrive File. Files exceeding 25MB require chunked migration with retry logic and are flagged for the admin to handle manually if the migration script encounters upload timeouts.

HighLevel Form field mappings and submission records exist as contact properties and workflow triggers rather than standalone records. We document the form field schema (field name, field type, required/optional status) as a reference for the admin to recreate in Pipedrive. Form submission histories do not export as discrete records; contact property values from the most recent submission migrate as field values on the Person record.