Migrate from Salesboom to Odoo CRM

Salesboom Lead records map to Odoo crm.lead with type='lead'. All standard Lead fields (name, company, email, phone, status, source) migrate directly. We create Odoo crm.lead records before the opportunity migration so that any leads that convert during the Salesboom operational window are handled with a type check. Custom Lead fields migrate as char, text, or selection fields depending on Salesboom field type, using Odoo developer-mode ir.model.fields creation for Community or Studio for Enterprise.

Salesboom Account records map to Odoo res.partner with partner_type='company'. The Account Name becomes the partner's display name, billing and shipping addresses migrate to partner address fields, and industry and annual revenue map to custom res.partner fields. res.partner is the foundational object in Odoo; it must import before Contacts so that the partner_id lookup on Contact records is satisfied at insert time. We use external_id tracking to link Salesboom Account IDs to Odoo partner IDs for subsequent reference resolution.

Salesboom Contact records map to Odoo res.partner with partner_type='contact' and parent_id pointing to the mapped company-type partner. Email, phone, title, and function fields migrate directly. If the Contact's linked Account cannot be resolved (orphaned Contact), we create a placeholder company partner and flag it for the customer's admin to reconcile post-migration. Multi-address Contacts on a single Account require address record creation in Odoo's res.partner model with address_type fields.

Salesboom Opportunity records map to Odoo crm.lead with type='opportunity'. The Salesboom stage name maps to Odoo's crm.stage by name lookup; we configure the stage pipeline in Odoo before migration so that the target stage values already exist. Expected revenue, close date, probability (as a percentage), and lost-reason fields migrate as crm.lead expected_revenue, date_deadline, probability, and lost_reason fields respectively. The mapped crm.team (sales team) is resolved via owner email matching against the User migration.

Each distinct Salesboom Opportunity stage name becomes a crm.stage record scoped to the target crm.team pipeline. We extract the complete stage list from Salesboom during discovery, create the corresponding crm.stage records in Odoo with the same sequence order, and map probability percentages to stage_probability on each stage. Stages must be created in Odoo before any opportunity records insert so that the stage_id foreign key is satisfied.

Salesboom pipeline structures (if multiple pipelines exist on Professional or Enterprise) map to Odoo crm.team records. Each crm.team gets its own crm.stage sequence, and the opportunity records are assigned to the correct team via the team_id field. If Salesboom has one pipeline only, we create a default crm.team and assign all opportunities to it.

Salesboom Products map to Odoo product.template (or product.product for variants). The product name, SKU, list price, and cost price migrate directly. We create product.product variants during migration if the Salesboom product has size or color variants recorded as separate products. Price books in Salesboom map to Odoo's pricelist model; if multiple price lists exist, we create the corresponding pricelist records and assign them to the relevant partner records post-migration.

Salesboom Tasks migrate to Odoo project.task records. Subject, status, priority, due date, and description migrate directly. Assigned owner resolves by email to the Odoo res.users record. If the destination Odoo instance does not have the Project app installed, we fall back to creating Tasks as crm.activity log entries on the related crm.lead record. Recurring tasks from Salesboom are flattened into individual task records with recurrence metadata stored in a custom description field.

Salesboom Calendar Events migrate to Odoo calendar.event with start_datetime, stop_datetime, duration, location, and description preserved. Attendee mapping links to res.partner records via calendar.attendee records. If the mapped Contact or Account partner does not yet exist in Odoo at the time of event migration, the attendee is held in a staging table and re-resolved after the partner migration phase completes.

Salesboom Notes migrate to Odoo mail.message records with subtype='comment', linked to the parent crm.lead or res.partner via model and res_id fields. Note body text migrates as HTML content in mail.message body. If the parent record was not migrated (orphaned note), we attach the note to the related Account's partner record and flag it for reconciliation. Rich-text formatting is preserved as inline HTML within the message body.

Salesboom Cases migrate to Odoo helpdesk.ticket if the Helpdesk Management app is installed and licensed. Case status, priority, origin, and description map to ticket stage_id, priority, source_id, and description. If the Helpdesk app is not installed in the destination Odoo instance, Cases migrate as crm.lead records with a 'case' tag and a custom case_number field for audit trail. Auto-assignment rules and escalation workflows do not migrate; we document them in the automation inventory for admin rebuild.

Salesboom unlimited custom fields on Lead, Account, Contact, Opportunity, Case, and Task tabs migrate as Odoo custom fields. In Odoo Community, custom fields are created via developer mode (ir.model.fields). In Odoo Enterprise, Studio provides a no-code field creation interface. We extract field type from Salesboom (text, number, date, picklist, checkbox) and create the corresponding Odoo field definition before migrating any data. Custom picklist fields in Salesboom require Odoo selection field creation with the same key-value pairs.

Salesboom Owners map to Odoo res.users by email address. We extract the full owner list from Salesboom during discovery and match by email against the destination Odoo User table. Any Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision the User before record import resumes. Inactive Owners migrate as inactive Odoo Users with the original Salesboom owner ID stored in a custom field for audit.

Salesboom ERP add-on modules (Accounts Payable, HR Policy Tracking, Payroll, PTO Management, Expense Tracking at $10/user/month) have schemas distinct from CRM objects and require separate module-level migration scope. We extract transaction records from each licensed ERP module and map them to the corresponding Odoo app (account module for AP, hr module for HR, hr_payroll for Payroll, hr_leave for PTO). ERP module migration requires the corresponding Odoo app to be installed and configured in the destination instance; we flag any missing app requirements before migration begins.