Migrate from Zurple to Pipedrive

Zurple Contact maps directly to Pipedrive Person. Name, email, phone, and address fields transfer as standard fields. Any custom properties on the Zurple Contact become Pipedrive custom person fields created via the Pipedrive personFields API endpoint before migration. Primary company link maps to Pipedrive OrganizationId.

Zurple's early-stage leads (before conversion to Contact) map to Pipedrive's Lead object. Pipedrive Leads inherit all custom dealFields, so any Zurple lead-specific custom properties must be created as deal fields in Pipedrive before migration runs. Unqualified leads can remain as Pipedrive Leads rather than converting to Persons immediately.

Zurple Company maps to Pipedrive Organization. Company name, domain, industry, and employee count transfer as standard fields. Custom properties on the Zurple Company become Pipedrive custom organization fields created via the Pipedrive organizationFields API endpoint. Multiple contacts per company in Zurple link to the same Organization in Pipedrive via Person-Organization relationships.

Zurple Deal maps directly to Pipedrive Deal. Deal name, value, stage, expected close date, and owner transfer as standard fields. Each Zurple deal pipeline maps to a Pipedrive Pipeline created via the Pipedrive pipelines API. Deal stage names map value-by-value to Pipedrive stage names within each pipeline.

Zurple pipelines become Pipedrive Pipelines. Each pipeline requires creation in Pipedrive via the pipelines API before deals can be assigned to it. Pipeline visibility settings and stage probability weights must be configured in Pipedrive's pipeline management UI or via API after migration. Multiple pipelines in Zurple map to multiple Pipedrive pipelines, which can be assigned per user or globally.

Zurple pipeline stage names map to Pipedrive stage names via explicit value mapping. Stage order, probability percentages, and forecast category settings in Pipedrive are configured per pipeline after migration. Stage-entered timestamps from Zurple can be preserved as custom datetime fields on the Pipedrive Deal if historical stage-timing analysis is needed.

Zurple engagement activities (calls, emails, meetings) map to Pipedrive Activities. Activity type, subject, due date, and owner transfer as standard fields. Each activity links to the related Person and/or Deal via Pipedrive's activity_links API. Original timestamps and notes content preserve as-is. Attendees from Zurple meetings map to Person references in the Pipedrive Activity.

Zurple notes on any record map to Pipedrive Notes attached to the corresponding Person, Organization, or Deal. Rich text content in Zurple notes converts to plain text in Pipedrive Notes. Notes created by specific users link to the Pipedrive user matched by email. Embedded file attachments in Zurple notes are downloaded and re-uploaded as Pipedrive File attachments linked to the parent record.

Zurple custom properties on any object become Pipedrive custom fields. For Contacts → create via personFields; Companies → organizationFields; Deals → dealFields. Pipedrive assigns a 40-character hash as the field key — this is referenced in subsequent API calls. Custom field options (pick-list values) map value-by-value. Fields are created in Pipedrive before data migration begins to avoid validation errors on write.

Zurple user records resolve to Pipedrive users matched by email address. Active Pipedrive users must exist before migration runs. Unmatched Zurple owners are flagged in a pre-migration report; their records can be assigned to a fallback Pipedrive user or left unassigned pending user creation. Pipedrive user visibility groups do not migrate and must be configured post-migration.

Files attached to Zurple contacts, companies, or deals are downloaded from Zurple's storage and uploaded to Pipedrive's file management. Files attach to the corresponding Person, Organization, or Deal via Pipedrive's files API. File size limits apply — Pipedrive handles files up to 50MB by default on most plans. We preserve the original filename and any description stored in Zurple.

Zurple automated nurture sequences and workflow logic do not have a direct equivalent in Pipedrive and cannot be exported as structured automation rules. We export the sequence step definitions (trigger conditions, email content, timing, and branching logic) as a human-readable PDF document that your Pipedrive admin can use to rebuild equivalent automations in Pipedrive's Automation and Sequences tools.