Migrate from SuperOffice CRM to Odoo CRM

SuperOffice Contact maps to Odoo res.partner with type = 'person'. The SuperOffice Contact's firstname and lastname concatenate to the Partner name field in Odoo, and we preserve the original split by storing firstname and lastname in custom fields partner_firstname__c and partner_lastname__c. Email, phone, and address fields map 1:1. The SuperOffice associate (Owner) maps to Odoo User by email resolution before Contact import begins.

SuperOffice Company maps to Odoo res.partner with type = 'company'. The Company name becomes the Partner name, and domain/website maps to Odoo's website field. The Company-Contact link table is preserved by setting the parent_id on the Contact Partner record to point to the Company Partner record after both are imported.

SuperOffice Sale maps to Odoo crm.lead with type = 'opportunity'. The SuperOffice sale stage (lost/won/stage) maps to Odoo stage_id within the assigned crm.team. Amount and currency migrate to planned_revenue and currency_id. The SuperOffice SaleType and its linked stage list map to a specific Odoo crm.team and its stage sequence. Automations on sale stage changes do not migrate.

SuperOffice Quote maps to Odoo sale.order. The Quote is linked to the corresponding Sale (Opportunity) via the Odoo crm.lead's opportunity_id reference on sale.order. Pricing, line items, and terms migrate directly. Note that Odoo sale.order does not support a multi-version quote model natively.

SuperOffice QuoteAlternative records (secondary proposal versions with different pricing, technology, or terms) do not have a native Odoo equivalent. We designate the primary QuoteAlternative as the main sale.order and store secondary QuoteAlternative records as a JSON blob in a custom field quote_alternatives__c on the sale.order. We include line item detail, pricing, and the alternative name in the JSON. The post-migration handoff document lists every QuoteAlternative with its parent Sale so the Odoo admin can decide whether to create separate sale.order records for each.

SuperOffice Project maps to Odoo project.project. The ProjType and ProjStatus list values map to Odoo project tags or custom stage fields. Project-type-status links are preserved as custom fields on the Odoo project record. Note that Odoo's native Project app is a separate app install from CRM; we confirm CRM app is active before migration and flag if the Project app is not installed.

SuperOffice Activities (calls, tasks, appointments) map to Odoo crm.activity log records attached to the corresponding crm.lead. Call duration, disposition, and completion status migrate to custom fields on crm.activity. Meeting details (start/end time, location) map to the crm.activity description or a custom field. Activity associations to other records (Projects, Sales) are reconstructed via the Odoo model and res_id references after parent records are loaded.

SuperOffice Selections are named dynamic lists of Contacts, Companies, or Sales. Odoo has no native equivalent dynamic list concept. We export each Selection as a set of tags applied to the corresponding Partner records (Contacts and Companies) and produce a written inventory listing every Selection name, its criteria (e.g., all Contacts in the Nordics region with open Sales), and the Odoo tag name assigned. The Odoo admin recreates the dynamic filter using Odoo's native domain-based filter or a saved filter group.

SuperOffice documents stored in the so_arc archive export as binary blobs with filename, MIME type, and create date metadata. We import them as ir.attachment records linked to the parent model (res.partner, crm.lead, project.project) via res_model and res_id. Document-link relationships that exist in SuperOffice are reconstructed via the attachment's res_model and res_id fields. Large document archives may require a staged import with throttling.

SuperOffice userDefined fields on Contacts, Companies, Sales, and Projects map to Odoo custom fields created on the target model via the Settings > Technical > Custom Fields interface. Dropdown lists from SuperOffice map to Odoo selection fields with the same option values. We create the destination custom field schema before any data import so that the import pipeline can write values directly into typed fields rather than storing them in a catch-all note field.

SuperOffice Users (associates) map to Odoo res.users by email resolution. The SuperOffice Role (module-level access rights) does not map directly to Odoo's access rights model; we note the role name and access level in the handoff document for the Odoo admin to assign via Odoo's Access Rights tab. Inactive or archived SuperOffice users map to Odoo portal users or are excluded based on the customer's inclusion criteria.

SuperOffice Tags applied across Contact, Company, Sale, and Project objects map to Odoo res.partner.category (Tags app). Tags on Sales and Projects map to crm.tag or project.tag if those apps are installed. We export the tag taxonomy from SuperOffice and create the equivalent Odoo tags before any tagged records are imported. Duplicate tag names are deduplicated by name match.

SuperOffice SaleType and its linked stage list table (stage name, order, probability) map to Odoo crm.stage records within the destination crm.team. Stage probability percentages migrate to Odoo's probability field. The SuperOffice stage list table is exported as a configuration object and applied during schema setup. We configure stage names to match SuperOffice labels so that the sales team's muscle memory is preserved as much as the data model allows.

The SuperOffice associate table linking Contact to Company is a critical lookup dependency. We sequence Companies (type=company Partner) first in the import order, then Contacts (type=person Partner) with parent_id resolved to the Company Partner record. This ensures that when Contact records are imported into Odoo, the Company relationship is established at insert time rather than requiring a follow-up update pass.