Migrate from Soffront to Odoo CRM

Soffront Contacts map to Odoo res.partner records with partner_type set to contact. The Contact's email, phone, address, and lifecycle stage fields map to corresponding Odoo partner fields. Group assignments and tags from Soffront migrate as Odoo tags on the partner record. We resolve the Account-Contact relationship by creating parent Account partners first, then linking Contact partners to them via the parent_id field.

Soffront Accounts map to Odoo res.partner records with partner_type set to company. Industry, size, and custom properties from Soffront become custom fields on the Odoo partner. The Account-Contact hierarchy is preserved by linking child Contact partners to the parent Company partner. Company domain (from the account website) becomes the partner's website field and is used as a dedupe key during import.

Soffront Deals map to Odoo crm.lead records in the Opportunities kanban. Deal stage names are reconciled against Odoo's stage palette during scoping; if Soffront stages do not map directly to Odoo stage values, we create custom stage names in the Odoo sales team pipeline. Deal amount, expected close date, owner, and custom fields migrate directly. Pipeline-to-sales-team assignment maps to Odoo's team_id field on the lead.

Each Soffront Deal pipeline becomes an Odoo sales team with its own kanban stage sequence. Stage names and probabilities from Soffront are mapped to Odoo stage definitions in the corresponding sales team. We configure stage sequence ordering and probability percentages in Odoo CRM settings before migration to align with the Soffront pipeline behavior the team expects.

Soffront Activities map to Odoo mail.message records linked to the res.partner or crm.lead record. Call activities with duration and disposition data migrate as mail.message with subtype note; email activities migrate as mail.message with subtype comment; meetings become calendar.event records linked to the opportunity or partner. Task activities migrate as Odoo project.task records within the CRM project if task tracking is enabled, or as note records if the team uses Odoo's lightweight task model. Activity timestamps and owner assignments are preserved.

Soffront Knowledge Base articles migrate to Odoo Documents as document records with the article body as the document content and the article title as the document name. Soffront KB categories are re-created as Odoo Documents folders, and we tag each article with the original category name using Odoo's document tags. If Odoo's Documents app is not enabled, we fall back to using the CRM Notes feature with a structured tag prefix matching the original KB category. The category re-creation step must complete before article imports to establish the folder hierarchy.

Soffront Projects map to Odoo Project records with their status, milestones, assigned managers, resources, and due dates. Soffront project tasks become Odoo project.task records within the corresponding project. We map project-level custom fields to Odoo custom field definitions on the project.model. The migration includes task hierarchy and sub-task relationships where Soffront supports them.

Soffront Tickets migrate to Odoo Helpdesk tickets if the Helpdesk app is enabled in the destination Odoo instance. Ticket status, priority, assignee, and conversation history map to Odoo helpdesk.ticket fields. Soffront ticket type assignments migrate as ticket team or category assignments in Odoo Helpdesk. Conversation threads migrate as mail.message records linked to the ticket. If Helpdesk is not in scope, tickets migrate as project.task records in a dedicated support project.

Soffront custom object types are inspected during discovery, and we create corresponding Odoo custom models (x_<objectname> in the ir.model table) with all custom fields defined before data import. Lookup relationships from Soffront custom objects to standard objects are replicated as Odoo many2one fields to the mapped res.partner or crm.lead model. Picklist and multi-select fields become Odoo selection and many2many fields respectively.

Soffront custom fields on Contacts, Accounts, Deals, and Activities require a per-instance field inventory because field names differ between Soffront organizations. We capture the Soffront field name, field type, and picklist values during discovery, then create matching Odoo custom fields on the corresponding model (res.partner for Contact/Account, crm.lead for Deal, mail.message for Activity) before import. Picklist values are mapped individually; any Soffront picklist value without a direct Odoo equivalent is flagged for the customer's admin to approve a mapping or new Odoo value.

Soffront Groups organize records for access control and segmentation. We map group memberships to Odoo user groups via the res.groups model. If Odoo's Sales Team model is used for territory or team-based access, we create sales teams and assign members accordingly. Group-based permissions migrate as Odoo group assignments per user, with the understanding that Odoo's permission model (record rules and access rights groups) differs architecturally from Soffront's group model.

Attachments linked to Contacts, Deals, Tickets, and Projects are exported from Soffront and re-uploaded to Odoo as ir.attachment records linked to the corresponding res.partner, crm.lead, helpdesk.ticket, or project.task. File size limits and storage location depend on the destination Odoo instance's attachment storage configuration (database or file system). We flag any Soffront attachment exceeding 25 MB for manual review because Odoo attachment processing may require configuration changes for large files.