Migrate from Nutshell to Pipedrive

Nutshell People records map directly to Pipedrive Person. Standard fields (name, email, phone, address) map to Pipedrive's name, email_id, phone, and address fields. We extract all per-Person custom fields and create matching Pipedrive custom fields before migration. The Person's Organization lookup is resolved at load time using the Nutshell Company-to-Organization mapping.

Nutshell Company records map to Pipedrive Organization. Company-level custom fields migrate to Organization custom fields. The Organization record must be created before the related Person records so that the OrganizationId lookup is satisfied at Person insert time. We use the Company domain as a dedupe key during Organization import.

Nutshell's separate Leads object requires a migration decision: map to Pipedrive Person with the Lead checkbox enabled, or keep as a separate Pipedrive Lead object if the customer uses a distinct lead qualification workflow. We make this choice during scoping based on the customer's Nutshell pipeline configuration and the maturity of their lead management process. The original Nutshell Lead status and any lead score values migrate to custom fields on the destination record.

Nutshell Activities (calls, emails, meetings, tasks) tied to People or Companies map to Pipedrive Activity records. We use the Nutshell activity type field to set the Pipedrive activity_type (call, email, meeting, task) and sub_type fields accordingly. Activity timestamps and subject lines preserve the original Nutshell record for timeline ordering. Each Activity is linked to the resolved Person (and Organization) record via the PersonId field.

Nutshell pipeline definitions extract as stage name, stage order, and win/loss status. We create matching Pipedrive Pipelines before Deal migration begins, using the same stage names and ordering. Stage probability percentages are mapped from Nutshell to Pipedrive stage probability fields. If Nutshell has multiple pipelines, each becomes a separate Pipedrive Pipeline that we configure with its own stages and Deal source filters.

Stage-level configuration including stage name, position, and probability migrates to Pipedrive stage definitions within each Pipeline. Automation triggers attached to specific Nutshell stages are flagged in the documentation deliverable as Pipedrive automation candidates; they do not migrate as active rules.

We enumerate all Nutshell custom field definitions across People, Companies, and Leads before migration. Each custom field is matched to a Pipedrive custom field with the equivalent type (text, number, date, dropdown, checkbox, currency). Pipedrive requires custom fields to be created before data import; we provision them in the destination account before the first record loads.

Nutshell tags used for categorizing People and Companies export as a flat list per record. We map them to Pipedrive Person or Organization tags depending on the object they were attached to in Nutshell. Tag hierarchy (if any) flattens during transfer. We preserve the original tag strings and let the customer decide on tag consolidation after migration.

Nutshell Users who serve as record owners appear across People, Companies, Leads, and Activities. We map Nutshell users to Pipedrive Users by email match. Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before record import resumes. Active Nutshell users without Pipedrive access block the OwnerId assignment on Deals.

Nutshell's API exposes attachment metadata (filename, URL reference) but does not return binary file blobs directly. We export attachment filenames and the original URLs for reference but cannot automatically download and re-upload files. Customers should download attachments directly from Nutshell and re-upload manually to Pipedrive or a linked cloud storage integration post-migration.