Migrate from Klipy CRM to Microsoft Dynamics 365 Sales

Klipy Contacts are auto-created from Gmail/Microsoft email history with email address as the primary identifier. We migrate them 1:1 to Dynamics 365 Contact using email address as the dedupe key. Name normalization is applied because auto-imported contacts may have slight variations (John Smith vs [email protected]) from thread-level capture. We run email-based deduplication during staging, flagging potential duplicates for customer review before final import. Any Klipy custom fields detected during scoping are mapped to typed Dynamics 365 Contact fields or custom fields created in the destination org.

Klipy Companies are linked to Contacts via company name or domain matching. We map them 1:1 to Dynamics 365 Account, creating the Account record before Contact import so that the parent AccountId Lookup is satisfied at insert time. Domain normalization is applied to the Website field since auto-imported company data may have inconsistent domain formats from email thread metadata. If the same company appears under multiple name variants in Klipy, we consolidate to the primary Account using a canonical name chosen during scoping.

Klipy Deals are created from email threads and linked to Contacts and Companies. We map them to Dynamics 365 Opportunity with deal name, estimated value, stage, and creation date preserved. The pipeline is fixed in Klipy — we map the existing stages verbatim to Dynamics 365 Opportunity stage values. If Klipy's stage count differs from the destination's default stage set, we add or collapse stages in Dynamics 365 to match the source count before migration begins. Owner resolution uses email-based User lookup against the destination org.

Klipy's pipeline stages cannot be renamed or extended. We map the existing stage names and probabilities verbatim to Dynamics 365 Opportunity Stage values and corresponding probability percentages. The Dynamics 365 stage set is pre-built in a Sandbox org to match the Klipy stage count and order, with stage names preserved exactly as they appear in Klipy. Stage-level security and sales process scoping are configured post-migration by the customer's admin if multiple sales processes are needed.

Klipy captures multi-channel Activities (email, calls, meetings, LinkedIn, WhatsApp, Telegram) that trigger AI follow-up drafting. We migrate activity type, timestamp, and linked Contact. Email activities map to Dynamics 365 EmailMessage records linked to Tasks on the Contact timeline. Calls map to Task with TaskSubtype=Call and CallDuration preserved in a custom field. Meetings map to Event with StartDateTime and EndDateTime preserved. LinkedIn, WhatsApp, and Telegram interactions map to Task records with a custom channel field because Dynamics 365 does not have native social channel objects. Full message content and attachment URLs migrate where the platform API supports them.

Klipy Notes store AI-generated follow-up drafts and manual annotations linked to Contacts or Deals. We migrate note content, timestamp, and linked Contact or Deal. AI draft metadata is preserved as a custom note property (ai_generated__c) in the destination so that the customer can identify AI-suggested content versus manually authored notes. Notes attach to Dynamics 365 Contact, Account, or Opportunity via the Regarding field. If the customer used Klipy's AI draft approval workflow, the note status (draft vs approved) is preserved in a custom field.

Klipy Tags label Contacts and Deals for segmentation. We preserve tag names and reapply them to destination records. Tag migration strategy is chosen during scoping: for sparse tag sets (under 50 unique tags), we use a text field on Contact with comma-separated values; for richer segmentation, we use a multi-select picklist. If the customer uses Microsoft Dynamics 365 Sales Enterprise or Premium, we can create a dedicated Tag entity with a many-to-many relationship to Contact and Opportunity via a junction table. Tag deduplication is applied during staging to merge tag variations.

Attachments linked to Deals or Activities in Klipy are migrated as file references or binary transfers to Dynamics 365. We verify attachment integrity post-migration and flag any files that exceed Dynamics 365 attachment size limits (currently 131,072 KB per file for annotations). If the destination org uses SharePoint for document management (common in Microsoft 365-integrated deployments), we migrate attachments to SharePoint document libraries linked via the Regarding field on the Opportunity or Contact. The customer confirms the preferred attachment storage strategy during scoping.