Migrate from CRM Service to Odoo CRM

CRM Service Accounts map to Odoo res.partner records where is_company = True. We extract Account.Name as partner name, Account.BillingAddress as address fields, Account.Industry as a custom selection field, and Account.AnnualRevenue as a float field. The commercial_partner_id on the created partner record points to itself (self) marking it as the top-level organization. Account is created first so that Contact import can resolve the parent partner reference immediately.

CRM Service Contacts map to Odoo res.partner records where is_company = False and parent_id = the mapped Account. We extract Contact.FirstName and Contact.LastName concatenated into partner name, Contact.Email as email, Contact.Phone as phone, Contact.Title as function/title. The parent_id field links the contact to its organization partner record. Contacts without an Account are created as individual partners (is_company = False, parent_id = null) and flagged for manual review.

CRM Service Opportunities map to Odoo crm.lead with type = 'opportunity'. We extract Opportunity.Name as lead name, StageName as stage_id (mapped to Odoo stage sequence), Amount as planned_revenue, CloseDate as date_deadline, Probability as odoo_probability (custom float field), and Owner as user_id via email match to Odoo res.users. The partner_id field links the opportunity to the mapped Account partner record.

CRM Service Leads map to Odoo crm.lead with type = 'lead'. Where the destination Odoo instance has the Lead Management module installed (standard on CRM app), leads are tracked as separate crm.lead records until converted to opportunities. We preserve LeadStatus as a custom selection field on the lead. Lead score or rating migrates to priority field. Leads with a CompanyName are created with is_company = True on the linked partner; those without are attached as contacts to the company if one is found by domain match.

CRM Service Opportunity stages map to Odoo crm.stage records within the appropriate crm.team sequence. We create stages in the same order as the source, preserving the probability percentage (rounded to nearest integer) and won/lost flags. Stage names are mapped by sequence position rather than by name string because stage names are org-specific in CRM Service.

CRM Service Products map to Odoo product.product records. We extract Product2.Name as name, ProductCode as default_code, and Description as description. A corresponding product.template record is also created. If the CRM Service product has a standard price, it is set on the template.

CRM Service Line Items are not directly migratable as standalone records in Odoo because Odoo models line items in the context of a sale.order. We map line items to crm.lead optional lines if Odoo CRM is used without the Sale app. If the customer installs the Sale app during migration, line items are migrated as draft sale.order.line records linked to a draft sale.order record created per Opportunity.

CRM Service Campaigns map to Odoo utm.campaign records if the Marketing app is installed. Campaign member responses (Responded, Sent) are preserved as crm.tag values on the linked leads and opportunities. If the Marketing app is not installed, campaign names are stored as crm.tag records and applied to relevant crm.lead records.

CRM Service Tasks migrate to Odoo mail.activity records linked to the target res.partner or crm.lead. We extract Task.Subject as activity title, Task.Status as state (done vs open), Task.ActivityDate as date_deadline, Task.Priority as priority, and Task.Description as note. Completed tasks become activities with activity_type_id = 'mail.mail_activity_data_meeting' or a configured type; open tasks become planned activities. Owner resolution is via email match to res.users.

CRM Service Events migrate to Odoo calendar.event records. We extract Event.Subject as name, Event.StartDateTime as start, Event.EndDateTime as stop, Event.Location as location, and Event.IsAllDayEvent as allday. Attendees (EventWho) are resolved to res.partner records and added as calendar.attendee records. The linked WhatId (Account, Contact, or Opportunity) is mapped to the event's res_model and res_id.

CRM Service EmailMessage records migrate to Odoo mail.message records on the relevant res.partner (Contacts and Accounts) and crm.lead. Email body and subject migrate as message_body and subject fields. The From and To addresses are resolved to res.partner records where possible; raw email addresses are stored as a fallback. HasAttachment migrates as a flag for manual file attachment review.

CRM Service Notes migrate as Odoo mail.message records with subtype = 'note' on the parent record (Contact, Account, Opportunity). The note body transfers as plain text. Notes attached to multiple records in CRM Service are migrated to the primary parent and flagged as duplicates for manual review in Odoo.

CRM Service custom objects are migrated to Odoo custom models created via a custom module. We generate an ir.model entry, create the corresponding database table, and define fields via ir.model.fields. Lookup relationships to standard objects (Account, Contact, Opportunity) map to Odoo many2one fields pointing to res.partner or crm.lead. The Odoo module is installed in the destination database before any data is loaded. Custom object migration requires Odoo Community or Odoo.sh; Odoo Online SaaS does not allow custom module installation.

CRM Service Users are not migrated as records but resolved as references during migration. We extract all OwnerId values from Opportunities, Tasks, and Events and map them by email to existing Odoo res.users. Inactive CRM Service users without an Odoo counterpart are assigned to a migration placeholder user for admin reconciliation.

CRM Service Attachments (ContentDocument and Attachment objects) are exported to a staging directory with their parent record reference. We import them as Odoo ir.attachment records linked via res_model and res_id to the migrated parent record (res.partner, crm.lead). File size limits in Odoo are set by the hosting configuration; large files are flagged for manual handoff if they exceed the configured limit.