Migrate from Klipy CRM to monday CRM

Klipy Contacts are auto-created from Gmail and Microsoft email history, where email address is the primary identifier and duplicate records may exist if the same email appears with slight name variations across threads. We apply email-based deduplication, normalize names to a consistent format, and flag potential duplicates for customer review before final import. The resolved unique Contact maps 1:1 to a Monday.com Person record using email as the dedupe key. Any crm_company_link or company affiliation from Klipy becomes a Monday.com Person-Company association.

Klipy Companies are linked to Contacts via company name or domain matching. Monday.com Companies store business entity information separately from People. We map them as parent records before Contact import to preserve associations. Domain normalization is applied since auto-imported company names in Klipy may include formatting inconsistencies. The Monday.com Company is created first so that the Person-Company relationship is satisfied at the moment of Person insert.

Klipy Deals are created from email threads and linked to Contacts and Companies. We preserve deal name, deal value, stage, and creation date. The Klipy pipeline is fixed — we map its existing stages directly to the Monday.com pipeline stages in the CRM Board. If Monday.com has a different stage count, we collapse or split stages per the customer's direction during scoping. Deal value maps to a number column; the linked Contact and Company resolve to Monday.com Person and Company lookups at migration time.

Klipy Activities capture multi-channel interactions that trigger AI follow-up drafting. We migrate activity type, timestamp, and linked Contact as a Timeline or Updates entry in Monday.com. Full message content migrates where Klipy's export includes it. Activity channel (email, call, meeting, LinkedIn, WhatsApp, Telegram) is preserved as a tag or label in the Activity column so the context is visible in Monday.com without rebuilding the AI draft feature.

Klipy Tags label Contacts and Deals for segmentation. We preserve tag names and reapply them to the destination records as Monday.com Tags. Tag merging is applied if the destination already has identically named tags. The customer chooses whether tags map to Monday.com Labels on items or to a dedicated Tag column during scoping.

Klipy Notes store AI-generated follow-up drafts and manual annotations linked to Contacts or Deals. We migrate note content, timestamp, and linked Contact or Deal. AI draft metadata is preserved as a custom column property in Monday.com if the customer wants to distinguish AI-generated notes from manual entries post-migration.

Attachments linked to Deals or Activities are migrated via file URL or binary transfer. We verify attachment integrity post-migration and flag any files that exceed size limits in Monday.com (5GB per workspace on Standard and Pro tiers). Files are attached to the corresponding Item (Deal) or Person (Contact) in Monday.com.

Klipy Custom Fields exist on Contacts and Deals but the full schema is not publicly documented. We detect available custom fields during the scoping scan by probing Klipy's export mechanism, then map them to Monday.com typed columns (text, number, date, list, checkbox, etc.) based on the inferred field type. Field type guessing is noted in the mapping document for the customer to validate. Any fields that cannot be typed definitively are flagged for manual review before import.