Migrate from Clientify to Pipedrive

Clientify Person records map directly to Pipedrive Person. Name, email, phone, and address fields migrate as standard Pipedrive Person fields. Custom properties on Person (picklist, date, numeric, text) map to Pipedrive custom fields, but picklist values in Pipedrive must be pre-created in the destination org before import or the insert fails for those records. We run a pre-flight schema sync to ensure all picklist values exist before migration begins.

Clientify Organization records map to Pipedrive Organization. Industry, size, address, and website fields migrate as standard fields. Organization is created before any Person import so that the Person-Organization link (owner_id on the organization) is satisfied at Person insert time. We use organization_name as the dedupe key to prevent duplicate Organizations during import.

Clientify Deal records map to Pipedrive Deal with title, value, stage, owner, and expected close date preserved. The Clientify pipeline_id maps to a Pipedrive Pipeline that we pre-create with stage names and ordering replicated from Clientify. Stage probability percentages migrate as editable integer values on Pipedrive's stage configuration.

Each Clientify pipeline with its ordered stages maps to a Pipedrive Pipeline with corresponding Stage records. Stage names, order index, and probability values transfer directly. We configure the pipeline and stages in Pipedrive before any Deal records are imported to ensure stage IDs are available for Deal inserts.

Clientify's Lead object (distinct from Person) requires a scoping decision: leads can migrate as Pipedrive Leads (separate object) or as Persons with a lead_status custom field. The decision depends on whether the team uses Pipedrive's Lead Inbox feature. We apply the chosen strategy during scoping, run the split as a transform before insert, and preserve lead source and score fields as custom fields on the destination object.

Clientify logged calls map to Pipedrive Activity records with type set to Call. Call duration, disposition, and timestamp migrate as activity fields. The activity is linked to the target Person or Deal via Pipedrive's deal_id and person_id fields, which we resolve at migration time by looking up the migrated record's Pipedrive ID from the source Clientify record ID stored in a custom field during the Persons and Deals import phase.

Clientify logged emails map to Pipedrive Activity records with type set to Email. Subject, body, and timestamp migrate as activity fields. Email attachments migrate as Pipedrive file attachments linked to the activity record. We resolve the person_id and deal_id references for each email activity using the ID mapping table built during Persons and Deals import.

Clientify meeting records map to Pipedrive Activity records with type set to Meeting. Meeting title, start time, end time, location, and attendees migrate as activity fields. Attendee resolution depends on whether the attendee emails match a migrated Person record; unmatched attendees are stored as a text list in a custom field for manual review.

Clientify task records map to Pipedrive Activity records with type set to Task. Task title, due date, status, and priority migrate directly. Completed status maps from Clientify's completion flag to Pipedrive's done field (0 or 1). Owner assignment resolves via email match against the migrated Users table.

Clientify custom fields on Person, Organization, and Deal objects map to Pipedrive custom fields of matching type. Text-to-text, number-to-number, and date-to-date mappings are direct. Picklist fields require pre-creation of the picklist values in Pipedrive before import. Multi-select picklists in Clientify map to Pipedrive multi-select fields. Any field-type mismatch is flagged during scoping and resolved with a type-cast or custom field recreation in Pipedrive before migration.

Clientify user records (name, email, role, active/inactive status) map to Pipedrive User records. We match by email address. Active status migrates as-is; inactive users are created as inactive Pipedrive Users so that historical owner assignments on Deals and Activities resolve correctly. Role and permission structures differ between platforms and require manual configuration in Pipedrive post-migration.

Clientify tags applied to Persons and Deals migrate as Pipedrive Tags. Tags are linked via the Person-Tag or Deal-Tag relationship tables in Pipedrive after the parent record is inserted. We extract all unique tag names from Clientify and create them in Pipedrive before importing relationship records.