Migrate from Klipy CRM to Freshsales

Klipy Contacts migrate to Freshsales Contacts using email address as the dedupe key. We apply email-based deduplication before import, normalizing names to a consistent format and flagging potential duplicates for customer review. Klipy contact fields (name, email, phone, company affiliation) map to Freshsales standard Contact fields. Company affiliation from Klipy resolves to the Freshsales Account linked in the Account phase. Tags from Klipy transfer to Freshsales Contact Tags. Any AI-generated follow-up context stored in Klipy Notes migrates as Freshsales Notes linked to the Contact.

Klipy Companies map to Freshsales Accounts. We create Accounts before Contacts so the Account lookup is satisfied at Contact insert time. Domain normalization is applied for companies auto-created from email signatures, since Klipy extracts company name from email headers rather than domain matching. The Account's primary address, phone, and website migrate from Klipy's Company fields. If no Website is present in Klipy, we leave the Account Website field blank rather than inferring from email domain.

Klipy Deals migrate to Freshsales Deals. Each Deal's name, value, stage, creation date, and closing date transfer directly. The pipeline from Klipy maps to the Freshsales pipeline that the customer configures before migration — Freshsales allows adding and renaming stages where Klipy does not. We map the closest Klipy stage to the equivalent Freshsales stage by name order, and the customer adjusts stage mapping during scoping. Owner resolution uses email matching against Freshsales Users.

Klipy call activities migrate to Freshsales Tasks with subtype set to call. Call disposition, duration, and recording URL transfer to custom Task fields where supported. Activity timestamp preserves the original Klipy activity date so the contact timeline reflects the correct sequence of interactions. The Task links to the resolved Freshsales Contact via WhoId.

Klipy meeting activities migrate to Freshsales Events with start time, end time, location, and description preserved. Events link to the resolved Freshsales Contact or Account. Meeting attendees from Klipy transfer to Event participants in Freshsales where attendee data is present in the export. Timestamp ordering is preserved for timeline accuracy.

Klipy tags on Contacts and Deals migrate to Freshsales Tags. Tags used for segmentation map to Freshsales Contact Tags and Deal Tags. If the destination Freshsales account uses a different tagging taxonomy, we apply tag normalization during the transform phase and flag discrepancies for customer review. The customer chooses tag strategy during scoping.

Klipy Notes migrate to Freshsales Notes linked to the parent Contact or Deal. Note body, timestamp, and author preserve. AI-generated follow-up drafts from Klipy transfer as standard Freshsales Notes content. The source (AI draft vs manual entry) is noted in a custom field if the customer's Freshsales plan supports it.

Attachments linked to Deals or Activities in Klipy migrate to Freshsales Attachments via the Freshsales Attachments API endpoint. We verify attachment integrity post-migration and flag any files that exceed Freshsales size limits. If Klipy's export does not include binary attachment files (common with CSV-based exports), we document the missing files in the migration report and advise the customer to re-upload manually or via Freshsales file upload.