Migrate from Odoo Field Service to Twenty CRM

Odoo's res.partner with partner_type='contact' maps directly to Twenty People. The email, phone, address, and job_title fields migrate as standard Twenty People fields. The res.partner.id is preserved as source_system_id__c for delta-run deduplication. This mapping requires the Company records (res.partner type=company) to exist in Twenty first so the companyId relation can resolve.

Odoo's res.partner with partner_type='company' maps to Twenty Companies. Company name, website, street/city/state/country fields migrate directly. The Odoo parent_id hierarchy (parent/child company relationships) is preserved by mapping parent_id to Twenty's companyId self-relation field. Multi-company Odoo setups map to separate Twenty workspace Companies records.

Odoo's crm.lead for active pipeline stages (new, qualified, proposition) maps to Twenty Opportunities. The expected_revenue field migrates to amount (currency field). Odoo's crm.stage names (new, qualified, etc.) are mapped via a value map to Twenty's opportunity stageName options. The lead's partner_id is resolved to the People record already migrated.

Won and lost crm.lead records migrate to Twenty Opportunities with stageName set to the corresponding closed stage. Odoo's won/lost stage probability values are mapped value-by-value. Lost reasons stored in Odoo's lost_reason_id field migrate as a custom text field (lost_reason__c) for audit continuity.

Odoo fsm.order has no native equivalent in Twenty. We create a custom object called 'field_service_order' in Twenty's data model with custom fields for: stage (fsm.stage.name), location_address (fsm.location.partner_id display name + street), scheduled_date (scheduled_date_start), assigned_worker (assigned_to user email match), and tags. The fsm.order.id is stored as source_system_id__c.

Odoo fsm.location records (service site addresses) are merged into the Twenty Companies object. The location name + address fields populate the Company name and address fields. If the location has a related partner_id (customer), we link it to that Company record. Locations without a customer link create standalone Company records in Twenty.

Odoo Project tasks linked to fsm.order migrate as Twenty Tasks. The task name, description, planned_date_begin/end, user_id (owner), and stage_id (stage name) map directly. Tasks linked to a fsm.order carry the source fsm.order ID in a custom field (source_fsm_order_id__c) for traceability back to the field service order.

Odoo file attachments (ir.attachment records linked to res.partner, crm.lead, or fsm.order) are downloaded and re-imported to Twenty. Files attached to People or Companies become Twenty Notes with the attachment content. Large binary files (e.g., signed PDFs from fsm.order worksheets) are stored with a URL reference to the destination storage.

Odoo res.users records with active CRM or Field Service access are matched to Twenty workspace members by email address. Unmatched Odoo users (e.g., inactive technicians no longer in the system) are flagged and assigned to a fallback owner. The match is used to resolve owner_id on crm.lead and user_id on fsm.order during migration.

Odoo bank details on res.partner (res.partner.bank records) have no native equivalent in Twenty's Company object. They are migrated as a custom multi-text field (bank_details__c) containing the account number, bank name, and IBAN as a formatted string. This is a reference-only preservation — payment processing is handled outside Twenty CRM.

Any Odoo custom fields added via Odoo Studio or ir.model.fields on crm.lead or res.partner are migrated as Twenty custom fields on People or Opportunities. The field type is inferred from Odoo's field ttype (char→text, integer→number, many2one→relation, selection→select). Fields with no equivalent in Twenty become custom text fields for reference.

Odoo fsm.tag records (name, color) migrate as a multi-select custom field (service_tags__c) on the field_service_order custom object. Tag names are preserved as options; tag colors are not migratable since Twenty multi-select fields use plain text values. Tags are de-duplicated (same name = one option).