Migrate from Dr.DENTES to Pipedrive

HubSpot Contact maps directly to Pipedrive Person. Every standard field such as name, email, phone, and job title has a Pipedrive equivalent, preserving the original data format. Contacts that lack a HubSpot company association become orphan Persons; FlitStack can optionally attach these to a default Organization or a placeholder company to keep the data structure consistent.

HubSpot lifecycle_stage has no native Pipedrive equivalent, so FlitStack creates a pick‑list custom field called lifecycle_stage on the Person object, copying HubSpot's exact stage values and order. Stage‑transition timestamps are stored as separate datetime custom fields to preserve the history of each contact's progression and enable reporting continuity in Pipedrive.

HubSpot Company maps directly to Pipedrive Organization, copying fields such as name, domain, industry, employee count, and annual revenue on a one‑to‑one basis. Because Pipedrive does not support a native parent‑child hierarchy for organizations, HubSpot's parent‑company relationships are stored as a custom parent_org_id field, allowing teams to reconstruct corporate structures in Pipedrive through custom reporting or filtering.

HubSpot Deal maps directly to Pipedrive Deal, making this the most straightforward object mapping in the migration. Core fields such as deal name, amount, close date, and owner are transferred and resolved by matching owner email addresses between HubSpot and Pipedrive. The pipeline‑stage mapping is handled in a separate step (see Pipeline mapping row) to ensure each deal lands in the correct Pipedrive pipeline and stage.

HubSpot pipeline becomes a Pipedrive Pipeline; each distinct HubSpot pipeline translates into its own Pipedrive Pipeline because Pipedrive scopes stage names per pipeline. Consequently, a HubSpot configuration with three separate pipelines results in three Pipedrive Pipelines, each containing its own ordered set of stages that reflect the original HubSpot stage order and probability settings.

HubSpot stage names map to Pipedrive Stage names on a value‑by‑value basis within each Pipeline, preserving the exact stage labels as they appear in HubSpot. The display order of stages is transferred to maintain the visual sequence in Pipedrive. Stage probability percentages and forecast categories are manually re‑applied in Pipedrive because HubSpot's native probability metadata does not export automatically.

HubSpot call engagements are migrated as Pipedrive Activities with type='call', preserving the original call timestamps, duration, direction (inbound or outbound), and the owner resolved by email match. The resulting Pipedrive Activity record is linked to the corresponding migrated Person or Deal via its ID, ensuring that call history remains associated with the correct CRM entity.

HubSpot email engagements are transferred as Pipedrive Activities with type='email', preserving the subject line, body content, and the sent or received timestamp for each message. Email attachments are downloaded from HubSpot and re‑uploaded to Pipedrive's file storage; any attachment exceeding Pipedrive's 25 MB per‑file limit is flagged in the migration report for manual handling.

HubSpot meeting engagements become Pipedrive Activities with type='meeting', retaining the start time, end time, location, and attendee list, with each attendee resolved by matching their email address to a Pipedrive user or contact. Because Pipedrive generates its own video meeting links, any HubSpot video link is saved as a custom text field on the activity to preserve the original meeting URL.

HubSpot notes are migrated as Pipedrive Notes attached to the corresponding Person, Organization, or Deal record, preserving rich‑text formatting such as bold, italics, and hyperlinks. When a HubSpot note is associated with multiple records, FlitStack creates separate Note entries on each related entity in Pipedrive, because Pipedrive Notes can only be linked to a single record.

HubSpot custom objects (Enterprise tier) map to custom fields on the nearest Pipedrive entity (Person, Organization, or Deal). Custom-object relationships that are N:N in HubSpot must be stored as pipe-separated custom fields in Pipedrive since Pipedrive does not support many-to-many junction objects natively.

HubSpot association labels (Decision Maker, Influencer, Champion) have no Pipedrive equivalent. We create a custom pick-list field (association_role) on the Person-Deal relationship or on Person directly. Teams choose whether to replicate every label or collapse into a simpler role set.