Migrate from Sugarcrm to Odoo CRM

Sugar Accounts map to Odoo res.partner records with partner_type = 'company'. The Account name becomes partner_name, website maps directly, and industry classifications map to Odoo's industry_id picklist. Address fields (street, city, state, postal code, country) migrate to res.partner address fields. Sugar Account relationships to Contacts are preserved as child res.partner records with partner_type = 'individual' linked via parent_id.

Sugar Contacts map to res.partner records with partner_type = 'individual' and a parent_id reference to the Company partner when a Sugar Account relationship exists. Multi-email addresses per Contact with Primary/Invalid/Opted Out flags migrate to res.partner email, email_normalized, and opt_out fields. We preserve the Sugar contact title and function fields in Odoo's function field on the partner record.

Sugar Leads map directly to Odoo crm.lead records. Lead status values (New, Assigned, In Progress, Converted, Recycled, Dead) map to Odoo stage_id values in the default sales team pipeline. Lead source maps to Odoo's source_id reference. Sugar lead_score and rating fields migrate to crm.lead as custom float and selection fields if present in the source data.

Sugar Opportunities map to Odoo crm.lead with type = 'opportunity'. The Opportunity name becomes crm.lead name, amount maps to planned_revenue, probability maps to probability (as integer percentage), and expected_close_date maps to date_deadline. Sugar's opportunity-to-Account linkage maps to Odoo's partner_id on the crm.lead record. Stage history from Sugar migrates as a note or custom activity log if the customer requires closed-won pipeline audit.

Sugar Revenue Line Items attach to Opportunities via Sugar's relationship model. In Odoo, line items belong to sale.order records, not directly to crm.lead. We create sale.order records (in draft Quotation state) for each Sugar Opportunity that has Revenue Line Items, preserving the line item product, quantity, unit_price, and revenue amount. The sale.order is linked to the partner_id from the Opportunity's Account. The Opportunity migrates to crm.lead with a Many2one reference to the generated sale.order if the customer wants a direct pipeline-to-quote link.

Sugar Quotes map to Odoo sale.order records with state = 'sent' or 'draft' depending on approval status in Sugar. Quote expiration_date maps to validity_date. Quote line items map to sale.order.line records attached to the sale.order. Approval workflow status flags from Sugar migrate as custom fields on the Odoo sale.order because Odoo's standard approval flow is configured per-team rather than per-record.

Sugar Products map to Odoo product.product records. ProductCode (hs_sku in Sugar) maps to product.product default_code. Sugar pricing fields (price, cost) map to Odoo's list_price and standard_price. Inventory fields in Sugar migrate to Odoo's qty_available and virtual_available if the destination Odoo instance includes the Inventory app.

Sugar Cases migrate to Odoo helpdesk.ticket if the destination Odoo instance includes the Helpdesk app. Case priority and status map to Odoo ticket priority and stage_id. Case conversation threads migrate as message_ids on the helpdesk.ticket using Odoo's mail.thread model, preserving the full support history. Account and Contact links from Sugar map to partner_id and attached partner_ids on the ticket.

Sugar Campaigns migrate to Odoo utm.campaign records. Campaign status, type, and budget migrate to corresponding fields. Sugar Campaign targets (the contacts or leads linked to a campaign) migrate as Odoo utm.mixin records linked to the campaign and the respective partner or lead. Note: Odoo's native campaign tracking is limited to UTM attribution in the Marketing app; the customer may need to configure additional campaign reporting via Odoo's custom report builder.

Sugar Tasks migrate to Odoo project.task records linked to the default CRM project or a project created for the migration. Task status, priority, due date, and assigned owner migrate directly. Tasks linked to Sugar Opportunities carry a Many2one to the crm.lead record in Odoo. Recurring tasks in Sugar are documented as a task pattern note because Odoo's recurring task model requires manual configuration in the destination.

Sugar Users map to Odoo res.users by email match. Active/inactive status migrates directly. Sugar team memberships and role assignments map to Odoo res.users groups (Sales / Administrator / Portal) and the crm.team membership records. Any Sugar User without a matching Odoo user record goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Sugar custom fields built via Studio and Module Builder require pre-creation in Odoo before migration. We audit every Sugar custom field during discovery, map the data type to the closest Odoo field type (char, text, integer, float, selection, many2one, many2many), create the field in the destination Odoo database via Odoo Studio or data migration script, and then include it in the CSV or XML-RPC import. Custom module objects from Sugar Module Builder map to Odoo custom model records if the customer has developer-mode access to create new models in Odoo.