Migrate from Klipy CRM to Zoho CRM

Klipy Contacts migrate to Zoho Contacts using email address as the dedupe key. The primary identifier in Klipy is the email address (Contacts are auto-created from email history), so we apply email-based deduplication before Zoho import, normalizing names to a consistent format and flagging potential duplicates for customer review. Klipy custom fields on Contacts are detected during scoping (since Klipy's field schema is not publicly documented) and mapped to Zoho custom fields pre-created in the destination org.

Klipy Companies map to Zoho Accounts. Since Klipy auto-creates Companies from email domain parsing during its contact import, domain normalization is applied during mapping. We create the Account record before importing linked Contacts so that the Account Lookup is satisfied at the moment of Contact insert. Account Phone, Website, Industry, and Address fields map from the corresponding Klipy Company fields.

Klipy Deals migrate to Zoho Deals. Each Klipy Deal carries a deal name, value, stage, and creation date linked to a Contact and Company. We map Klipy's fixed pipeline stages verbatim into the destination Zoho pipeline stage set, collapsing or expanding stage names as needed if the customer's chosen Zoho pipeline has a different stage count. Deal value and expected close date migrate to Zoho Amount and Closing Date fields. Note: Klipy Deals are created from email threads and may not have the same structured product-line association as Zoho's multi-product Deal model.

Klipy ships a single default pipeline with fixed stages that users cannot rename or extend. We create a Zoho Pipeline matching the customer's preferred stage names, map Klipy's existing stages to the closest Zoho equivalents, and document any stage collapse or expansion in the mapping specification. If Klipy's stages cannot be replicated exactly in Zoho due to a different stage count, we confirm the target stage set with the customer before migration runs.

Klipy Pipeline Stages are fixed and cannot be customized, so there is no source-stage configuration to migrate. We treat this as a configuration step on the Zoho side: we configure the Zoho pipeline stage set to best match the existing Klipy stage sequence and probabilities, using Zoho's Stage Probability field to preserve the relative weighting of each stage.

Klipy Activities capture emails, calls, meetings, and LinkedIn, WhatsApp, and Telegram messages that trigger AI follow-up drafting. We migrate activity type, timestamp, and linked Contact to Zoho Task (for calls, emails, and tasks) or Event (for meetings). Full message content migrates to Zoho Notes attached to the Activity record. The original channel type (email, call, meeting, WhatsApp) is preserved in a custom Klipy_Channel__c field on the Zoho Activity record.

Klipy Tags are used to label Contacts and Deals for segmentation. We preserve tag names and reapply them as Zoho Tags on the migrated Contact and Deal records. Tag merging is applied if the destination Zoho instance uses a different naming convention, confirmed during the scoping review with the customer's admin.

Klipy Notes store AI-generated follow-up drafts and manual annotations attached to Contacts and Deals. We migrate note content, timestamp, and the linked Contact or Deal lookup. AI draft metadata (indicating the note was generated by Klipy's AI rather than manually authored) is preserved as a custom note property Klipy_AI_Draft__c in Zoho so the customer's team can review AI-generated content separately from manual entries.

Attachments linked to Deals or Activities in Klipy migrate to Zoho Attachments via file URL or binary transfer. We verify attachment integrity post-migration and flag any files that exceed Zoho's attachment size limit (the lesser of the Zoho tier limit or 25 MB per file). Attachments exceeding the limit are listed in the reconciliation report for manual handling.

Klipy custom fields exist on Contacts and Deals but the full schema is not publicly documented. During the scoping scan, we probe Klipy directly to detect available custom fields and their data types, then pre-create matching custom fields in Zoho before migration begins. Field type mapping is inferred from Klipy's export format: text exports map to Zoho varchar fields, number exports to Zoho integer or decimal, date exports to Zoho date fields, and checkbox exports to Zoho boolean.

Klipy Owner references (users assigned to Contacts, Companies, Deals, and Activities) map to Zoho User records by email match. We extract every distinct owner email from the Klipy export and match against Zoho User email addresses. Any Klipy owner without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before the migration proceeds, because Zoho User lookups are required on standard objects.