Migrate from Dashcord to Odoo CRM

Dashcord Lead records map to Odoo CRM Lead (crm.lead model). The Salesforce Lead object is the source; we transform all standard fields (Name, Email, Phone, Company, Status) and any Dashcord-specific custom fields (lifecycle stage, lead score) into Odoo Lead fields. Dashcord's lifecycle stage value is preserved in a custom char field x_dashcord_lifecycle_stage on the Odoo Lead for reporting continuity. Lead owner maps by email match to the Odoo res.users record.

Dashcord Contacts map to Odoo CRM Lead with type='lead' and is_customer=True set after Account resolution. In Odoo's unified model, Contacts from Salesforce do not create a separate Contact object — they create Leads that the customer's sales team converts to Opportunities. We preserve the original Salesforce ContactId as x_sf_contact_id on the Odoo Lead for cross-reference. Standard contact fields (name, email, phone, title) map directly.

Dashcord Account records map to Odoo res.partner with customer=True. The Salesforce Account becomes the Odoo Partner that Contacts and Opportunities attach to. Account name, website, industry, phone, and address fields map to their Odoo equivalents. Billing and shipping addresses from Salesforce Account are preserved as Odoo partner address records (res.partner.address). Account is created before any Contact or Opportunity insert to satisfy the partner_id foreign key.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns and map them to Odoo CRM Campaign (crm.campaign). Campaign name, start and end dates, budget, and status transfer. Campaign member tracking data (how many Leads and Contacts are in each Campaign) is preserved as Odoo campaign statistics. Odoo campaign model supports tag-based segmentation equivalent to Salesforce Campaign Member status.

Campaign Members link Salesforce Leads and Contacts to Campaigns with status, timing, and response tracking. We map them to Odoo crm.tag.assignment records tied to the CRM Campaign. Dashcord campaign member status values (Sent, Open, Clicked, Responded) are preserved as custom selection values on the Odoo campaign record. Each member record is linked to the corresponding Odoo Lead converted from the source Contact or Lead.

Dashcord stores event records as custom Salesforce objects with schema that varies by package version. We introspect the custom object field definitions during pre-flight via the Salesforce Tooling API, export the active event records, and map them to Odoo calendar.event. Event name, start datetime, end datetime, location, and description transfer. Attendee relationships from Salesforce EventRelation map to calendar.attendee records on the Odoo event. Dashcord-specific event fields (event type, capacity, RSVP status) become custom fields on the Odoo event record.

Dashcord assigns lifecycle stage values (subscriber, lead, MQL, SQL, customer, evangelist) to Leads and Contacts as custom picklist fields. Odoo CRM uses its own stage model for the sales pipeline (New, Qualified, Proposition, Won, Lost) which is distinct from lifecycle stage. We preserve Dashcord lifecycle stage values in a custom field x_dashcord_lifecycle_stage on the Odoo Lead record. Customers who need lifecycle stage to drive automation in Odoo rebuild it as a separate stage column in Odoo Studio.

Dashcord stores numeric or tiered lead scores as custom fields on Salesforce Lead records. We export the raw score values and the scoring model name or rule set reference if stored in a custom object. The numeric score transfers to a custom integer field x_dashcord_lead_score on the Odoo Lead. The score tier label (Cold, Warm, Hot) transfers to x_dashcord_score_tier as a selection field.

Any custom fields added by Dashcord or the customer on Salesforce objects are introspected via the Salesforce Metadata API during pre-flight. We enumerate every custom field on each standard object, map Salesforce field types to Odoo field types (checkbox to boolean, text to char or text, number to float or integer, picklist to selection), create the Odoo custom fields via Studio or data migration payload, and populate the values during record import.

Dashcord tracks email sends, opens, and clicks via Salesforce Activity records (Task and EmailMessage objects). We export EmailMessage records with body, subject, from address, to address, and status (Sent, Read, Bounced). These load into Odoo as mail.message records linked to the crm.lead via the model and res_id foreign key. Email attribution (which Campaign drove the send) is preserved as a custom field x_sf_campaign_id on the Odoo message record.

File attachments on Salesforce Campaign, Contact, or Account records are stored as Salesforce ContentDocument, ContentVersion, or Attachment objects depending on org configuration. We export the file binary data and name, then create Odoo ir_attachment records linked via res_model and res_id to the matching Odoo Lead or Partner record. Files exceeding Odoo's default attachment size limits are flagged for the customer's admin to store externally and link via URL.

Dashcord does not have its own user model — user records are Salesforce User objects. We resolve Dashcord owner references by matching Salesforce User email against Odoo res.users email. Any Salesforce User without a matching Odoo user is held in a reconciliation queue for the customer's Odoo admin to provision before record import resumes. OwnerId on all migrating records is resolved to the Odoo res.users id at migration time.