Migrate from Star CRM to Odoo CRM

Star CRM Contacts map to Odoo res.partner records. Individual contacts are res.partner records with partner_type='contact'; company records are res.partner with partner_type='company'. We use the Star CRM contact email as the dedupe key during import. Name, email, phone, and address fields migrate directly. Custom contact properties discovered during live API scoping map to Odoo custom fields, which we pre-create as ir.model.fields before the import phase begins.

Star CRM Company records map to res.partner with partner_type='company'. Company name becomes the partner's name field, and address fields migrate as address fields on the partner. Individual Contacts from Star CRM that are linked to a Company are imported as child res.partner records with parent_id pointing to the company partner, preserving the Star CRM contact-company relationship. We resolve parent_id by matching on the company name or company ID during the import phase.

Star CRM Deals do not have an explicit Lead vs Opportunity distinction. We split at migration time using stage indicators: Deals in early stages (New, Qualified, or equivalent) map to Odoo crm.lead; Deals in later stages (Proposal Sent, Negotiation, Closed Won/Lost) map to crm.opportunity. We preserve the original Star CRM deal value in crm.lead and crm.opportunity expected_revenue. The split rule is documented during scoping and approved by the customer's admin before migration.

Star CRM pipeline stages map to Odoo crm.stage records in a named stage sequence. We create each Odoo stage record before migration, preserving the stage name, sequence order, and probability percentage from Star CRM. Stage-specific actions from Star CRM (stage-change automations) are documented in the automation inventory and do not migrate as code.

Star CRM Deal pipelines map to Odoo crm.team (sales team) records. We create a crm.team per Star CRM pipeline during the Odoo configuration phase, and assign the migrated crm.lead and crm.opportunity records to the appropriate team based on the Star CRM pipeline assignment. Team member assignments map from Star CRM Owner records.

Star CRM Activities (calls, emails, meetings, notes) migrate to Odoo mail.message records linked via model and res_id to the parent res.partner, crm.lead, or crm.opportunity. Activity type maps to Odoo's mail.message.message_type field (email, comment, notification). Date and time preserve from Star CRM. Call duration and disposition migrate to custom mail.message fields if present in the source. Email body content migrates as mail.message.body (HTML).

Where Star CRM distinguishes a separate Lead object from Contact, those records migrate to Odoo crm.lead as unqualified prospects. Lead source and any lead-specific custom properties migrate to crm.lead custom fields. Leads that have been converted to Contacts in Star CRM are handled as part of the Deal migration flow and do not duplicate as crm.lead records.

Star CRM Owners map to Odoo res.users by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Activity records and match by email against the destination Odoo instance's res.users table. Any Star CRM owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Star CRM owners migrate as inactive Odoo users if flagged for inclusion.

Star CRM Tags on Contacts or Deals migrate to Odoo crm.tag records. Tags on Contacts link to crm.lead and crm.opportunity via crm.tag.rel. Multi-select tags migrate as separate tag assignments per record. We create the crm.tag records before import and re-associate them during the data load phase.

Star CRM custom properties on Contacts, Companies, Deals, or Activities require pre-configuration in Odoo before migration. We perform live API discovery against Star CRM during scoping to enumerate all custom property names, data types, and values. We then create corresponding ir.model.field records in Odoo (as ir.model.fields) before the data import phase begins. Migration cannot load data into non-existent custom fields in Odoo, so this pre-configuration step is a prerequisite for any migration involving custom properties.

Star CRM exports attachments as individual files per record without a structured archive. We download all attachment files, build a manifest linking each file to its parent record ID, and re-upload them to Odoo as ir.attachment records linked via res_model and res_id to the correct res.partner, crm.lead, or crm.opportunity. This step adds time to projects with heavy attachment volume and requires the parent records to exist in Odoo before attachments can be associated.

Star CRM engagement history (combined calls, emails, meetings, and notes on a per-record basis) migrates as a chronological mail.message chain in Odoo. We preserve the original timestamp on each message, maintain the parent-child message threading where available in Star CRM, and link each message to the correct res.partner or crm.lead/opportunity by resolving res_id at migration time. Engagement history that spans multiple years may be scoped to a 24-month window during scoping to reduce migration volume.