Migrate from Crust CRM to Odoo CRM

Crust Contact records map to Odoo res.partner with is_company=False. Standard fields (name, email, phone, mobile, street, city, state_id, country_id, zip) map directly. The Crust lifecycle_stage property maps to a custom res.partner field (x_lifecycle_stage) since Odoo standard partner does not include lifecycle tracking. Owner assignment from Crust contact_owner_id resolves to Odoo res_users id by email match before partner insert.

Crust Company records map to Odoo res.partner with is_company=True. The company domain becomes the partner website field. We run deduplication against existing Odoo partners using company domain and company name as the dedupe key. After partner insert, we link any Crust Contacts with the same company_id by updating their partner_id field to the newly created company partner.

Crust Deal records map to Odoo crm.lead with type='opportunity'. The deal_name maps to crm.lead name, deal_amount maps to planned_revenue, close_date maps to date_deadline, and probability maps to Odoo probability (or is calculated from stage mapping). Crust pipeline_id and dealstage_id map to crm.lead team_id and stage_id respectively, requiring a pre-migration pipeline-stage translation table built during discovery.

Crust pipelines map to Odoo crm.team records, and Crust pipeline stages map to crm.stage records linked to each team. We collect the full Crust pipeline-stage map during discovery, generate a translation table that preserves stage order and probability, and create the Odoo teams and stages before any crm.lead import begins. Closed-Lost and Closed-Won stages in Crust map to Odoo's lost_status and won_status defaults.

Where Crust CRM uses a distinct Lead object from Contact, we map to Odoo crm.lead with type='lead'. Crust lead_status property maps to crm.lead activity state or a custom tag field. Leads that exist in Crust but have no corresponding opportunity are migrated as Odoo leads, which can be converted to opportunities later via Odoo's Lead to Opportunity wizard.

Crust user records map to Odoo res.users by email match. We extract every distinct Crust owner_id referenced on Contact, Company, Deal, and Engagement records. Owners without a matching Odoo user go to a reconciliation queue for the customer's Odoo admin to provision before record import resumes. Active/inactive status maps directly.

Crust email activities map to Odoo mail.message records linked to the parent res.partner (for contact emails) or crm.lead (for deal emails). The Crust email body migrates as mail.message body (HTML), sender and recipient map to email_from and partner_ids respectively, and message_date preserves the original timestamp for activity timeline ordering.

Crust call activities map to Odoo crm.phone.call.log if the Odoo instance has the VoIP module installed, or to mail.activity with activity_type=call. Call duration, disposition, and recording URL map to call log custom fields. ActivityDate from Crust preserves for timeline ordering.

Crust meeting activities map to Odoo calendar.event with start, stop, duration, and location preserved. Attendees map to calendar.event attendee records linked to res.partner records. Meeting notes migrate as mail.message attached to the calendar.event.

Crust note activities map to Odoo note.note records linked via mail.activity.mixin to the parent res.partner or crm.lead. Note body preserves rich text. We flag notes with file attachments for separate file migration handling.

Crust task activities map to Odoo project.task if the project module is active, or to mail.activity with activity_type=todo. Task status, priority, due_date, and assigned owner map directly with owner resolved via email match to res.users.

Crust tags on Contacts map to Odoo res.partner.category records. Crust tags on Deals map to Odoo crm.tag records. Tags stored as multi-checkbox custom properties map to Odoo crm.lead tag_ids. We document tag strategy during scoping since Odoo does not have a global tag model shared across all objects.

Crust custom objects require schema pre-creation in Odoo before migration. We create Odoo custom models via the ir.model and ir.model.fields API, define field types that match Crust field types (char, text, integer, float, date, datetime, many2one, one2many, many2many), and then import the custom object data via XML-RPC with the newly created model API name. This is the most complex object in the migration and requires a dedicated discovery phase.

Crust custom properties on standard objects (Contact, Company, Deal) migrate to Odoo custom fields. We create the custom field via Odoo Studio before migration, or via ir.model.fields if the field type is not supported by Studio. Selection fields (picklist) in Crust map to Odoo selection fields with the same options list.

Crust attachments stored per-record migrate as Odoo ir.attachment records linked via res_model and res_id to the parent record (res.partner or crm.lead). We export files individually preserving filename and association, re-attach in Odoo, and map the original Crust attachment URL to the Odoo ir.attachment external URL field if Odoo version supports it.

Crust enterprise messaging channels and identity management modules are recorded as metadata during export and delivered as a written inventory document. Odoo does not have a direct equivalent messaging module; the inventory documents the channel names, members, and message counts so the customer's admin can recreate channels in Odoo Discuss (mail) or a third-party messaging integration.