Migrate from Populate to Pipedrive

HubSpot Contact maps directly to Pipedrive Person. The email, name, phone, job title, and address fields map field-for-field. HubSpot lifecycle_stage has no Pipedrive native equivalent — it becomes a custom pick-list field (lifecycle_stage__c) on the Person record with the same value set as the source.

HubSpot lifecycle stages (subscriber, lead, MQL, SQL, customer, evangelist) map to a custom pick-list field on Pipedrive Person. The exact values are preserved. Stage-change timestamps from HubSpot's property history are not available via the standard API — we surface them as a note on the Person record during migration.

HubSpot Company maps to Pipedrive Organization. Name, domain/website, industry, employee count, annual revenue, and address fields map directly. HubSpot's parent-child company hierarchy maps to Pipedrive's address_data structure — parent companies must be migrated first and their Pipedrive IDs used as the parent org_id reference.

HubSpot Deal maps 1:1 to Pipedrive Deal. Deal name, amount, expected close date, owner, and pipeline stage all have direct equivalents. The pipeline-to-pipeline and stage-to-stage mapping is done by name string comparison; stage order and probability values are mapped per pipeline to preserve forecast accuracy.

HubSpot pipeline maps directly to Pipedrive Pipeline. Each pipeline's stages map one-to-one by stage name string. Stage probability and forecast category values from HubSpot are stored as custom fields in Pipedrive so that revenue forecasting is consistent after migration. This preserves forecast accuracy and ensures deal-weighted pipeline reports reflect historical stage probabilities.

HubSpot stage names are mapped to Pipedrive stage names by string comparison. The stage order is preserved from HubSpot's pipeline configuration. If two pipelines share a stage name (e.g., 'Demo Given'), both Pipedrive stages receive the same name and are distinguished only by their Pipeline context — this is a known Pipedrive constraint.

HubSpot calls map to Pipedrive Activities with type set to 'call'. The call subject, duration, direction (inbound/outbound), outcome, and original timestamp are preserved. The activity is linked to the Person record via the person_id field. Call recordings are exported as file attachments and re-linked to the Pipedrive activity record.

HubSpot email records map to Pipedrive Activity records with type 'email'. The email subject, body text, and timestamp are preserved. HubSpot's email headers and thread tracking are not available in Pipedrive's activity model — the activity stores the most recent email in the thread as a single record.

HubSpot meetings map to Pipedrive Activities with type 'meeting'. The meeting title, start/end timestamps, location, and outcome notes are preserved. HubSpot's meeting link and calendar integration data is not migratable — those connections must be rebuilt in Pipedrive. The meeting title, attendees (from Person records), and outcome notes transfer to maintain historical meeting context.

HubSpot notes map to Pipedrive Activity records with type 'note'. Rich-text formatting is preserved where the Pipedrive API supports it. Notes attached to specific contacts or companies are linked via the person_id or org_id field. Notes with multiple associations in HubSpot are duplicated to each Pipedrive record for reference.

HubSpot file attachments on contacts, companies, and deals are downloaded and re-uploaded to Pipedrive Files, then linked to the corresponding Person, Organization, or Deal record. Pipedrive's file storage limits apply — files over 50MB require a different handling approach. Inline images in notes are extracted and re-hosted as Pipedrive Files.

HubSpot products in the CRM catalog map directly to Pipedrive Products. Product name, SKU, price, and currency map field-for-field. Products associated with deals are linked via the deal_id in Pipedrive. Bundle and discount configurations from HubSpot require manual rebuild in Pipedrive's product pricing model.