Migrate from Corteza CRM to Odoo CRM

Corteza Lead records with conversion status of unconverted map to Odoo crm.lead with type = lead. Standard fields (first_name, last_name, email, phone, rating, source) translate to Odoo name, email_from, phone, and medium_id. We set type to lead at migration time and leave the opportunity conversion to occur natively in Odoo after go-live. Any Corteza lead_score or custom scoring fields map to crm.lead priority or a custom float field.

Corteza Account records map to Odoo res.partner with is_company = True. The company_name, industry, website, street, city, country, phone, and social media URL fields translate to Odoo partner fields (name, industry_id, website, street, city, country_id, phone, social_twitter/facebook/linkedin). We set parent_id = NULL for company partners and use the company_name field as the primary name field.

Corteza Contact records map to Odoo res.partner with is_company = False and parent_id pointing to the migrated Account partner. First name and last name concatenate into Odoo name. Email, phone, job_title, department, and the account relationship (AccountContactRole) translate to email, phone, function, department_id, and contact_type. If a Corteza Contact has no parent Account, we create an orphan partner record and flag it for the customer admin to resolve.

Corteza Opportunity records map to Odoo crm.lead with type = opportunity. Stage, amount, probability, expected_close_date, and description map to stage_id, expected_revenue, probability, date_deadline, and description. We resolve the Account lookup by matching Corteza account_id to the migrated res.partner company record and set partner_id on the Odoo opportunity. OpportunityContactRole records create crm.lead.partner_involved_id entries linking the Opportunity to related Contact partners.

Corteza Campaign records translate to Odoo utm.campaign for campaign tracking attribution (UTM tags on leads and opportunities). CampaignMember records linking Contacts and Leads to a Campaign migrate as crm.lead records tagged with the utm.campaign reference. Odoo does not have a native CampaignMember object; the campaign association is stored on the lead via campaign_id. If the customer requires campaign member tracking as a separate list, we recommend using Odoo Mass Mailing Lists (mailing.list) as the replacement.

Corteza Case records map to Odoo helpdesk.ticket if the customer licenses the Odoo Helpdesk app. Case status, priority, origin, and description translate to ticket stage_id, priority, origin, and description. Case-contact and case-account relationships map to ticket partner_id and the ticket's project_id if linked. If Helpdesk is not licensed, Cases map to crm.lead with a custom case_type tag and lose the service-level tracking features.

Corteza Contract records with line items (ContractLineItem) translate to Odoo account.move (invoicing) or sale.subscription (subscription management) depending on whether the contracts represent recurring billing or one-time agreements. Contract terms, dates, and related Account and Contact roles map to the corresponding fields. ContractLineItem pricing and quantities map to invoice lines or subscription line items. This mapping requires the customer to decide on the Odoo contract representation during scoping.

Corteza standalone Tasks with no parent CRM record map to Odoo project.task. Tasks related to CRM records (Lead, Account, Contact, Opportunity) map to Odoo calendar.event if they represent meetings or calls, or project.task if they represent action items. Status, due date, assignee, and description translate to stage_id, date_deadline, user_id, and description. Task assignment resolves Corteza user IDs to Odoo res.users by email match.

Corteza Event records (meetings, calls) map to Odoo calendar.event with start_datetime, stop_datetime, duration, location, and description preserved. Organizer and attendee references from Corteza resolve by email to Odoo res.users (organizer) and res.partner (attendees). EventRelation records in Odoo link attendees via calendar.event.res_partner_rel. We set the event's crm_lead_id if the Odoo event is linked to a migrated opportunity.

Corteza Quote records with line items (QuoteLineItem) map to Odoo sale.order. Quote status (draft, sent, accepted, lost) maps to Odoo state (draft, sent, sale_order, canceled). Related Opportunity maps via the order's opport_id to the migrated crm.lead opportunity. QuoteLineItem quantity, unit price, and discount map to sale.order.line quantity, price_unit, and discount. Product references resolve to Odoo product.product records via SKU match.

Corteza Product records map to Odoo product.template with product_variant_ids. Product name, SKU (hs_sku), list price, and cost map to name, default_code, list_price, and standard_price. If Corteza products have variants (size, color), we create Odoo product template with variant attributes. Pricebook and PricebookEntry records translate to Odoo product.pricelist and product.pricelist.item entries attached to the product.

Corteza's low-code module builder creates entirely custom module objects. We translate these to Odoo custom modules by pre-creating ir.model (x_custom_object) and ir.model.fields definitions in the destination Odoo database before data migration. Custom field types in Corteza (select, number, date, record reference) map to Odoo field types (selection, float, datetime, many2one). Custom validation rules, required field constraints, and default values translate to Odoo ir.model.constraint and ir.model.fields.default entries. The customer reviews the custom module mapping during staging.

Corteza file fields and standalone attachments migrate as Odoo ir.attachment records. We extract file binary content, name, and mime type from the Corteza export and create ir.attachment records linked via res_model and res_id to the migrated parent record (crm.lead, res.partner, etc.). Folder structure from Corteza's export is not preserved; all files land in a flat attachment list on each record. Bulk attachment export with full folder hierarchy may require supplemental file system handling beyond the API migration path.

Corteza Workflow definitions are captured during discovery as JSON exports and documented in the workflow rebuild handoff. We do not translate Corteza workflows to Odoo automated actions because the trigger models and action types differ structurally. The inventory document lists each Corteza workflow with its trigger (record create, update, stage change), conditions, sequence, and actions with Odoo Automated Action or Studio action equivalents recommended for rebuild in Odoo Studio. Lead conversion automation is flagged as requiring specific Odoo CRM action rules.