Migrate from PHP CRM to Odoo CRM

PHP CRM Contact records map to Odoo res.partner with partner_type set to 'contact'. The source email field maps to Odoo's email field; phone maps to phone. We resolve the parent Company relationship by matching the source company_name against the already-migrated res.partner records and populate parent_id accordingly. If the source contact has no company, the record is imported as an individual partner without a parent_id. Address fields (street, city, state, country, zip) map via Odoo's partner address fields.

PHP CRM Company records map to Odoo res.partner with partner_type set to 'company'. The company_name field maps to Odoo's name field on the partner record. We import Companies first as parent entities before any Contact import so that the parent_id lookup is satisfied at Contact insert time. Company-level custom fields from PHP CRM map to custom res.partner fields in Odoo. If the source Company has no associated address, we set address fields to empty rather than null to satisfy Odoo's address format expectations.

PHP CRM Deal records map to Odoo crm.lead (the opportunity model). The source dealstage maps to an Odoo crm.stage record on the crm.lead.pipeline. We resolve partner_id from the source deal's linked Company or Contact at migration time. The deal's expected_close_date maps to Odoo's date_deadline field; amount maps to Odoo's planned_revenue field. Type on crm.lead is set to 'opportunity' during import. Owner assignment maps to Odoo user_id via email matching against res.users.

PHP CRM Pipeline definitions map to Odoo crm.lead.model records. Each source pipeline becomes a separate crm.lead.model in Odoo with a name matching the source pipeline name. We configure the model's stage_ids to reference the migrated crm.stage records. The pipeline's sequence order is preserved via Odoo's sequence field on the model. If the source deployment has a single default pipeline, it maps to the standard Odoo CRM pipeline without configuration changes.

PHP CRM Pipeline Stage records map to Odoo crm.stage records attached to the corresponding crm.lead.model. Stage name, sequence order, and probability percentage migrate from the source stage values. Odoo requires stage records to belong to a specific pipeline model; we resolve the parent pipeline before inserting each stage. If a source stage has no Odoo equivalent (e.g., custom named stages with no close/won equivalent), we flag them for manual Odoo stage creation before migration resumes.

PHP CRM Task records map to Odoo project.task linked to the default crm_project if the task is CRM-related. The source due date maps to date_deadline; assignee maps to user_id via email matching. Task status (open/closed) maps to Odoo's kanban_state field. If the source task has a linked Deal or Contact, we resolve the destination crm.lead or res.partner ID and set the task's project_id and partner_id accordingly. Task description maps to the Odoo description field as plain text.

PHP CRM Note records attach free-text content to any entity. We migrate Notes as Odoo mail.message records with message_type set to 'comment'. The WhoId (Contact or Company) and WhatId (Deal) are resolved to destination res.partner and crm.lead IDs, and the message is linked via mail.message.model and mail.message.res_id. Author is set to the migrating Odoo user who owns the note assignment. Note body migrates as HTML-formatted plain text without image attachments unless the source provides a file path accessible during extraction.

PHP CRM Activity records (calls, emails, meetings) with timestamps and outcome data map to a combination of Odoo mail.message and crm.activity. Call activities map to mail.message with message_type='comment' and a custom call disposition field; the source call duration and outcome map to custom crm.activity fields if defined. Email activities map to mail.message with attachments preserved as ir.attachment records linked via mail.message. Meeting activities map to calendar.event records in Odoo's calendar module if available, or to mail.message if calendar is not in scope. We enumerate the actual activity field schema present in the source PHP CRM instance during discovery since PHP CRM activity schemas vary by deployment.

PHP CRM user-defined custom fields on any standard object map to Odoo ir.model.fields records created via Odoo Studio or direct Python model definition. Each custom field requires a separate Odoo field creation step before the associated record import begins. We enumerate all custom fields during mandatory discovery, capture the field type (text, number, date, checkbox, dropdown) from PHP CRM, and map to the equivalent Odoo field type (char, text, float, datetime, boolean, selection). Fields with no Odoo equivalent are flagged for manual field creation before migration resumes.

PHP CRM Owner records on Deals, Tasks, and Contacts map to Odoo res.users by email matching. We extract every distinct owner referenced across all objects, match against the destination Odoo res.users table, and flag any owner without a matching user for admin provisioning. Owner assignment on crm.lead maps to Odoo's user_id; task assignment maps to project.task user_id. Active/inactive status from the source is preserved in the Odoo user record. The customer's Odoo admin provisions any missing users before record import resumes.

PHP CRM Tags are per-instance label vocabulary that map to Odoo crm.tag records. We extract the full tag taxonomy from the source, create matching crm.tag records in Odoo, then link them to the appropriate crm.lead records via crm.lead.tag_rel at migration time. If the source tag vocabulary is large (50+ tags), we recommend the customer audit the taxonomy before import to remove deprecated labels. Tags with no clear Odoo equivalent are flagged for customer review.

PHP CRM stores file attachments on the local filesystem (self-hosted) or cloud storage path, not through a documented API endpoint. We cannot programmatically extract attachments. We export the attachment directory to a local path for the customer's review and advise re-uploading manually via Odoo's document management interface or using Odoo's bulk file import tools post-migration. This gap is documented explicitly in the migration scope.