Migrate from Twenty CRM to Odoo CRM

Twenty Companies map to Odoo Partner records with partner_type set to 'company'. We use the Twenty company domain as the Odoo Partner Website field and as the dedupe key during import. Odoo Partner records must exist before any Contact (People) import because Odoo's Contact model links to a parent Partner via partner_id. We handle Twenty's soft-delete uniqueness constraint by checking for deleted Partner records in Twenty with matching domain before creating new Odoo Partners.

Twenty People records map to Odoo Contact records under the corresponding Partner. The companyId foreign key resolves to the Odoo Partner ID at migration time. We flag People records without a companyId for customer decision: either create a placeholder Odoo Partner or link to an existing partner. Phone numbers normalize from Twenty's E.164 format to Odoo's locale-aware phone field. Email serves as the dedupe key on Contact.

Twenty Opportunities map to Odoo CRM Opportunity records. The linked Company and Person resolve to Odoo Partner and Contact IDs respectively. Stage names migrate as Odoo stage values in the CRM pipeline Kanban; we create or map pipeline stages explicitly to avoid silent mismatches. Amount, close date, probability, and expected revenue migrate to Odoo's expected_revenue, date_closed, and probability fields. We configure the Odoo CRM pipeline stages before migration to match the Twenty pipeline structure.

Twenty Tasks map to Odoo To-Do records linked to the relevant Partner, Contact, or Opportunity via res_model and res_id. Title, due date, assignee (ownerId resolving to Odoo User), completion status, and description migrate. Task priority maps to Odoo's priority field (0-3 scale). Completed status from Twenty maps to Odoo's closed boolean. Record-to-task relational links are preserved by resolving the parent record to its Odoo ID before importing the task.

Twenty Notes migrate as Odoo Chatter messages or Notes attached to the target Partner, Contact, or Opportunity. The note body content migrates as the message body. We preserve the relational target by mapping Twenty's note target record to the corresponding Odoo Partner, Contact, or Opportunity ID. Note attachments migrate as Odoo IrAttachment records linked to the parent record. The activity type (NOTE engagement in Twenty) becomes a chatter message for activity timeline continuity.

Twenty Custom Objects use a metadata-driven schema where fields are created via the /metadata API and a GraphQL schema is generated dynamically. Odoo Custom Objects require a Python module with ir.model and ir.model.fields XML definitions. This is not a direct data migration — it is a custom development task that must be scoped and executed separately before data can be imported. We deliver a written schema mapping of each Twenty Custom Object (fields, types, relationships) to a proposed Odoo model structure, and the customer's Odoo developer or a FlitStack AI custom development engagement builds the module before migration data loads.

Twenty call engagements map to Odoo CRM Call records linked to the Contact or Partner. Call disposition, duration in seconds, and timestamp migrate to Odoo's call_duration, description, and date_deadline fields. We preserve activity timeline ordering by setting the Odoo record date to the original Twenty timestamp. Call disposition values from Twenty may not have Odoo equivalents — we map them to custom selection fields or store as plain text notes at customer preference.

Twenty meeting engagements map to Odoo Calendar Event records. Start datetime, end datetime, location, and meeting title migrate. Attendee records map to Odoo EventPartner records linked to the Contact or Partner. Timeline ordering is preserved via the event start date. We handle UTC normalization for meetings with timezone metadata to ensure Odoo displays correct local times after import.

Twenty email engagement history migrates as Odoo Chatter messages on the Contact or Partner record. Email body content, subject, and timestamp transfer. Attachments become IrAttachment records linked to the message. Note that Odoo does not have native two-way email sync out of the box — the email bodies appear as logged chatter but do not provide an inbox experience. Teams expecting Outlook or Gmail integration configure Odoo's incoming mail server (fetchmail) separately post-migration.

Twenty Owners map to Odoo User records matched by email address. Any Twenty Owner without a matching Odoo User goes to a reconciliation queue for the customer's Odoo admin to provision before record import resumes. OwnerId references on Opportunity and Task require a valid Odoo User to be present at migration time, making this a dependency that blocks downstream imports if unresolved.

If Twenty includes product or subscription data in Custom Objects or linked to Opportunities, we map Product Template records in Odoo with Standard Price List entries. SKU, name, list price, and cost migrate directly. Products must exist in Odoo before Line Item or Opportunity Product link records import.

Twenty tags on People, Companies, and Opportunities map to Odoo Tags on the CRM record. Multi-value tags from Twenty (stored as arrays or comma-separated values) map to Odoo tag_ids many2many field. The customer chooses at scoping whether tags become Odoo CRM tags, Partner category records, or both.