Migrate from EspoCRM to Odoo CRM

EspoCRM Account records map directly to Odoo res.partner with partner_type = 'company'. The Account name becomes the partner display name, website URL migrates as website field, and industry classification maps to Odoo's industry_id field. We use the company domain as the dedupe key during import to prevent duplicate partner records when multiple EspoCRM Contacts reference the same Account. Address data (street, city, state, country, zip) migrates as partner address records (res.partner.address or the built-in address tab on the partner form).

EspoCRM Contact records map to Odoo res.partner with partner_type = 'contact' and parent_id pointing to the mapped Account partner. We deduplicate by email address during import so that multiple EspoCRM Contacts with the same email produce one Odoo partner record with multiple address records. Title (Mr/Ms/Dr), phone, email, and function fields migrate to the partner contact record. Any Contact linked to a deleted or null Account in EspoCRM creates an orphan-free res.partner with parent_id = null and is flagged for manual Account assignment review.

EspoCRM Leads map to Odoo crm.lead records with type = 'lead'. The EspoCRM lead status and conversion date fields map to Odoo's stage_id and date_closed. If the EspoCRM Lead was converted to a Contact before migration, we follow the conversion link and map the resulting Contact to res.partner (as above) rather than a crm.lead. Unconverted Leads retain full lead-specific fields including source, rating, and campaign attribution.

EspoCRM Opportunity records map to Odoo crm.lead with type = 'opportunity'. The opportunity amount field migrates to Odoo's planned_revenue, probability maps to probability (rescaled if EspoCRM used a different probability scale), and expected_close_date maps to date_deadline. Stage mapping requires a configuration step: we extract EspoCRM's stage names and probabilities, create matching Odoo stage records in the CRM pipeline via XMLRPC, and assign stage_id on each Opportunity during import. partner_id on the Odoo opportunity is resolved from the Account mapping.

EspoCRM Cases map to Odoo Helpdesk tickets (helpdesk.ticket) if the destination Odoo instance includes the Helpdesk app. If Helpdesk is not in the current Odoo subscription scope, Cases map to crm.lead records with a custom case flag for admin review. Case priority maps to Odoo ticket priority (1-5 scale), case status maps to ticket stage, and the conversation thread migrates as mail.message records linked to the ticket. The parent Account partner_id resolves from the Account mapping.

EspoCRM Campaign records migrate as Odoo utm.campaign records, which provide the source attribution infrastructure for Leads and Opportunities in Odoo CRM. Campaign targeting lists (linked Leads and Contacts) do not migrate as Odoo mailing lists; instead, the campaign name and medium/source attribution links are recorded on each migrated Lead so that pipeline reporting can filter by campaign. Full mailing list migration requires Odoo Marketing Campaigns app separately.

EspoCRM Meeting records map to Odoo calendar.event. Start datetime, stop datetime, location, and description migrate directly. The partner_ids on the Odoo calendar.event are resolved by matching EspoCRM's linked Contact and Account IDs to the mapped res.partner records via our ID remapping table. If a linked Contact has no matching partner (unresolved Account), we create a minimal partner record or skip the partner linkage with a flag for manual review. Meeting attendees also include mapped EspoCRM Users resolved to Odoo res.users.

EspoCRM Call records have two migration paths depending on the Odoo apps installed. Calls where duration and outcome are primary map to Odoo crm.phonecall (a standard CRM module in Odoo). Calls that represent scheduled meetings map to calendar.event with event_type set to 'call'. We assess the EspoCRM call record's purpose field during discovery and assign each to the appropriate Odoo object. The partner and user resolution follows the same remapping table as meetings.

EspoCRM Task records map to Odoo project.task. Task status maps to Odoo stage_id (within a default project pipeline), priority maps to priority, and assigned user resolves via the User mapping table. Tasks linked to specific CRM records (Opportunities, Cases) attach via the Odoo project.task record's related_opportunity_id or ticket_id cross-reference. If Odoo Project is not in the subscription scope, Tasks map to crm.lead tasks or are flagged for project app activation.

EspoCRM email engagement records (tracking sent emails) migrate as Odoo mail.message records linked to the relevant crm.lead, res.partner, or helpdesk.ticket via model, res_id, and message_type fields. The email body and subject transfer as message_body and subject fields. Full email conversation threads (reply chains) do not migrate because EspoCRM stores the sent email record but not the recipient's reply chain within the CRM; we document this boundary in the scope document.

EspoCRM Document records and file attachments require separate handling for self-hosted instances where files live on the filesystem under data/files/. We extract the referenced files during discovery, transfer them to Odoo's filestore path (typically under filestore/ based on the database UUID), and re-register each as ir.attachment records linked to the parent model (crm.lead, res.partner) via res_model and res_id. Cloud-hosted EspoCRM instances expose attachments via the API, which we stream directly to Odoo via XMLRPC binary upload.

EspoCRM custom entity types created via Entity Manager have no direct Odoo equivalent that can be created without developer involvement. We export the entityDefs metadata (field names, types, relationships, ACL rules) and document the Odoo custom module structure needed to reproduce each entity. The migration includes a staging-phase upsert of custom entity records into a temporary Odoo table for manual module deployment by the customer's Odoo developer. We do not deploy Odoo custom modules within the migration scope; we deliver the metadata specification and the staged record data.