Migrate from Sugar Sell to Odoo CRM

Sugar Accounts map to Odoo res.partner records with customer=1 flag. The Account name maps to partner name, website to website field, and industry to the industry_id custom field we create in Odoo. Sugar's billing_address and shipping_address become Odoo street, city, state_id, zip, and country_id fields. We run a dedupe check against existing Odoo Companies before import to flag any potential duplicates from prior Odoo pilots.

Sugar Contacts map to Odoo res.partner records. Since Odoo uses a single partner model for both Leads and Customers, we set customer=1 on Contact-derived records and customer=0 on Lead-derived records. The Contact's parent_id links to the migrated Account as a Company. We preserve the Contact title, email, phone, and address fields directly. Sugar's account_id foreign key resolves to the migrated Company partner.id at migration time.

Sugar Leads map directly to Odoo res.partner records with customer=0. Sugar's lead_status, lead_source, and status lifecycle fields map to Odoo's stage_id and team_id. We preserve the original Sugar Lead status values in a custom field sugar_original_status__c for audit. Any Lead converted to Contact in Sugar before migration retains that converted Contact as a customer=1 partner record in Odoo.

Sugar Opportunities map to Odoo crm.lead records with type='opportunity'. The opportunity name maps to name, amount maps to planned_revenue, date_closed maps to date_deadline, and sales_stage maps to stage_id. We create Odoo CRM stages that correspond to the Sugar pipeline stages before migration. The probability percentage migrates as a custom float field since Odoo's stage probabilities are tied to stage settings rather than per-record.

SugarBPM workflow definitions (module triggers, conditional routing, alert sequences) are migrated as named records in a written inventory document. We do not execute them as Odoo Studio automations because the trigger-event model differs between platforms. The inventory lists each SugarBPM workflow with its trigger module, conditions, actions, and a recommended Odoo Studio Automation equivalent. The customer's admin or an Odoo partner rebuilds them post-migration.

Sugar Quotes map to Odoo sale.order records in draft state. Quote line items map to sale.order.line records linked to the sale.order. Sugar's Product_bundle records resolve to sale.order.line entries with product_id, product_uom_qty, and price_unit. Tax and discount fields migrate to Odoo's tax_id and discount fields. Signed quote PDFs migrate as Odoo attachments on the sale.order record.

Sugar Product Catalog entries map to Odoo product.product records with type='product' or 'service' as appropriate. Sugar's product_types and manufacturers map to Odoo product.category records we create before migration. Product pricing migrates to Odoo list_price and standard_price. Sugar's cost field maps to Odoo's standard_price for margin calculations.

Sugar Call activities map to Odoo crm.lead log notes via the mail.message model linked to the opportunity. We preserve call duration, disposition, and the original timestamp in the message body and create_date. Odoo does not have a native call activity object at the CRM level, so call history appears as logged notes in the opportunity chatter rather than a structured call record.

Sugar Meetings map to Odoo calendar.event records with start, stop, duration, and location fields preserved. Meeting attendees resolve to Odoo res.partner records via the calendar.attendee model. The calendar.event is linked to the relevant crm.lead opportunity via the res_id and model fields in mail.message for activity timeline visibility.

Sugar Tasks map to Odoo project.task records under the CRM project's task list. Task status, priority, due date, and description migrate directly. Task assignments resolve by email match to Odoo res.users records. For CRM-only migrations without Odoo Project, we link tasks to the crm.lead record via project_id=false and res_model='crm.lead'.

Sugar Notes with file attachments migrate to Odoo note.note records with body text and attachment links. File attachments are extracted from the Sugar file system or API response, re-uploaded to Odoo as ir.attachment records linked to the note, and the note.note record references the attachment. Plain-text notes migrate as note.note body content.

Sugar custom fields defined in vardef PHP files are extracted during discovery via direct file access or ModuleLoader package analysis. We parse the vardef field name, type, label, required flag, and dropdown options. In Odoo, we create equivalent fields using the Settings > Technical > Fields interface or direct database insert into ir_model_fields. This step happens before any data migration to ensure target fields exist at import time. Sugar custom modules require separate module analysis beyond standard field mapping.

Sugar Users map to Odoo res.users by email match. Team membership from Sugar (which controls record-level access) maps to Odoo crm.team membership. We extract user status (active/inactive) and recreate the hierarchy in Odoo before any record migration begins because OwnerId references on Opportunities and Contacts must resolve at insert time.

Sugar Tags stored as string values on Leads, Contacts, and Opportunities migrate to Odoo crm.tag records. We extract the full tag vocabulary, create matching tag records in Odoo, and link them to migrated crm.lead records via the crm.tag.rel junction table. Tag-based segmentation is preserved for reporting and filtering in Odoo's CRM pipeline view.

Sugar Cases migrate to Odoo project.task records under a dedicated support project if the customer uses Odoo Project, or to helpdesk.ticket if Odoo Helpdesk is installed. Case priority and status map to Odoo priority and stage_id. The mapping approach is confirmed during scoping based on which Odoo apps are active in the destination environment.