Migrate from Pipedrive to Nutshell

Pipedrive Person records map directly to Nutshell Person records. Name, email address, phone, and address fields migrate by field-name match. Each Person retains its linked Organization relationship as a People-Company association in Nutshell. We resolve Organization links before Person import so that the Company lookup is satisfied at insert time. Duplicate detection runs on email address during import to prevent duplicate Person records in Nutshell.

Pipedrive Organization records map to Nutshell Company records. The organization name becomes the Company name, domain is stored as a text field, and custom fields migrate by label match. Organization address fields map to Company address. We preserve the count of linked Persons on each Organization as a custom field org_person_count__c in Nutshell for reporting purposes.

Pipedrive Deal records map to Nutshell Deal records with a direct stage-name match. Pipedrive deal monetary value (formatted as an integer in cents) converts to Nutshell's decimal value field. Expected close date, loss reason, and won reason custom properties migrate to matching Nutshell custom fields. Each Deal retains its linked Person (stored as the primary contact on the Nutshell Deal) and Organization references.

Pipedrive Leads are a separate pool from Deals with identical custom field schemas. Nutshell has no separate Lead object. We apply a split rule during scoping: Leads with no associated pipeline activity are imported as Nutshell Person records; Leads with active deal history are imported as Nutshell Deals with the Person fields populated. The original Pipedrive lead_status and leadgrade fields are preserved as custom fields on the destination record for audit and reporting.

Pipedrive Activities (calls, meetings, tasks, notes) map to Nutshell Activities by type. Call activities set the Nutshell Activity type to Phone; meeting activities set type to Meeting; tasks set type to Task; notes with attachments migrate as Nutshell notes. Activity due dates, assignment to Person or Deal, and owner assignments transfer directly. The Pipedrive note body migrates as the Nutshell Activity description text.

Pipedrive Products (standalone items with SKU, pricing, and unit info) map to Nutshell Products if the product catalog is used for quoting or price lists. If products are used primarily as deal-line metadata rather than for a formal product catalog, we map product name, quantity, and price to Nutshell custom fields on the Deal record, which preserves the line-item context without requiring Nutshell Enterprise API access.

Pipedrive assigns each custom field a 40-character hash key unique to the source account. We read the hash-to-label mapping from the Pipedrive account, resolve all field labels, match by name and data type to existing Nutshell custom fields, and create any missing Nutshell fields before import. Text, number, date, dropdown, checkbox, and user-lookup field types map to equivalent Nutshell field types. The mapping prevents data from landing in wrong columns or being silently dropped due to key mismatch.

Pipedrive Pipelines and their Stages map to Nutshell Pipeline and Stage configurations. Stage names and position order transfer directly; probability percentages round to nearest integer per Nutshell requirements. If the destination Nutshell account already has pipelines configured, we match by stage name and append new stages to the existing pipeline rather than creating duplicates.

Pipedrive Tags are string labels applied to Persons, Organizations, Deals, and Products. We extract all tag strings, deduplicate the set, and apply matching tags to the corresponding Nutshell records by name. Nutshell Tags are a flat namespace per record type, so multi-object tags (a tag applied to both a Person and a Deal in Pipedrive) are stored as separate Tag records in Nutshell under each object.

Pipedrive Users and Deal Owners are referenced by user_id and email in the API. We match by email address to existing Nutshell Users. Any Pipedrive Owner without a matching Nutshell User is flagged in the pre-flight report and held in a reconciliation queue until the customer's Nutshell admin provisions the corresponding user account. Owner assignments on Deals and Activities resolve at migration time once the User lookup table is confirmed.