Migrate from HubSpot to Pipedrive

HubSpot Contacts migrate to Pipedrive Persons. All standard contact properties (name, email, phone, address, job title, company association) map directly. Custom contact properties migrate to Pipedrive custom Person fields, with field type mapping: HubSpot single-line text becomes Pipedrive text, HubSpot dropdown becomes Pipedrive enum, HubSpot multi-checkbox becomes Pipedrive set of options. The HubSpot Lifecycle Stage property migrates to a custom Pipedrive text or enum field hs_lifecycle_stage__c for reporting continuity.

HubSpot Company records map directly to Pipedrive Organizations. The HubSpot company domain becomes the Organization's Website field. We preserve the contact-to-company association by linking the migrated Person record to the Organization via Pipedrive's Person-Organization relationship at import time.

HubSpot Deals map to Pipedrive Deals 1:1. The HubSpot dealstage property maps to a Pipedrive pipeline stage via a pre-configured stage map created during scoping. Deal amount, close date, owner (hubspot_owner_id), and custom deal fields migrate directly. We configure the Pipedrive pipeline stages to match the HubSpot pipeline stages before migration begins.

HubSpot's deal pipelines map to Pipedrive Pipelines. We create Pipedrive Pipelines during the configuration phase, configuring each stage name, stage probability, and stage order to match the source HubSpot pipeline. If the HubSpot account has multiple pipelines, each becomes a separate Pipedrive Pipeline with its own stage configuration. Pipedrive's pipeline model supports this natively across all paid tiers.

HubSpot Lead records (Enterprise-only on source) merge into Pipedrive Persons. The Lead object does not exist in Pipedrive; unqualified prospects land as Persons with the original HubSpot lead score, lead status, and source tracked in custom Person fields. We preserve any HubSpot Lead-specific properties (hs_lead_status, hs_lead_source, hs_analytics_source) as custom fields on the Person record.

HubSpot Products map to Pipedrive Products. The HubSpot product name, SKU (hs_sku), price, and description migrate to Pipedrive Product fields. Products must exist in Pipedrive before Line Items can be linked at migration time.

HubSpot Line Items map to Pipedrive Deal Products. We resolve the Product reference and associate each Line Item with the correct Deal at migration time using the deal's HubSpot ID as a lookup key. Quantity, item price, and discount migrate to the corresponding Pipedrive Deal Product fields.

HubSpot Owners map to Pipedrive Users by email match. We extract every HubSpot Owner referenced on Contacts, Companies, Deals, and Activities and match by email against the destination Pipedrive User list. Any HubSpot Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision the User before record import resumes.

HubSpot email engagements migrate to Pipedrive Activities with type = email. The email subject, body, timestamp, and direction (sent/received) transfer to the corresponding Pipedrive Activity fields. The Activity is linked to the migrated Person (Who) and, if applicable, the Organization or Deal (Entity). We batch emails by timestamp and insert via Pipedrive's activities API, handling rate limits with exponential backoff.

HubSpot call engagements migrate to Pipedrive Activities with type = call. Call duration, disposition, direction, and recording URL migrate to custom Pipedrive Activity fields. The Activity is linked to the Person and Deal. We preserve call timeline ordering by setting the Pipedrive Activity start timestamp to the original HubSpot timestamp.

HubSpot meeting engagements migrate to Pipedrive Activities with type = scheduled. Start time, end time, location, and title transfer to the corresponding Pipedrive Activity fields. Attendees are resolved to migrated Person records and added as Activity participants.

HubSpot Notes (engagement type NOTE) migrate to Pipedrive Activities with type = note. The note body and timestamp transfer directly. Notes linked to a Contact, Company, or Deal are attached to the corresponding migrated Person, Organization, or Deal in Pipedrive.

HubSpot Task engagements map to Pipedrive Activities with type = task. Task subject, due date, completion status, and assignee migrate directly. Completed tasks transfer with status marked complete; open tasks transfer as pending.

HubSpot Tickets have no direct Pipedrive equivalent. Pipedrive does not have a native ticketing or support object. We work with the customer during scoping to decide: Tickets with a sales context (pre-sale support, deal-adjacent questions) migrate to Pipedrive Deals with a custom ticket reference field. Pure support tickets migrate as Activity notes attached to the Person, or the customer stands up a dedicated support tool (Zendesk, Front) post-migration and we deliver a Ticket-to-support-tool mapping document.

HubSpot custom objects (Enterprise-only on source) have no Pipedrive equivalent custom object type. We re-architect each HubSpot custom object as a set of custom fields on the most appropriate Pipedrive standard object (Person, Organization, or Deal) and, where a custom object had relationships to other objects, we represent those relationships as custom ID fields or linked Deal-Organization associations. The customer reviews and approves the re-model before migration.

HubSpot tags migrate to Pipedrive Labels. Tags are applied to the corresponding Person, Organization, or Deal record based on the HubSpot tag's associated object type. Multi-value tag sets on a single record become Pipedrive Label sets on that record.