Migrate from Sales Infinite to Odoo CRM

Sales Infinite Contact records map directly to Odoo res.partner with partner_type set to 'contact'. The Sales Infinite name field splits into firstname and lastname using Odoo's name splitting logic. Email, phone, mobile, street, city, state_id, zip, and country_id map to Odoo's typed fields. Owner assignment (salesperson) maps to Odoo user_id via email lookup against res.users. Any Sales Infinite custom properties on Contact require schema discovery before mapping: picklist values map to fields.selection, free-text to fields.char, numeric to fields.float, and date to fields.date. We create the custom field definition in Odoo via Studio or Python migration before importing data.

Sales Infinite Account records map to Odoo res.partner with is_company=True and partner_type='contact'. Industry, annual revenue, type (customer/prospect/vendor), and website migrate to industry_id, annual_revenue (custom fields.float), company_type, and website respectively. Account records must import before Contact records so that each Contact's parent_id (company link) resolves at insert time. We extract the domain from the Account website field and use it as a dedupe key if multiple Contacts share the same company.

Sales Infinite Opportunity records map to Odoo crm.lead. The opportunity name, amount, probability, expected_close_date, and description migrate directly. StageName maps from Sales Infinite's stage labels to Odoo's crm.stage sequence values. Priority (high/medium/low) maps to priority. Partner_id is resolved by looking up the Contact or Company name in res.partner. For Odoo editions without a separate Lead object active, all Opportunity records land as crm.lead with type='opportunity'; if the Lead module is active, unqualified records (no prior engagement) can land as type='lead' for routing.

Sales Infinite Lead object may be gated to certain tiers. Where Sales Infinite Lead records exist, we split based on Lead_Status: unqualified leads with no associated Opportunity map to Odoo crm.lead with type='lead' and stage_id set to the first stage in the pipeline. Qualified leads with a linked Opportunity map to crm.lead with type='opportunity' and are merged with the Opportunity mapping. Lead_Status is preserved as a custom field (x_lead_status as fields.selection or fields.char depending on value count) for reporting continuity. If the Odoo instance does not have the CRM Lead module activated, all Leads merge into res.partner as new Contact records.

Sales Infinite pipeline configuration (stage names, probabilities, sequence order, and pipeline-specific stage sets) is configuration data extracted during scoping. We reconstruct the pipeline in Odoo by creating crm.stage records with the matching name, probability (probability as integer percentage), and sequence values. If Odoo's single-pipeline constraint applies (default installation without multi-pipeline module), we use a tag-based workaround: pipeline names become tags on crm.lead, and each pipeline's stages become sequential stage values that the customer manages within a single pipeline view.

Sales Infinite email engagements map to Odoo mail.message records. The email subject becomes message_subject, body migrates as HTML, and date maps to date. We link each message to the correct res.partner via model='res.partner' and res_id pointing to the migrated Contact ID. If the email references an Opportunity, we link via mail.message.subtype with crm.lead as the model. Thread ordering is preserved by date. Attachments on emails download individually via Sales Infinite API and re-upload as ir.attachment records linked to the mail.message.

Sales Infinite call engagements map to Odoo crm.phonecall (if the voip module is installed) or mail.activity with activity_type='phonecall'. Call duration, disposition outcome, and recording URL migrate as custom fields on crm.phonecall or as extra fields on mail.activity. The crm.phonecall.name is set to the Contact name and call date. ActivityDate preserves the original timestamp for chronological ordering. If crm.phonecall is not available in the destination Odoo edition, calls fall back to mail.activity with a phonecall-specific activity type.

Sales Infinite meeting engagements map to Odoo calendar.event. Start datetime, end datetime, location, and meeting title migrate directly. We create calendar.attendee records linking the event to the res.partner records of invited Contacts. If the meeting is linked to an Opportunity, we store the crm.lead ID in the event's description or a custom many2one field. Meeting body and agenda migrate as event description. If the calendar module is not installed in the Odoo destination, we fall back to mail.activity records with activity_type='meeting'.

Sales Infinite task engagements map to Odoo mail.activity with activity_type='task'. Task subject becomes activity summary, description migrates as note, due_date maps to date_deadline, and status (complete/pending) maps to activity state. User assignment migrates by resolving Sales Infinite owner email to Odoo res.users id. Activities linked to Opportunities attach via res_id pointing to the crm.lead id.

Sales Infinite Notes (engagement type NOTE) map to Odoo note.note records. Note title (first line or truncated body) becomes note.note name; the full note body migrates as HTML content. We link the note to the correct res.partner or crm.lead via res_model and res_id. The note's creation date and author map to create_date and create_uid for audit trail. If the note module is not active in Odoo, notes fall back to mail.message with no envelope (plain message on the record thread).

Sales Infinite Product records map to Odoo product.product with product_tmpl_id resolved as the template. Product name, SKU (product_code), list_price, standard_price, and description migrate directly. Product category maps to product.category via name lookup. We create the product.template records before product.product variants so that the template link is satisfied at insert. If the Odoo instance uses product variants, each Sales Infinite product variant maps to a separate product.product linked to the same template.

Sales Infinite Owner records (salespersons and team leads) map to Odoo res.users by email address lookup. Every record carrying an Owner assignment — Contact, Account, Opportunity, Activity — references the user_id on the migrated Odoo record. Any Sales Infinite Owner with no matching res.users in the destination Odoo instance enters a reconciliation queue for the customer's admin to provision the user before record import continues. Owner team membership maps to crm.team via user_ids on the team record.

Sales Infinite team structures map to Odoo crm.team records. Team name, description, and member list (user_ids) migrate directly. If a Sales Infinite team has a designated lead or manager, that user becomes the team_lead_id on crm.team. Teams without a direct Odoo equivalent map to an Odoo User group, with team membership handled via res.users groups.

Sales Infinite custom properties on any standard object are discovered during schema audit: we capture field name, data type, picklist values, default values, and required status. For each custom field we create the corresponding Odoo ir.model.fields record with the appropriate field type — fields.selection for picklists, fields.char for short text, fields.text for long text, fields.float or fields.monetary for numeric values, fields.date or fields.datetime for dates, fields.many2one for relational fields, and fields.boolean for flags. Custom field order and grouping are documented for Odoo Studio reconfiguration by the admin post-migration.