Migrate from Klipy CRM to Odoo CRM

Klipy Contacts are auto-created from Gmail/Microsoft email history, making email address the primary identifier. We use email as the dedupe key during Odoo import, normalize name fields to a consistent format, and apply deduplication to collapse any duplicates created by slight name variations across email threads. Odoo's res.partner model serves both companies and individuals; we set type=contact for person records. Klipy's linked Company association (via company name or domain) is resolved using Odoo's partner_id lookup on res.partner.

Klipy Companies are linked to Contacts via company name or domain matching. We import them as Odoo res.partner records with type=company before the Contact import so that the parent partner lookup is satisfied at the moment of Contact insert. Domain normalization is applied since Klipy auto-imports company names from email signatures, which may vary in format (example.com vs www.example.com). Odoo's commercial partner relationship automatically links child Contact records to the parent Company partner.

Klipy Deals are created from email threads and linked to Contacts and Companies. We preserve deal name, expected revenue (mapped to Odoo's planned_revenue), stage, and creation date. Klipy's deal value maps to Odoo's expected_revenue field. The pipeline is fixed in Klipy, so we map the existing stages verbatim to Odoo CRM stage values, or collapse to a compatible stage set if the destination pipeline has fewer stages.

Klipy has a single default pipeline with unmovable stages. We map this to a single Odoo CRM Pipeline (crm.team) if the customer uses one team, or split into multiple crm.team records if the customer manages separate business lines. Each Odoo crm.team gets its own stage configuration within the CRM module.

Klipy's pipeline stages cannot be customized. We map them verbatim to Odoo CRM stages. If Odoo's stage count differs from Klipy's, we collapse the Klipy stages into the closest matching Odoo stage values during scoping, subject to customer approval. Stage probabilities from Klipy are remapped to Odoo's probability field per stage.

Klipy captures multi-channel interactions across email, calls, LinkedIn, WhatsApp, and Telegram, each triggering AI follow-up drafting. We migrate the activity type, timestamp, and linked Contact or Deal reference. Channel-specific fields (call duration, message type) map to Odoo mail.activity fields. Full message content migrates as a Note (mail.message) attached to the parent record rather than as a structured activity field because Klipy's channel data does not map directly to Odoo's activity type taxonomy.

Klipy generates AI follow-up drafts after every email, call, LinkedIn, WhatsApp, and Telegram interaction. These drafts are stored as Notes in Klipy and linked to the parent Contact or Deal. We migrate the draft content, timestamp, and linked record reference as Odoo mail.message records with a note subtype. We preserve an indicator that the note originated as an AI draft so the customer can distinguish AI-generated content from manual notes in Odoo.

Manual Notes in Klipy migrate to Odoo mail.message records attached to the parent Contact, Company, or Deal (crm.lead). Note body migrates as plain text. Any rich formatting present in Klipy is converted to Odoo's markdown-compatible note format. Notes are imported after the parent record exists in Odoo to satisfy the res_id reference.

Klipy Tags are used to label Contacts and Deals for segmentation. We preserve tag names and reapply them to Odoo crm.tag records. Tag merging is applied if Klipy and Odoo use overlapping tag names with different casing or punctuation. Tags are linked to crm.lead via crm.tag.rel after both records exist.

Attachments linked to Deals or Activities are migrated as Odoo ir.attachment records linked to the parent crm.lead or res.partner via res_model and res_id. We verify attachment integrity post-migration and flag any files that exceed Odoo's attachment size limits (default 25MB per file, configurable). External file URLs from Klipy are downloaded and re-uploaded to Odoo's local storage unless the customer specifies a document management integration.

Klipy custom fields on Contacts are not publicly documented in a developer reference. During scoping, we probe Klipy's export capability to identify available custom field names and data types, then map them to Odoo custom res.partner fields (ir.model.fields with track_visibility enabled). Field type mapping converts Klipy types to Odoo field definitions (char, text, selection, many2one, etc.) and we flag any fields that cannot be typed directly in Odoo for customer decision.

Klipy custom fields on Deals map to Odoo crm.lead custom fields (x_ prefixed ir.model.fields). As with Contact custom fields, we detect available fields during scoping, map types to Odoo field definitions, and configure the fields in the destination Odoo database before Deal import begins. Stage-dependent fields are flagged if they reference values that only exist in Klipy's fixed stage set.

Klipy Owner records map to Odoo res.users. We resolve owners by email match against the Odoo destination User table. Any Klipy Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Deals and Contacts is resolved via res.users partner_id at migration time.

Klipy Workflows, automations, and sequences do not migrate. Klipy has no native email-sending capability, so outbound sequences are managed outside the platform. Odoo's automation framework (Studio automations, server actions, scheduled actions) uses different primitives and must be rebuilt. We deliver a written inventory of every active Klipy automation with its trigger, conditions, and actions, plus a recommendation for the Odoo equivalent. The customer's admin rebuilds these post-migration.