Migrate from Clarify CRM to Pipedrive

Clarify Contact records map to Pipedrive Person (people) records. Standard fields (name, email, phone, job title) transfer directly. Clarify's autonomous AI context fields (auto-enriched company details, conversation-derived properties) are flagged during scoping — we present a list to the customer and they decide whether to include or exclude each AI-generated property before import. The AI-flagged fields are noted in the migration manifest so the customer understands what came from autonomous population versus manual entry. Clarify has no separate Lead object; all prospects exist as Contacts with lifecycle-stage properties, which map as-is to Pipedrive People.

Clarify Company records map to Pipedrive Organization records. The domain-based enrichment that Clarify's AI populates is flagged similarly to Contact AI fields — we present the field list and the customer chooses which autonomous properties to retain. Website, industry, employee count, and address fields migrate directly where present. Clarify's company domain becomes the Organization's Website field and serves as a dedupe key during import.

Clarify Deal records map to Pipedrive Deals with value, stage, and close date preserved. Clarify's autonomous agents update deal fields automatically — those updated values transfer but are flagged in the migration manifest so the customer can verify accuracy. Pipedrive's Deal record type does not distinguish between product lines; if Clarify uses deal-level custom fields for product categorization, those migrate as Pipedrive custom fields on the Deal object.

Clarify pipeline stages map directly to Pipedrive pipeline stages in sequence order. We capture the full stage name, position, and probability (if set in Clarify) and create matching Pipedrive stages before Deal import. If Clarify uses multiple pipelines, we create corresponding Pipedrive pipelines and map Deals by pipeline assignment. Stage probabilities transfer as decimal values and round to Pipedrive's integer-percentage format.

Clarify call records map to Pipedrive Activity records with the Call subtype flag set. Duration, call outcome, and any disposition data transfer to custom activity fields in Pipedrive. The activity timestamp preserves the original Clarify date so the timeline in Pipedrive reflects the correct sequence.

Clarify email engagements map to Pipedrive Activities. The email content attaches as a note body within the activity record, and the activity timestamp preserves the original send date. Pipedrive's activity timeline displays these in chronological order alongside other activity types.

Clarify meeting activities map to Pipedrive Activity records. Meeting title, date, and attendee information transfer. Pipedrive does not have a native meeting object separate from activities, so meeting records land as activity entries with the meeting title and date preserved.

Clarify's AI-generated meeting summaries are stored as enriched note content attached to activity records, not as first-class structured fields. We export these summaries and attach them as notes to the corresponding Person or Deal in Pipedrive. The summary content transfers as plain text or rich text depending on the format exported from Clarify. The customer should review summaries for accuracy since Clarify's autonomous AI may have introduced hallucinations into the summary text.

Clarify tag-based labeling on records migrates to Pipedrive Labels, which apply to both People and Organizations. Tag assignments per record transfer as Pipedrive Label selections on the corresponding record. Clarify's multi-tag-per-record model maps directly to Pipedrive's label system.

Clarify custom fields on Contacts, Companies, and Deals map to Pipedrive custom fields on the equivalent objects. We validate field types during scoping: multi-select fields in Clarify map to Pipedrive multi-select fields, date fields map to date fields, currency fields map to currency fields. Pipedrive supports custom fields from the Lite plan onward. Any Clarify custom field type that Pipedrive does not support (e.g., complex relational fields) is flagged during scoping for the customer to decide whether to flatten or omit.