Migrate from Odoo CRM to Twenty CRM

Odoo's crm.lead table holds both Leads and Opportunities in one table, distinguished by the type field. We filter type='lead' and migrate these as Twenty Opportunities in a New or Prospect stage. The original Odoo type value is preserved in a custom field odoo_record_type__c for audit. Fields including name, email_from, phone, source_id, and description map to their Twenty equivalents. Stage resolution uses crm.stage.name mapped against Twenty's pipeline stage values.

Odoo Opportunities (crm.lead with type='opportunity') map directly to Twenty Opportunities. Key fields including expected_revenue, probability, date_closed, and partner_id migrate. The partner_id foreign key resolves to a twenty.person record that we create or match during the Partner/Contact migration phase. stage_id maps to the nearest Twenty pipeline stage; probability percentages are rounded to integer and stored on the Opportunity.

Odoo res.partner records where is_company=True map to Twenty Company records. Fields including name, street, city, country_id, phone, website, and email map directly. The company's domain from website is used as a dedupe key. Company records are created before any Person or Opportunity import so that lookup relationships are satisfied at insert time.

Odoo res.partner records where is_company=False map to Twenty Person records. The linked company partner (company_id field) becomes the Person's company link in Twenty. Fields including name, email, phone, function (job title), and address fields migrate. We match existing Persons by email during import to avoid duplicate records.

Odoo crm.stage records per team map to Twenty pipeline stage values. Each stage has a name, sequence, and probability. We extract all custom stages the customer has added and map their names and probabilities to Twenty's pipeline stage configuration. The Odoo team-stage relationship (crm.team.stage.rel) is documented but simplified in Twenty because Twenty supports a single pipeline per workspace by default.

Odoo Sales Teams (crm.team) have members and independent pipeline stage configurations. Twenty does not replicate Odoo's per-team pipeline model. We document each Odoo team's member list and map team ownership to Opportunity assignment. If the customer requires team scoping in Twenty, we configure Twenty's workspace permissions as the equivalent structure.

Odoo crm.tag records are a flat list applied via many2many to crm.lead. Tag names migrate as a tag array on Twenty Opportunities. If the customer uses tags for segmentation, we map them to a multi-select custom field on Opportunity rather than Twenty's native label system, depending on use case.

Odoo mail.activity records linked to crm.lead migrate to Twenty Tasks attached to the corresponding Opportunity. Fields including activity_type_id, date_deadline, user_id (mapped to Person or Team Member), and note body migrate. Activity ordering is preserved by setting the task's created_at timestamp to the original Odoo activity date. High-volume activity exports are chunked to avoid overwhelming the Twenty REST API.

Odoo ir.attachment records linked to crm.lead are stored in the Odoo filestore. We export attachments as files, preserve their original filenames and MIME types, and generate a mapping of ir_attachment.id to file path. In Twenty, we store the file URL or re-upload to the customer's chosen storage. Large attachment volumes are exported separately and sequenced after parent Opportunity records to prevent orphaned references.

Odoo sale.order records linked to Opportunities carry line items, pricing, and taxes. Twenty does not have a native Quotation or Order object in the standard CRM scope. We export sale.order as a structured JSON payload and store it as a custom field on the linked Twenty Opportunity, preserving order lines, totals, and currency. The customer's admin can review and recreate quotes in Twenty or a connected tool if needed.

Odoo custom fields on crm.lead are stored as columns in the database. We export field definitions (name, field type, selection options) and map them to Twenty custom fields on Opportunity. Selection fields map to Twenty dropdown custom fields; many2one and many2many fields require schema review to determine the correct lookup relationship in Twenty. We pre-create the destination custom field schema before data import.