Migrate from Daffodil CRM to Odoo CRM

Daffodil CRM Contact records map to Odoo res.partner with partner_type = 'contact'. We extract contact name, email, phone, company association (via company_name field), lifecycle stage (custom property), and any custom fields. In Odoo, the contact's address fields (street, city, country) live on a separate res.partner record when the address differs from the company; we create address records as children of the parent company partner. The customer selects whether Daffodil contacts without a company association import as standalone partners or get a placeholder company created.

Daffodil CRM Company records map to Odoo res.partner with partner_type = 'company'. The company's name becomes the partner name, domain or website becomes website field, and industry classification maps to custom res.partner fields if configured. We create the company partner before importing contacts so that the contact's parent_id reference is satisfied at the moment of import. Company records without contacts create standalone company partners; company records with multiple contacts receive all related contacts as children.

Daffodil CRM Deals map to Odoo crm.lead with type = 'opportunity'. We capture deal name, amount (stored as float), stage, expected close date, owner assignment, and associated contact via partner_id. The Daffodil pipeline name maps to Odoo's crm.team (sales team) or a custom pipeline stage configuration. Custom pipeline stages on Daffodil Deals create Odoo stage records in the CRM pipeline with the same probability and sequence order.

Daffodil CRM activity records are flat rows with activity type, date, duration, outcome, and related contact or deal. We map call activities to Odoo crm.activity records with activity_type_id pointing to the Call category, meeting activities to the Meeting category, and email activities to the Email category. The activity body and outcome notes migrate to mail.message linked to the crm.lead. If Daffodil stores email content separately, we create mail.message records with message_type = 'email' attached to the partner or lead. Activity ordering is preserved by setting create_date to the original Daffodil timestamp.

Daffodil CRM custom fields on contacts, companies, and deals require pre-creation in Odoo via Settings > Technical > Database Structure > Model Fields (developer mode) before import begins. We receive the customer's full Daffodil field inventory during scoping, map each to an Odoo field with the appropriate type (char, text, selection, float, integer, date, datetime, boolean), and create the fields as custom columns on the target model. Multi-select picklist values from Daffodil become Odoo selection fields with matching key-value pairs. We do not create custom Odoo modules; custom fields are created via the Odoo interface or directly in the database.

Daffodil CRM user records (sales reps, managers, admins) map to Odoo res.users by email match. We extract owner assignments from Contacts, Companies, and Deals and resolve each to an Odoo user record. Users that do not yet exist in the destination Odoo instance are placed in a reconciliation queue for the customer's Odoo administrator to provision (with login credentials and appropriate access rights) before record import resumes. Active and inactive status maps directly.

Tags applied to Daffodil CRM contacts, companies, or deals export as comma-separated values or individual rows per the customer's export format. We flatten multi-value tag fields and reassemble them in Odoo by matching tag names to crm.tag records, creating any missing tags at import time. Odoo's tag model is a simple name field with no hierarchy; if Daffodil uses a hierarchical tag taxonomy, we flatten it to a single-level tag in Odoo and document the original structure for manual categorization.

If the customer's Daffodil CRM instance separates unqualified prospects from qualified contacts as distinct objects, the prospect records map to Odoo crm.lead with type = 'lead'. The lead status and score properties migrate to crm.lead custom fields or stage values. We check during discovery whether Daffodil uses a separate Lead concept or a single Contact object with a lifecycle stage property.

File attachments stored within Daffodil CRM (documents, images, uploaded files) are not reliably exportable via CSV. We do not migrate attachment binary content directly. Instead, we export attachment metadata (filename, file type, upload date, related contact or deal) as a reference list that the customer's admin uses to manually re-upload files to the relevant Odoo records after migration. If the customer has direct database access to Daffodil CRM, we can extract binary blob fields and reconstruct them as ir.attachment records in Odoo as a separate scoped task.

Daffodil CRM notes (free-text entries not tied to an activity type) migrate to Odoo mail.message records with message_type = 'comment' attached to the parent crm.lead or res.partner. The note body migrates as the message body, and the original creation date migrates as create_date to preserve chronological ordering on the record's chatter thread.

Daffodil CRM pipeline stages map to Odoo crm.stage records within the relevant crm.team's pipeline. We preserve stage sequence order, probability percentage, and whether the stage is marked as won or lost. Closed-Lost and Closed-Won outcomes from Daffodil map to Odoo's fold and is_won flags on the respective stage record.

If the customer's Daffodil CRM uses a team or department structure for deal assignment, we map these to Odoo crm.team records. Team member assignments resolve to res.users records via email matching. The crm.team's alias_name and use_leads toggle are configured to match the customer's workflow preference (lead-first vs. opportunity-first).