Migrate from Pipz to Pipedrive

Pipz Contacts map directly to Pipedrive Persons. We preserve email, name, phone, custom properties, CEI score (as a custom numeric field), tags (as labels), and owner assignments. The primary email address serves as the dedupe key. Pipz's lifecycle stage values migrate as a custom multi-select picklist field so the customer's admin can rebuild segmentation logic in Pipedrive.

Pipz Companies map directly to Pipedrive Organizations. The organization domain and industry values migrate to standard fields. We preserve the relationship graph by resolving the Organization ID before importing Persons, ensuring that every Person record is linked to its parent Organization at insert time.

Pipz Deals map to Pipedrive Deals with deal name, value, currency, owner, expected close date, and stage preserved. The critical dependency is pipeline resolution: Pipz organizes pipeline stages differently by solution tier, so we identify the active pipeline structure during scoping and pre-create matching Pipedrive pipelines and stages before Deal import begins.

Pipz pipeline stages map to Pipedrive stage values within the corresponding pipeline. Stage ordering and probability percentages transfer directly. Custom stage properties and automation triggers tied to stages in Pipz do not migrate; we document the stage logic in a written stage-mapping reference for the customer's admin to configure in Pipedrive's visual pipeline editor.

Pipz Activities capture email engagement events, page views, live chat conversations, and automation-triggered events. We map these to Pipedrive Activity records with the original timestamp preserved, the activity type set (email_open, link_click, page_view, chat), and the Person or Organization linked via the activity's target_id. Note that Pipedrive Activities are calls, meetings, tasks, and emails as first-class types, so behavioral events from Pipz become notes-attached-to-activities to preserve the event history without creating orphaned records.

Pipz email campaigns include metadata (name, subject, send date, status) and performance metrics (opens, clicks, unsubscribes). We map campaign records as Activity records linked to the target Persons, with campaign name in the activity subject and performance metrics stored in custom fields. Segment membership associated with each campaign is preserved as labels on the Person records.

Pipz Smart Segments use demographic, tag-based, and behavioral rules. We transfer the segment definition logic as a written document specifying the conditions, operators, and values for each segment. Pipedrive's saved filters replicate the outcome of segment-based views, but the underlying behavioral rules require manual rebuild in Pipedrive's filter builder.

Pipz tags apply across contacts, companies, deals, and campaigns as a flexible labeling mechanism. We map all tags to Pipedrive Labels, preserving the full tag vocabulary and all associations. Pipedrive Labels are entity-scoped (Person, Organization, Deal) and available from the Essential plan onward.

Pipz custom fields on contacts, companies, and deals are fully supported with type-level mapping to Pipedrive field types. We extract the full custom field definition including field type, options list, and required status. Custom fields must be pre-created in Pipedrive before the import phase begins. Pipedrive supports text, number, date, phone, email, address, multi-select picklist, and organization link field types.

Pipz Users map to Pipedrive Users by email match. Owner assignments on Contacts, Companies, Deals, and Activities resolve to the corresponding Pipedrive User ID at migration time. Pipz includes unlimited team members at no per-seat cost, so teams with large Pipz user rosters should verify that their Pipedrive plan covers the user count before migration scope is finalized.

The Customer Engagement Index is a Pipz-proprietary behavioral score with no direct Pipedrive equivalent. We extract the raw CEI value for each Contact and store it as a custom numeric field cei_score__c on the Person record. Engagement event data (login timestamps, in-app actions, email engagement) is preserved as Activity records with the original event timestamps. The customer's admin can use cei_score__c to build Pipedrive custom reports or trigger manual segmentation.