Migrate from Klipy CRM to HighLevel

Klipy Contacts map directly to GoHighLevel Contacts using email address as the primary dedupe key. Because Klipy auto-creates Contacts from email thread history, the same email may appear with name variations across multiple imported threads. We apply email-based deduplication, normalize first and last name to a consistent format, and flag duplicate candidates for customer review before final import. Any Klipy custom fields on Contact are mapped to GoHighLevel Contact custom fields, which must be pre-created in the destination sub-account before import begins.

Klipy Company records map to GoHighLevel Company using domain or company name as the dedupe key. We create Companies before Contact import to satisfy the Contact-to-Company lookup relationship at the moment of Contact insert. Klipy auto-imports company names from email signatures and subject lines, so normalization is applied to reduce duplicates caused by inconsistent naming (e.g., 'Acme Corp', 'Acme Corporation', 'ACME' all map to a single GoHighLevel Company). Custom fields on Klipy Companies map to GoHighLevel Company custom fields.

Klipy Deals map to GoHighLevel Opportunities. Deal name, monetary value, creation date, and linked Contact and Company references migrate directly. The pipeline assignment in Klipy maps to a GoHighLevel Pipeline that we configure during the schema design phase. Since Klipy's pipeline stages are fixed and cannot be renamed, we map them verbatim to GoHighLevel stage names or, if the customer prefers, collapse them to a compatible stage set that better reflects their current sales process in GoHighLevel.

Klipy ships with a single default pipeline. We create a corresponding Pipeline in GoHighLevel during schema design. GoHighLevel supports multiple pipelines with independent stage sets, which is a significant upgrade from Klipy's single-pipeline model. The customer can optionally expand to multiple pipelines during migration if they have distinct lines of business or client segments that warrant separate pipelines.

Klipy's pipeline stages are fixed and non-customizable, so they map verbatim to GoHighLevel pipeline stages. We create GoHighLevel stages that match Klipy's stage names and probabilities exactly, then present the customer with the option to rename or reconfigure stages in GoHighLevel after migration since GoHighLevel allows this freely. This is one of the first items we confirm in scoping to avoid rework.

Klipy Activities span email, call, meeting, LinkedIn, WhatsApp, and Telegram interactions. We map call activities to GoHighLevel Tasks with TaskSubtype = Call and preserve call duration and disposition. Meeting activities map to GoHighLevel Calendar Events with start and end times. Email activities that are logged but not sent (Klipy drafts rather than sends) are stored as GoHighLevel Notes attached to the Contact. WhatsApp, LinkedIn, and Telegram interactions are mapped to GoHighLevel Tasks with a custom subtype field indicating the channel, since GoHighLevel does not have native LinkedIn or Telegram integration.

Klipy Tags on Contacts and Deals map to GoHighLevel Labels. Labels in GoHighLevel serve the same segmentation purpose as Tags in Klipy. We preserve the full tag name set and reapply them to the corresponding GoHighLevel Contact and Opportunity records. Tag merging is applied if the same logical tag appears with different naming conventions due to Klipy's auto-import behavior.

Klipy Notes, including AI-generated follow-up drafts, map to GoHighLevel Notes attached to the relevant Contact, Company, or Opportunity record. We preserve the original note body, creation timestamp, and linked record reference. If the note contains AI draft metadata, we store that context in a custom Note field or as a custom Contact field to preserve the drafting provenance after migration.

Klipy file attachments linked to Deals or Activities migrate as GoHighLevel Files attached to the corresponding Opportunity or Contact record. We verify attachment integrity post-migration and flag any files that exceed GoHighLevel's file size limits for the customer's review. Files are uploaded via the GoHighLevel API or direct storage attachment.

Klipy custom fields on Contacts, Deals, and Companies are mapped to GoHighLevel Contact custom fields and Opportunity custom fields respectively. Since Klipy's API surface is not publicly documented, we detect available custom fields during the scoping scan by probing the export path directly. GoHighLevel's custom field schema must be pre-created in the destination sub-account before import; field type mapping (text, number, date, picklist, checkbox) is applied based on detected values during scoping.