Migrate from Sales Journey to Odoo CRM

Sales Journey Contact records map to Odoo res.partner with partner_type set to contact. The email, phone, mobile, street, city, state, country, and website fields migrate directly. We preserve the company association as a parent_id link to the mapped Company/res.partner record. Any Sales Journey custom fields on Contact are mapped to ir.model.fields created via Odoo Studio before migration.

Sales Journey Company records map to Odoo res.partner with partner_type set to company (company_type = company). Company name becomes the partner's name field, address fields map to the corresponding res.partner address columns, and industry/sector maps to industry_id (a many2one to crm.industry). The relationship between Companies and their Contacts is preserved via the parent_id hierarchy in res.partner.

Sales Journey Deals map to Odoo crm.lead in opportunity mode. The deal name becomes the lead's name field, deal value maps to planned_revenue, close date maps to date_closed, and stage name maps to a crm.stage value that we configure before migration. Owner assignment on the Deal maps to the user_id field on crm.lead via the cross-reference table built during discovery.

Sales Journey Lead records map directly to Odoo crm.lead. Lifecycle stage status from Sales Journey migrates as a custom stage value in Odoo's crm.stage if the customer's Sales Journey lifecycle model has more stages than the default Odoo New / Qualified / Proposal / Negotiation / Won / Lost model. We create additional crm.stage records during configuration to accommodate the full source lifecycle.

Each Sales Journey pipeline becomes a set of crm.stage records in Odoo. Stage names, stage order, and probability percentages migrate from Sales Journey to Odoo crm.stage records. Odoo's crm.team (sales team) assignment per stage is configured based on the customer's team structure. We recommend creating one crm.team per Sales Journey pipeline during scoping.

Sales Journey email engagement records map to Odoo mail.message with message_type = email. The message body and subject migrate; the email is linked to the parent crm.lead record via res_id and model fields. If the Sales Journey email has attachments, we export them as ir.attachment records linked to the mail.message via ir.attachment.res_model = mail.message.

Sales Journey call engagement records map to Odoo mail.activity with activity_type = Call (a configured subtype of the base call activity type). Call duration and disposition from Sales Journey migrate to custom Char fields on the activity. The activity is linked to the crm.lead record via res_id and model = crm.lead.

Sales Journey meeting engagements map to Odoo mail.activity with activity_type = Meeting. Start and end datetime, location, and attendee list migrate. Attendees are stored as mail.activity.touch records or noted in the activity's note field. The activity links to the crm.lead via res_id and model.

Sales Journey Notes and Task engagements map to Odoo mail.message with message_type = comment. The note body migrates as the message body, preserving author and timestamp. For Sales Journey tasks with due dates, we create a mail.activity with activity_type = Upload Document or a custom Task type configured in Odoo.

Sales Journey Owner references on Contacts, Companies, Deals, and Activities are resolved via email match against Odoo res.users. We build a cross-reference table during discovery. Any Sales Journey Owner without a matching Odoo User is flagged in a reconciliation queue for the customer's admin to provision before record migration begins. We do not create Odoo users programmatically without admin approval.

Sales Journey custom fields on Contacts, Companies, Deals, and Leads are audited during discovery. We pre-create equivalent custom fields in Odoo via Odoo Studio or as ir.model.data XML entries before migration. Field types are mapped: text fields to char or text, numeric fields to float or integer, date fields to date, and picklist values to selection fields or many2one relationships.

Sales Journey tag taxonomy exports as a flat per-record list. We map each distinct Sales Journey tag to an Odoo crm.tag record, then create crm.lead.tag.rel entries linking each crm.lead to its applicable tags. If the customer uses tags for segmentation rather than pipeline filtering, we note this and recommend whether crm.tag or a separate segmentation approach is more appropriate in Odoo.

File attachments stored within Sales Journey records are identified during scoping. We export them as binary files and ingest them into Odoo ir.attachment records, linking each to the parent record (crm.lead or res.partner) via res_model and res_id. Attachment size and total count are estimated during discovery to determine whether file migration happens in a single batch or incrementally.