Migrate from OrangeCRM to Odoo CRM

OrangeCRM Customers map to Odoo res.partner records with partner_type = 'contact' for individual contacts and partner_type = 'company' for organization-level accounts. We extract the Customer export, map the organization name to Odoo's name field, and preserve custom properties (industry classification, account status flags) as Odoo custom fields. Parent-company relationships in OrangeCRM's Customer hierarchy map to the partner's parent_id field in Odoo, and child contacts attach to the parent partner record.

OrangeCRM Contacts export cleanly with standard fields (name, email, phone, address). We map these 1:1 to Odoo res.partner records, resolving the parent Customer as partner_id or parent_id depending on whether the Contact is an individual or an organizational sub-entry. Multi-value email and phone fields from OrangeCRM split into the Odoo email, phone, mobile, and fax fields. Any contact-level custom fields generated in OrangeCRM's Customer module become Odoo custom fields on res.partner.

Fulfillment records in OrangeCRM track subscription or order fulfillment status tied to Customers. We map Fulfillment to Odoo sale.order, preserving fulfillment status, fulfillment date, and subscription identifiers as custom fields on the order. The OrangeCRM Customer reference maps to the sale.order's partner_id. Line items map to sale.order.line records. Fulfillment-specific metadata (fulfillment method, tracking number, fulfillment node) becomes Odoo custom fields for admin visibility. Customers should validate that business logic embedded in fulfillment-stage transitions is correctly represented using Odoo sale.order state transitions.

OrangeCRM Help Desk tickets with status, priority, assignee, and conversation history map to Odoo helpdesk.ticket. Ticket status (open, pending, resolved, closed) maps to Odoo stage_id; priority maps to priority field. Assignee maps to Odoo user_id via email match against the Odoo User table. Conversation threads convert to Odoo message records attached to the ticket. Ticket relationships to Contacts map to Odoo partner_id on helpdesk.ticket.

Email campaign records and subscriber lists in OrangeCRM map to Odoo mass_mailing.contact records attached to mailing.list records. Subscriber opt-in dates and campaign engagement metrics (opens, clicks) preserve as custom contact fields. Campaign-level attributes map to mailing.mailing properties. Email templates, send history, and delivery metrics do not migrate as functional data; we document campaign names and engagement benchmarks for the customer's admin to reference when rebuilding in Odoo Marketing Automation.

BI reports and dashboards in OrangeCRM are configuration artifacts, not transactional records. We export report definitions and chart configurations as JSON metadata and deliver them as a reference document. The actual analytics data rebuilds in Odoo Reporting from migrated transactional records. Dashboards must be reconstructed in Odoo Studio or via custom report definitions post-migration.

Storefront orders and product records in OrangeCRM map to Odoo sale.order and product.product. Order totals, line items, and fulfillment status migrate as sale.order and sale.order.line records. Odoo product variants map from OrangeCRM product variants where present. Product images and descriptions become Odoo product template custom fields. Any OrangeCRM storefront-specific identifiers become Odoo custom fields for order reference.

OrangeCRM Banking module records for payment or ledger tracking map to Odoo account.move. We flag any multi-currency handling requirements during scoping and preserve currency codes in Odoo custom fields on account.move. Payment references map to Odoo's payment_reference field. Invoice-level metadata from the Banking module becomes custom fields on account.move for reconciliation visibility. Customers should confirm whether OrangeCRM's ledger entries represent invoices, payments, or both before migration, as the mapping differs per record type.

Event registrations and attendee records in OrangeCRM map to Odoo event.event records for the event and res.partner for attendees. Attendee status (registered, attended, cancelled), session selections, and custom registration fields become custom fields on event.registration. Multiple registrations for the same event require 1:N row generation during the transform pass. Event-level custom fields become Odoo custom fields on event.event.

OrangeCRM custom fields per module are extracted from the export schema. We pre-create equivalent Odoo custom fields using ir.model.fields with matching types (char, selection, float, boolean, date, many2one) before any data import. The field label and help text migrate from OrangeCRM's custom field definition. All custom field creation occurs in the schema design phase before production migration.

File attachments on OrangeCRM records export as URL references or binary blobs depending on OrangeCRM's export method. We download and re-upload attachments to Odoo's ir.attachment table, linking each to the migrated record via res_model and res_id. The attachment name, mimetype, and file size preserve. Any attachment URL that returns a 404 after extraction is flagged in the migration report with the source record reference.

OrangeCRM user accounts and record owners map to Odoo res.users by email match. We extract every distinct owner referenced on OrangeCRM records (Contacts, Companies, Fulfillments, Tickets) and match against the destination Odoo User table. Users without a match go to a reconciliation queue; the customer's Odoo admin provisions any missing users before migration resumes. Owner assignments on migrated records resolve to the matched res.users.id.