Migrate from Datacor CRM to Odoo CRM

Datacor CRM Contacts map to Odoo res.partner records with partner_type set to contact. Chemical-industry-specific fields (regulatory compliance contact flags, EDI readiness, shipping address distinctions) map to custom partner fields created in Odoo before migration. We deduplicate Datacor Contacts against Accounts on customer ID to avoid duplicate res.partner records where the CRM shares a customer record with the ERP layer.

Datacor CRM Accounts (chemical distributors and manufacturers) map to Odoo res.partner with partner_type set to company. Account hierarchy fields (parent-subsidiary structures) map to Odoo's parent_id self-referential lookup on res.partner. Regulatory certification dates and industry classification fields migrate to custom company fields in Odoo.

Datacor CRM Opportunities map to Odoo crm.lead records with type = opportunity. Chemical sales cycles (30-180+ days with multi-stage hazardous material approvals) migrate with stage names mapped to Odoo stage_ids, close_date mapped to date_deadline, and probability preserved. Long-cycle opportunities retain their historical stage progression in Odoo's crm.lead.history model when available from the export.

Datacor CRM Quotes map to Odoo sale.order records. Quote headers, line items, and pricing migrate. Chemical-specific line attributes (CAS numbers, hazard classifications, regulatory spec references) are stored in Odoo custom order line fields pre-created before migration. Datacor's ERP-integrated pricing engine references are replaced with Odoo product pricelist rules configured post-migration.

Datacor CRM Products map to Odoo product.product records with chemical attributes (CAS number, GHS hazard classification, SDS document URL, formulation data) migrated to custom product fields. CAS numbers and hazard classifications require Odoo custom fields created before migration; standard product.template fields do not cover these chemical-specific attributes. Product categories map to Odoo product.category.

Datacor CRM Cases map to Odoo helpdesk.ticket if the customer deploys the Odoo Helpdesk app, or to crm.lead with type = lead if the customer uses only the CRM app. Case status, assignment, description, and contact linkage migrate. Case-thread email history exports as plain text from Datacor and is attached to the ticket description or migrated as mail.message records if the Odoo mail archiver is active.

Datacor CRM call reports, logged activities, and task records export as date-stamped entries linked to Contacts or Accounts. We migrate these to Odoo mail.activity records with activity_type_id, date, user_id (owner), and summary preserved. Activity sequences or engagement journeys are not structurally migratable in Odoo because they require Odoo's own activity planning framework.

Datacor CRM Notes map to Odoo note.note records. Notes linked to specific records migrate as mail.message records attached to the parent res.partner or crm.lead for richer threading. Standalone notes migrate to note.note with the original creation date preserved.

Datacor CRM does not expose a documented bulk attachment export endpoint. We export attachment file names and URLs per record from the CRM UI or database layer where accessible, and map them to Odoo ir.attachment records with res_model and res_id pointing to the migrated parent record (res.partner, crm.lead, or sale.order). File content transfer depends on the export method available from Datacor's licensing tier.

Datacor CRM Owners map to Odoo res.users records. We resolve owners by name and email match against the destination Odoo instance's user table. Owners without a matching Odoo User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Datacor CRM pipeline assignments map to Odoo crm.team (sales team). We create crm.team records for each Datacor pipeline and map opportunity ownership to the corresponding team. If Datacor pipelines have distinct stage sets, each team gets its own stage configuration in Odoo.

Fields such as CAS Registry Numbers, GHS hazard classifications, SDS document links, and regulatory certification dates are native to Datacor CRM's data model but have no standard Odoo equivalent. We create custom fields on the relevant Odoo models (res.partner for compliance contact flags, product.product for chemical product attributes, sale.order.line for quote line hazard annotations) before migration. The customer validates that the expected field types (char, text, date, binary for SDS files) are supported in their Odoo edition.