Migrate from Klipy CRM to Nutshell

Klipy Contacts (auto-created from Gmail/Microsoft email history) map to Nutshell People records. Email address serves as the dedupe key and primary identifier. Because Klipy auto-creates contacts from email threads, the same person may appear as multiple contacts with slight name variations (for example, 'John Smith' vs 'John Smith'). We apply email-based deduplication during migration, normalizing the name field to a consistent format and flagging duplicates for customer review before final import. The primary contact record retains full name, email, phone, and any linked company affiliation.

Klipy Company records map to Nutshell Organization. Companies are imported as parent records before Contacts to satisfy the Organization lookup on each Person record. Domain normalization is applied to auto-imported company names derived from email sender domains — for example, 'acme inc.' and 'Acme Inc.' resolve to a single Organization record. If no company affiliation exists on the Klipy Contact, we create a placeholder Organization or leave the Person's organization field blank per the customer's scoping preference.

Klipy Deals (created from email threads and linked to Contacts and Companies) map to Nutshell Deals with deal name, value, stage, and creation date preserved. Klipy's fixed pipeline stages map verbatim to Nutshell Deal stages — we cannot rename or reorder stages on the Klipy side before export, so the stage values transfer as-is. If Nutshell's default stage set does not include a matching stage name, we map to the nearest equivalent and document the mapping in the field-level spec delivered before production migration.

Klipy's single default pipeline with its fixed stages maps to Nutshell's pipeline configuration. Nutshell supports multiple pipelines with custom stage sets, but since Klipy only has one pipeline, we map it to the primary Nutshell pipeline. The stage probability weights from Klipy transfer to Nutshell stage configuration as decimal values. If the customer has customized Nutshell's stage set before migration, we align the import to their existing configuration; otherwise, we use Nutshell's default stage set and document the mapping.

Klipy's pipeline stages cannot be renamed, reordered, or added, so we map them verbatim to Nutshell pipeline stages. There is nothing to configure on the Klipy side — we take the existing stage names and values as the source of truth. In Nutshell, we configure the matching stage values before import so that deal stage assignments land correctly on the first import pass. Stage probability percentages transfer from Klipy to Nutshell's stage probability field with rounding to the nearest allowed integer.

Klipy Activities (emails, calls, meetings, LinkedIn, WhatsApp, Telegram interactions) map to Nutshell Activity records. Each activity type maps to its equivalent Nutshell Activity subtype: calls become Tasks with a Call disposition note, meetings become Tasks with a Meeting subtype and duration, and email interactions become Activities linked to the Person record. The original timestamp, channel type, and linked Contact are preserved. Full message content migrates as Activity body text. Note that Klipy's multi-channel capture includes LinkedIn, WhatsApp, and Telegram — these are stored in Nutshell as plain Activity records without native channel icons, which the customer accepts during scoping.

Klipy Notes store AI-generated follow-up drafts and manual annotations linked to Contacts or Deals. We migrate note content, timestamp, and the linked Person or Deal record. AI draft metadata (indicating the draft was generated by Klipy's AI from conversation content) is preserved as a Note body prefix or a custom note flag, depending on Nutshell's field availability at the time of migration. The customer's admin reviews notes post-migration to confirm the formatting meets their needs.

Klipy Tags used to label Contacts and Deals for segmentation map to Nutshell Tags. Tag names transfer directly. If the customer used a tagging convention in Klipy that conflicts with Nutshell's tag naming limits, we apply a normalization rule (truncation at 50 characters, removal of special characters) and document any renames in the field-level spec. Tag merging recommendations are delivered if the customer's Klipy tagging was inconsistent.

Attachments linked to Deals or Activities in Klipy migrate as Files in Nutshell. We transfer files via URL reference or binary transfer depending on the export mechanism confirmed during scoping. Post-migration we verify attachment integrity against the source file count and flag any files that exceed Nutshell's size limits for manual handling. If Klipy's export path is CSV-only and does not include attachment binary data, we flag this gap in the scoping report and provide a manual alternative for the customer's team.