Migrate from Nurture to Pipedrive

Nurture Company records map to Pipedrive Organization. The Company name field maps to Organization name. Website, phone, address, and industry fields map to their Pipedrive equivalents. We use Organization name as the dedupe key during import. Organization is imported first because Pipedrive Deals require an Organization link, and Pipedrive People require an Organization link when a company relationship exists.

Nurture Contact records map to Pipedrive Person. Name, email, phone, title, and address fields migrate to their Pipedrive equivalents. We resolve the Organization link by matching the Nurture Contact's parent Company name to the Pipedrive Organization name created in the prior step. If a Contact has no associated Company in Nurture, the Person is imported without an Organization link.

Nurture custom fields on Contacts migrate to Pipedrive Person custom fields. We handle type mapping: Nurture date pickers become Pipedrive date fields, Nurture number fields become Pipedrive number fields, Nurture text fields become Pipedrive text fields, and Nurture single-select or multi-select fields become Pipedrive dropdown or multi-select fields respectively.

Nurture custom fields on Companies migrate to Pipedrive Organization custom fields using the same type-mapping logic as Person custom fields. All Organization custom fields must be created in Pipedrive before the Organization import begins.

Nurture Deal records map to Pipedrive Deal. Deal name, value, expected close date, stage, and owner map to their Pipedrive equivalents. We resolve the Organization link by matching the Nurture Deal's associated Company name to the Pipedrive Organization name. The Deal owner maps via email lookup to the Pipedrive User. Nurture Deal stage names map to Pipedrive Stage names within the configured pipeline.

Nurture custom fields on Deals migrate to Pipedrive Deal custom fields. Pipedrive requires that all custom fields exist before Deals are imported. We create the custom fields during the schema setup phase and then map field values during the Deal import phase using the correct Pipedrive field API names.

Nurture pipeline stages migrate to Pipedrive Pipeline stages. If Nurture has a single pipeline with multiple stages, we create a matching Pipedrive Pipeline with stages named to mirror Nurture's stage labels. Stage probability weights from Nurture migrate to Pipedrive Stage probability values. If Nurture has multiple pipelines, we create multiple Pipedrive Pipelines and map each to its corresponding Deal set.

Nurture call activities map to Pipedrive Activity with type = call. Duration, disposition, and notes migrate to Pipedrive activity fields. The activity is linked to the corresponding Person and, if applicable, the related Deal. Activity timestamps migrate as the Pipedrive Activity due date, preserving the original date and time for timeline accuracy.

Nurture email activities map to Pipedrive Activity with type = email. Subject, body content, and direction (sent/received) migrate to Pipedrive activity fields. We link the activity to the corresponding Person record. Email content migrates as a text note attached to the activity. Pipedrive's email sync on Advanced and above plans can supplement imported emails with live two-way sync after cutover.

Nurture meeting activities map to Pipedrive Activity with type = meeting. Title, start time, end time, location, and attendees migrate to Pipedrive activity fields. The activity is linked to the corresponding Person and related Deal. Attendees without existing Pipedrive Person records are logged as text notes pending manual contact creation.

Nurture Task activities map to Pipedrive Activity with type = task. Title, due date, status, and assignment migrate to Pipedrive activity fields. The activity is linked to the corresponding Person and related Deal. Completed status migrates as done = true in Pipedrive.

Nurture owner references on Contacts, Companies, and Deals map to Pipedrive Users via email address matching. We extract every distinct owner email from the Nurture export and check for a matching User in the destination Pipedrive account. Any owner without a matching User goes to a reconciliation queue for the customer's admin to provision before Deal and Activity imports run, because Pipedrive requires a valid User reference on Deal owner_id.