Migrate from erxes to Odoo CRM

erxes Contact records map to Odoo Partner records with Partner Type set to Individual. The erxes primaryEmail becomes the Odoo email field; firstName and lastName split from erxes fullName on the first space. Phone and mobilePhone migrate to Odoo Partner phone and mobile fields. We run Odoo's partner deduplication on email before insert to avoid creating duplicate partners for records that appear in both the erxes Contact and Company objects. Custom field values from erxes Contacts migrate as Odoo custom fields on the res.partner model, with field type mapping (text to char, date to date, select to selection) verified against the Odoo field definition.

erxes Company records map to Odoo Partner records with Partner Type set to Company. The erxes domain field becomes the Odoo website field, and parentId on linked Contacts resolves to this Partner after Company import. We set Odoo's industry_id from erxes industry by matching against the Odoo res.partner.industry selection list. Companies without a domain or website are created as Odoo Partner records without the website field populated, and deduplication runs on company name to avoid duplicates from import retries.

erxes Deals map to Odoo CRM Opportunity (crm.lead model). The erxes pipelineId and stageId translate to Odoo's team_id (Sales Team) and stage_id. Deal amount migrates to Odoo's expected_revenue and planned_revenue fields. The erxes createdAt timestamp preserves as Odoo's create_date. We resolve the partner_id on Odoo Opportunity by matching the erxes primaryCompanyId against the Partner records created in the Company import phase, falling back to matching by contact email if no Company link exists.

erxes Pipelines map to Odoo Sales Teams (crm.team model), and each erxes Pipeline Stage maps to an Odoo Stage within that Team. Stage names, probabilities, and order migrate. Odoo restricts Stages to a single sequence per team by default; if the erxes source uses multiple pipelines, we create a corresponding Odoo Sales Team per pipeline and map Deals accordingly. Stage probability percentages migrate to Odoo's probability field on crm.lead, rounded to nearest integer.

erxes Tasks migrate to Odoo Task records. If the customer uses Odoo Project, tasks map to project.task; otherwise they map to crm.lead as internal notes or activities. Task title, description (as HTML), due date (date_deadline), and stage status migrate. Owner assignment resolves by matching erxes userId to Odoo res.users by email. erxes Cycle membership does not migrate as Odoo has no native Cycle equivalent; cycle-based task grouping is documented for manual reorganization in Odoo Project if the customer adopts it.

erxes multi-channel Conversations (email, SMS, chat, WhatsApp) migrate to Odoo Mail Message records linked to the parent Partner. We preserve message body, direction (inbound/outbound), channel type, and createdAt timestamp as mail.message create_date. Channel credentials such as WhatsApp API keys and email integration tokens do not migrate; we flag these for manual reconfiguration in Odoo because they are destination-system credentials. Message threading order depends on the erxes server timestamp, which we preserve during import to maintain chronological fidelity.

erxes custom fields defined on Contacts, Companies, Deals, and Tasks migrate to Odoo custom fields on the equivalent model (res.partner, crm.lead, project.task). We pre-create the Odoo field schema before data import, setting field type (char, text, date, selection, many2one) to match the erxes field type definition. erxes schema-less import behavior means field values may arrive as wrong types; we validate and cast values against the Odoo field type before insert, flagging any that fail cast.

erxes Users map to Odoo res.users records. We resolve by email match during import. Any erxes User without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before Deal and Task import resumes. erxes role and permission configurations are destination-platform-specific and documented for manual rebuild in Odoo Access Rights settings.

erxes Channels (email, SMS, chat, WhatsApp) define communication mediums and credentials connected to the platform. Channel API keys, webhook URLs, and third-party credentials do not migrate because they are source-system credentials that do not apply to Odoo. We deliver a written list of every active erxes Channel with its type, connected number or inbox, and a recommended Odoo equivalent configuration (Odoo Mail, a third-party WhatsApp integration app from the Odoo Apps store, or Odoo's SMS gateway) for the customer's admin to rebuild post-migration.

erxes Automation Workflows define trigger-action sequences for customer journeys. We extract the workflow structure including triggers, conditions, and actions as a written inventory document. We do not migrate automations as code because erxes and Odoo use different rule engines. Each erxes automation is mapped to an Odoo Server Action or Automated Action equivalent (or a Planned Action on ir.cron) with trigger, condition, and action documented for the customer's Odoo admin to rebuild. Complex conditions referencing erxes object IDs are flagged individually because ID namespaces differ between systems.

erxes engagement records with subtypes (call, email, meeting, note) map to Odoo Mail Activity records linked to the parent Partner or Opportunity. Activity type, subject, body, and due date migrate. Odoo Mail Activity supports types: call, meeting, email, upload_document, and task. We map erxes engagement subtype to the nearest Odoo activity_type_id. Owner assignment resolves via the User mapping by email.

erxes tags on Contacts, Companies, and Deals migrate to Odoo CRM Tags (crm.tag model). Tags stored as multi-checkbox custom properties in erxes migrate to individual crm.tag records with many2many relation to crm.lead. Tag names are preserved verbatim; tag colors and categories do not migrate as Odoo CRM Tags has no color field by default.