Migrate from OneHash CRM to Pipedrive

OneHash Lead records map directly to Pipedrive Lead. The lead's status, source, and conversion log transfer to Pipedrive's Lead status and custom fields. The original lead_id is preserved in a custom field for audit. If the Lead has already been converted to a Contact in OneHash, we migrate the Contact portion to Pipedrive Person and leave the Lead record as a historical reference.

OneHash Contact records (with first_name, last_name, email, phone, organization linkage per ERPNext DocType) map to Pipedrive Person. The contact's organization linkage maps to the corresponding Pipedrive Organization via the OneHash Customer record. We resolve the organization reference before Person import so that the link is satisfied at insert time.

OneHash Customer records — organization-level entities with billing/shipping addresses — map to Pipedrive Organization. The organization's address fields migrate to Pipedrive's address structure. Organization is created before any Contact or Person import so that the lookup relationship is satisfied at the moment of Person insert.

OneHash Opportunities track deal stages, amounts, probability, and party information. These map directly to Pipedrive Deals with the stage name preserved via a stage-sequence map applied at migration time. The Opportunity party's link (Contact or Customer) maps to the corresponding Pipedrive Person and Organization. Stage probability migrates to Pipedrive's stage probability setting.

OneHash Quotations carry line items linked to Items, with tax templates and terms. Each Quotation maps to a Pipedrive Deal with the quotation items mapped to Pipedrive Products attached as Deal Products. The quotation-to-opportunity linkage is preserved as a custom field or note reference. Tax template information migrates to a custom field since Pipedrive Deals do not natively carry tax rates.

OneHash Item records (product/service definitions with pricing, stock data, and custom attributes) map to Pipedrive Products. Standard fields like name, item_code, description, and standard_rate migrate; custom Item fields map to Pipedrive custom fields on the Product object. If the customer uses OneHash Items for inventory tracking, stock data migrates as a custom field since Pipedrive Products are not inventory-tracked by default.

OneHash allows unlimited custom fields per DocType via ERPNext's Customize Form. These fields do not appear in standard API responses unless explicitly requested. We run a pre-migration discovery pass that introspects each DocType's custom field definitions via the API before mapping, ensuring no custom property is dropped during export. Custom fields then provision in Pipedrive via the Pipedrive API before data import begins.

OneHash Sales Orders reference both Customers and Items and carry delivery and billing status flags. We migrate Sales Order records as a custom Deal Activity type with status flags as custom fields. The order item rows are mapped field-by-field because OneHash allows custom Item fields that may not exist in the destination. Order-to-Customer linkage is preserved via the Organization lookup.

OneHash Employee records include designation, department, and salary structure. Pipedrive does not have a native Employee object. We migrate the org-chart relationship (designation and reporting structure) as Pipedrive User custom fields for administrative reference. HR-specific salary and compensation fields do not map to Pipedrive and are documented in the migration handoff for the customer's HR system team.

OneHash Projects carry Tasks, assignees, and time tracking. We migrate project metadata and task hierarchy as Pipedrive Deal Activities linked to the corresponding Deals. Open vs. completed status carries over; task-level comments map as notes attached to the activity. Time tracking data migrates to a custom field since Pipedrive Activities do not natively support time logs.