Migrate from Klipy CRM to Twenty CRM

Klipy Contacts map directly to Twenty People records using email address as the primary dedupe key. Klipy auto-creates contacts from Gmail/Microsoft email threads, so the same person frequently appears with slight name variations (different casing, nicknames, or company affiliations). We apply email-based deduplication during extraction, normalize names to a consistent format, and flag potential duplicates for customer review before final import. Contact owner assignment maps to Twenty's workspace Member via email match.

Klipy Company records map to Twenty Company records. Domain-based normalization is applied since Klipy auto-populates company names from email sender domains during import. Company is created before People import so the People-Company relationship is satisfied at insert time. If a Klipy Contact has no explicit Company link, we optionally create a Company record from the Contact's domain for relationship completeness.

Klipy Deals map to Twenty Opportunity records. The deal name, value (amount), stage, and creation date migrate directly. Klipy's pipeline is fixed — we map the existing stage names verbatim to Twenty Opportunity stages and create a Sales Process in Twenty matching Klipy's stage sequence before migration begins. Closed-Won and Closed-Lost dates migrate as stage exit timestamps if present.

Klipy has a single default pipeline that cannot be customized. We create one Sales Process in Twenty with stage names and probabilities that mirror the Klipy source exactly. If Twenty's default stage set differs in count, we collapse or expand the stage list per the customer's confirmed stage mapping during scoping. This configuration is applied before any Opportunity records are imported.

Klipy captures Activities across email, calls, LinkedIn, WhatsApp, and Telegram channels. All activity types map to Twenty Task records, with the activity type stored in a custom field or the task body for traceability. Call duration and disposition migrate as custom fields on the Task. We preserve the original timestamp as ActivityDate so the activity timeline in Twenty reflects the correct sequence. Activity-to-Contact linking requires parent record resolution during import (WhoId lookup).

Klipy Notes store AI-generated follow-up drafts and manual annotations. We migrate note body content to Twenty Task body, preserving the original timestamp and linking to the related People or Opportunity record. AI draft metadata (e.g., originating channel, draft status) is stored in a custom note property or task custom field. The customer chooses whether to surface AI drafts as Tasks or as separate Comments during scoping.

Klipy Tags on Contacts and Deals migrate to Twenty Tags. Tag names are preserved verbatim, and we reapply them to the mapped People and Opportunity records. If Twenty uses a different tag taxonomy or scope (People-only vs. multi-object), we normalize tag names and confirm the target scope during mapping design.

Klipy's custom field schema is not publicly documented. During scoping, we run a schema discovery probe to enumerate available custom fields on Contacts and Deals. We map each discovered custom field to an equivalent Twenty custom field (created in Settings → Data Model before import). Field type mapping follows the detected Klipy type: text fields map to Twenty text, date fields to date pickers, numeric fields to number fields, and picklist fields to select fields.

Files attached to Klipy Deals or Activities migrate as Twenty attachments linked to the corresponding Opportunity or Task. We verify file integrity post-migration and flag any files exceeding Twenty's size limits. If Klipy attachment URLs are inaccessible after the customer closes their Klipy account, we advise exporting attachment binaries during the extraction phase before account deprovisioning.

Pipeline stages cannot be renamed or customized in Klipy — there is nothing to configure on the source side. We do not migrate stage configuration records. Instead, we design the equivalent stage configuration in Twenty before migration begins, using Klipy's existing stage names as the target. The customer reviews and approves the stage mapping during scoping.