Migrate from Devi to Odoo CRM

Devi's core object appears to be social media high-intent leads detected from LinkedIn, Twitter, or other platforms. We map these to Odoo crm.lead with type = lead (not opportunity). The source lead score or intent signal maps to a custom float field intent_score__c if the customer wants to preserve it. Odoo's crm.lead uses stage_id for pipeline state and team_id for team assignment. We require the customer to confirm the exact source field names and data types during discovery.

Devi's social listening likely captures person-level data (name, email, LinkedIn URL, company) attached to a lead signal. We map these to Odoo res.partner with partner_type = contact. The company association maps to a parent partner record (company = contact's employer). Odoo res.partner is a unified Contact/Account model so we create the employer as a company-type partner and link the contact as a child.

G2 reviews mention AI-generated visual content as a valued Devi feature. We map these to Odoo ir.attachment records linked to the relevant crm.lead or res.partner via res_model and res_id. Odoo stores attachments in the database (bytea) or on the filesystem depending on the ir_attachment storage setting. We require the customer to confirm whether visual assets are the primary deliverable or a secondary artifact.

If Devi exposes a lead score or intent level, we map it to a custom float field on crm.lead and preserve it as a reference for post-migration prioritization. Odoo Studio (Enterprise) or custom module development (Community) handles field creation before migration. We document the field type, allowed values, and whether it maps to a picklist or numeric scale during discovery.

Devi's high-intent detection operates on specific social platforms (LinkedIn, Twitter/X, etc.). We create a custom char field platform_source__c on crm.lead to capture which platform triggered the lead detection. This preserves the social attribution signal that may be lost if all leads are bulk-imported into Odoo without source tracking.

Devi user management is unconfirmed. We extract owner assignments from the source data (who owns each lead in Devi) and match by email to Odoo res.users. Any owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import. If Devi has no user assignment model, all leads are assigned to a default Odoo user during migration.

If Devi stores notes or annotations on leads, we map them to Odoo mail.message records linked to the crm.lead via model and res_id. Odoo's mail.thread architecture supports message threads on crm.lead, which provides a native notes interface for sales reps. Notes without a clear parent lead are held for customer confirmation during discovery.

If Devi tracks any engagement activity (DMs sent, comments, follow-ups) against leads, we map these to Odoo mail.activity records linked to crm.lead. mail.activity supports activity_type_id (call, email, meeting, todo) and user_id for assignment. We require the customer to confirm what activity types Devi tracks before defining the activity mapping.

If Devi uses tags or labels to categorize leads (by intent level, industry, product interest), we map them to Odoo crm.tag records. Odoo CRM includes a tags feature on crm.lead using an O2M to crm.tag. Tags are created during migration if they do not already exist in the destination Odoo instance.

Devi's data model is unconfirmed, but customers may have custom fields tracking additional lead attributes. We pre-create any destination custom fields via Odoo Studio (Enterprise) or custom module XML (Community) before migration. Field types are mapped from the source (text, number, date, selection) to the nearest Odoo field type during discovery.

Devi's automation rules (social listening triggers, notification rules, follow-up sequences) are not migrated to Odoo. Odoo handles automation through server actions, automated actions (Studio), or custom cron jobs — a different model from Devi. We deliver a written inventory of every Devi automation rule with its trigger conditions and actions, and the customer's Odoo admin or implementation partner rebuilds them in Odoo Studio or via custom module development.

Social outreach sequences or engagement cadences are not migrated. These are sales engagement features that require a dedicated tool (Odoo has no native sequence cadence equivalent at the CRM layer). We document the sequence structure so the customer can evaluate Odoo native automation, a third-party sales engagement tool, or a custom workflow rebuild.