Migrate from Klipy CRM to Salesforce Sales Cloud

Klipy Contacts are auto-created from email threads with name, email address, and linked Company. We apply email-based deduplication during extraction, normalizing display names to FirstName/LastName splits and flagging records where the same email appears with conflicting names. Qualified contacts (those linked to an active Deal or a named Company) map to Salesforce Contact attached to an Account. Unqualified contacts with no deal history map to Salesforce Lead. The original Klipy contact creation date and any AI follow-up context migrate as custom fields for audit.

Klipy Companies are linked to Contacts via company name or domain matching from email auto-import. We normalize company domains (stripping mail., smtp., or mailtrap. subdomains) to the Website field on Salesforce Account and use domain as the dedupe key during import. Account is created before Contact import so that the AccountId lookup is resolved at the moment of Contact insert. Where Klipy records a company without a domain, we use the company name as Account Name with a manual review flag.

Klipy Deals are created from email threads and linked to a Contact and Company. We map deal name to Opportunity Name, deal value to Amount, and deal creation date to CloseDate. The Contact-to-ContactId lookup resolves after Contact import. Deal stage maps to Salesforce StageName using Klipy's fixed stage set verbatim since no stage customization exists in Klipy. If the destination Salesforce org has fewer stages than Klipy, we collapse using a customer-approved stage mapping table created during scoping.

Klipy has one default pipeline with fixed stages. We map this to a single Salesforce Record Type on Opportunity and a corresponding Sales Process. Stage probability values from Klipy migrate to Salesforce StageProbability percentages. Because Klipy's pipeline cannot be customized, there is no multi-pipeline complexity to resolve; the Salesforce destination receives one pipeline by default.

Klipy Activities capture multi-channel interactions that trigger AI follow-up drafting. We map each channel to the closest Salesforce equivalent: email activities to Salesforce EmailMessage linked to Task; calls to Task with TaskSubtype=Call; calendar meetings to Event; LinkedIn/WhatsApp/Telegram interactions to Task with a custom channel field. Activity timestamps and linked Contact resolve to Salesforce WhoId during migration. Full message content migrates as the Task or EmailMessage body. Because Klipy does not send email natively, the email activity records are inbound captures only.

Klipy's AI-generated follow-up drafts after each conversation are stored as Notes in Klipy with a reference to the linked Contact or Deal. We migrate these as Salesforce Note records with a custom field ai_draft__c set to true, preserving the draft content and timestamp. The Note is linked to the parent Contact or Opportunity via ContentDocumentLink. This metadata is important for teams that want to review AI draft history in Salesforce even though Salesforce does not natively generate these drafts.

Klipy Tags label Contacts and Deals for segmentation. Tags used for contact categorization migrate to a Salesforce multi-select picklist on Contact. Tags used for deal categorization migrate to a multi-select picklist on Opportunity. The customer chooses the target field during scoping. If the destination already uses Salesforce Topics for content classification, we offer Topic mapping as an alternative.

Files attached to Deals or Activities in Klipy migrate as Salesforce ContentDocument records via ContentVersion binary transfer. We verify file integrity with a hash comparison post-upload and flag any files that exceed the 25 MB Salesforce attachment limit. The ContentDocumentLink ties the file to the parent Contact, Account, or Opportunity.

Klipy Owner records (the user assigned to a Contact, Deal, or Activity) map to Salesforce User by email match. Any Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before the production migration phase begins. OwnerId is a required field on most Salesforce standard objects, so this step gates the record import.

Klipy supports custom fields on Contacts and Deals but the full schema is not publicly documented. During the scoping scan, we probe the Klipy export for any non-standard field names and map them to Salesforce custom fields (__c suffix) of the closest matching type. Field type transformation (date formats, picklist values, boolean flags) is applied during the staging transform. Custom field schema is deployed to Salesforce Sandbox before data migration runs.

Klipy's Pipeline Stages cannot be configured, renamed, or added. We map each Klipy stage name directly to a Salesforce Opportunity StageName value. Stage order is preserved. If the destination Salesforce org requires a probability percentage per stage, we use a customer-approved probability mapping created during scoping. No stage configurations on the Klipy side need to be preserved because there is nothing to configure.

Klipy call logs capture duration and disposition for calls made through its integration layer. We migrate these to Salesforce Task with TaskSubtype=Call. Call duration migrates to CallDurationInSeconds. Disposition text migrates to a custom Call_Disposition__c field. Activity timeline ordering is preserved by setting ActivityDate to the original Klipy timestamp.