Migrate from Klipy CRM to Pipedrive

Klipy Contacts are auto-created from Gmail and Microsoft email sync, making email address the primary identifier. We use email address as the dedupe key during Pipedrive import, normalizing to lowercase and stripping display name variations that occur when the same contact appears across threads with different name formats. Any duplicate candidates are flagged for customer review before final import. First name, last name, phone, and company affiliation migrate directly.

Klipy Companies are linked to Contacts via company name or domain matching. We create Pipedrive Organizations first as parent records, then link Contacts during import so that the Organization lookup is satisfied at insert time. Domain normalization is applied to prevent split records (e.g., 'acme.com' vs 'www.acme.com' vs 'http://acme.com') from creating duplicate Organizations in Pipedrive.

Klipy Deals are created from email threads and linked to Contacts and Companies. We preserve deal name, value (amount), stage, and creation timestamp. The pipeline is fixed in Klipy; we map the existing stages verbatim to Pipedrive pipeline stages or collapse them into a compatible Pipedrive stage set if the stage counts differ between platforms. We flag any stage mapping decisions for customer confirmation before migration.

Klipy ships with a single default pipeline with hardcoded stages. We create a Pipedrive Pipeline with stages mapped 1:1 from Klipy's stage names. If the customer needs multiple pipelines in Pipedrive (e.g., separate sales motions per product line), we set up additional Pipedrive pipelines during the schema configuration phase and distribute Klipy deals by a customer-defined attribute (e.g., tag or deal value range).

Klipy captures emails, calls, meetings, and LinkedIn, WhatsApp, and Telegram messages as Activities linked to Contacts. We migrate Activity type, timestamp, duration (for calls), and linked Contact. In Pipedrive, email activities become email type; call activities become call type; meetings become meeting type; LinkedIn, WhatsApp, and Telegram interactions become task type with the channel noted in the description field. Full message content migrates where supported by Pipedrive's schema.

Klipy Notes store AI-generated follow-up drafts and manual annotations linked to Contacts and Deals. We migrate note content, timestamp, and the linked Contact or Deal reference. AI draft metadata (e.g., the conversation source that triggered the draft) is preserved in the note body or in a custom field on the Note activity in Pipedrive for audit and context.

Tags are used in Klipy to label Contacts and Deals for segmentation. We preserve tag names and reapply them to Pipedrive records at migration time. Tag naming conventions are normalized to avoid conflicts with Pipedrive's tag format. If the customer uses overlapping or inconsistent tag names in Klipy, we propose a merge map during scoping and confirm before applying.

Attachments linked to Deals or Activities in Klipy are transferred via file URL retrieval or binary transfer to Pipedrive. We verify attachment integrity post-migration and flag any files that exceed Pipedrive's size limits or unsupported file type restrictions. Attachments that cannot migrate directly are flagged with the source URL so the customer's admin can re-upload manually.

Klipy supports custom fields on Contacts and Deals, but the full custom field schema is not publicly documented. We detect available custom fields during the scoping scan (via CSV export, direct platform probe, or customer-supplied screenshot of the Klipy field list), map each to a Pipedrive custom field of the matching type (text, number, date, dropdown, checkbox), and apply field values during the record import phase. Field type mapping is confirmed during scoping because no automated type detection is available.

Klipy Owner records (users who own Contacts, Companies, and Deals) map to Pipedrive Users. We resolve by email match. Any Klipy Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId is a required reference on Deals and many Activity records in Pipedrive.