Migrate from Oracle CRM On Demand to Odoo CRM

Oracle Accounts map to Odoo res.partner records with partner_type set to 'contact' = False and is_company = True. Oracle Account Name becomes res.partner name; Oracle address fields map to street, street2, city, state_id, zip, and country_id. Oracle Account Owner (user) maps to create_uid via email lookup. We resolve the Oracle Account row ID to the Odoo res.partner ID before importing any Contact records that reference it.

Oracle Contacts map to Odoo res.partner records with partner_type set to 'contact' = True and is_company = False. Oracle Contact Name, Email, Phone, Mobile, Job Title, and Department map to the corresponding res.partner fields. The parent_id lookup references the res.partner Account record resolved in the Account migration phase. We deduplicate by email using a pre-import dedup check and flag duplicates for customer review before insert.

Oracle Leads (Standard CRM On Demand tier) map to Odoo crm.lead records with type = 'lead'. Oracle Lead_Status maps to crm.lead stage_id; Oracle Lead_Source maps to crm.lead source_id; Oracle Rating maps to crm.lead priority. Custom lead fields migrate as char, text, or selection fields on the crm.lead model. Note that the Enterprise Lead Referral tier allows create-only access via the API with no edit, convert, or analytics, which restricts what lead history can be extracted; we flag this during discovery and scope accordingly.

Oracle Opportunities map to Odoo crm.lead records with type = 'opportunity'. Oracle Opportunity Name becomes crm.lead name; Oracle Revenue and Probability map to expected_revenue and probability; Oracle Close Date maps to date_deadline; Oracle Account maps via the Account lookup resolved in the Account migration phase. The pipeline stage from Oracle maps to the corresponding Odoo crm.stage ID, which we configure as a custom pipeline before migration.

Each Oracle Opportunity Stage becomes an Odoo crm.stage record within the CRM pipeline. We create the stages in Oracle stage order with the same probability percentages from Oracle (rounded to integer). Odoo's Kanban stage ordering is set by the sequence field. If Oracle has closed won and closed lost stages, we map them to Odoo's corresponding lost_closed and won stage states.

Oracle Tasks map to Odoo mail.activity records with activity_type_id set to the Odoo standard 'To Do' activity type. Oracle Task Subject becomes mail.activity summary; Oracle Status maps to mail.activity functional state (done vs open); Oracle Due Date maps to mail.activity date_deadline. The res_model and res_id on the activity record reference the migrated crm.lead or res.partner record.

Oracle Call records map to Odoo mail.activity with activity_type_id set to the Odoo 'Call' activity type. Call Duration from Oracle maps to a custom integer field crm_call_duration_seconds on the activity. Call Subject becomes activity summary; Call Date becomes date_deadline or activity_date_deadline. We store Oracle call disposition in a custom activity field for audit.

Oracle Appointments map to Odoo calendar.event records. Oracle Appointment Subject becomes calendar.event name; Oracle Start Date/Time and End Date/Time map to start and stop on the event; Oracle Location maps to location. Attendees map to calendar.attendee records linked by email to the migrated res.partner or crm.lead. Recurring appointments in Oracle require Odoo calendar recurrence configuration to replicate.

Oracle Named Users referenced as Owner on any record map to Odoo res.users by email address match. We extract every distinct Oracle Owner from Account, Contact, Opportunity, and Activity records during discovery, produce a user mapping table, and reconcile against the destination Odoo res.users table. Any Oracle Owner without a matching Odoo user goes to a provisioning queue for the customer's Odoo admin to create before record migration proceeds.

Oracle custom objects have tenant-specific schemas accessible via the Oracle Web Services API. We reverse-engineer each custom object's field definitions (field name, type, required, picklist values) from the Oracle API before creating the corresponding Odoo model. The Odoo model is created via ir.model and ir.model.fields with the correct field type (char, text, selection, many2one, one2many) matching the Oracle type. Custom object data migrates after all standard object parent lookups are resolved.

Oracle attachments associated with records (stored as URLs pointing to Oracle's document server or as binary blobs) map to Odoo ir.attachment records. We extract attachment content via the Oracle API, store it in our migration workspace, and create ir.attachment records with res_model pointing to the migrated model (crm.lead, res.partner) and res_id pointing to the migrated record ID. Large attachment volumes require separate scoping and may involve file-size limits on the destination Odoo instance.

Oracle Notes migrate as Odoo mail.message records with message_type = 'comment'. The note body becomes mail.message body (HTML). We link each note to the parent record via res_model and res_id. If Oracle notes are associated with multiple records, we create individual mail.message records per link or consolidate under a primary record at the customer's direction.