Migrate from SalezShark to Odoo CRM

SalezShark Leads map to Odoo crm.lead records with type = lead (not opportunity). The Lead's auto-assignment rules and conversion scoring from SalezShark do not transfer as executable logic — we preserve them as custom field values (ss_assignment_rule__c, ss_conversion_score__c) on the migrated crm.lead so the Odoo admin can reference them when setting up Odoo's Sales Team assign or lead scoring rules.

SalezShark Contacts map to Odoo res.partner records with company_type = person. Name, email, phone, mobile, and address fields map directly to their Odoo equivalents. The contact's parent_id is left null initially; it is populated after Account migration if the Contact belongs to a Company record in SalezShark.

SalezShark Accounts map to Odoo res.partner records with company_type = company. This is a critical schema difference: Odoo does not have a separate Account object. Company-level fields (industry, employee_count, annual_revenue) from SalezShark migrate to custom fields on the res.partner record. The Account's name becomes partner name, and the Account's domain is stored in the website field for deduplication reference.

SalezShark Contacts linked to an Account get their parent_id set to the Account's res.partner record. We resolve this lookup after Account records are created and before Contact import begins. Contacts without a parent Account in SalezShark import with parent_id null as standalone person partners.

SalezShark Opportunities map to Odoo crm.lead records with type = opportunity. The pipeline stage from SalezShark maps to Odoo's crm.stage via stage name matching; close date becomes date_deadline, and expected revenue maps to planned_revenue. Owner assignment resolves via email lookup against Odoo res.users.

SalezShark Pipelines map to Odoo stage groups. Each SalezShark pipeline becomes a named set of crm.stage records within Odoo. We export the pipeline stage names and ordering, then create corresponding Odoo stages with is_won = True on the closing stage and sequence ordering preserved. If the customer has multiple pipelines in SalezShark, we create separate stage sequences in Odoo and use crm.lead.team_id to route opportunities to the correct pipeline view.

SalezShark Tasks map to Odoo mail.activity records linked to crm.lead. Activity type (call, email, meeting, note) maps to activity_type_id; due date maps to date_deadline; status maps to active (True for open, False for done). Task notes migrate as mail.message records on the lead. We preserve the original creation timestamp as create_date on the activity record.

SalezShark Custom Fields available on Basic tier and above require Odoo custom field creation before data import. We export the custom field schema (name, data type, picklist values) from SalezShark's settings and create corresponding ir.model.fields on the appropriate Odoo model (crm.lead or res.partner) in Developer mode. Selection fields with picklist values migrate as selection fields; text fields migrate as char or text depending on length; numeric fields migrate as float or integer depending on precision.

SalezShark Document Management files attached to records migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. We export document metadata (filename, file type, upload date) and re-associate files to the migrated record. The actual binary files are exported from SalezShark's file storage and re-uploaded to Odoo's attachment store.

SalezShark Owner records map to Odoo res.users by email address. The migration user runs as a system admin in Odoo, and OwnerId on Opportunities and Tasks is resolved to res.users id. Any SalezShark Owner without a matching res.users record is flagged in the reconciliation report for the Odoo admin to provision before the final import batch.

SalezShark Workflow Automations (Professional tier) are exported as written configuration specifications describing trigger conditions, filter logic, and downstream actions. Odoo's equivalent is Automated Actions using ir.actions.server with server actions and cron triggers. We do not rebuild them as executable code in Odoo; we deliver the written spec and the customer or an Odoo partner rebuilds them post-migration.

SalezShark Custom Event Triggers (Professional tier) are exported as written specifications. Odoo's equivalent is ir.cron for scheduled triggers and ir.model.notify for model-level notifications. We deliver the configuration spec (trigger criteria, frequency, actions) for the Odoo admin to rebuild using Odoo's Scheduler/Automated Actions framework. These are not migrated as live code.

SalezShark Reports and Dashboards are exported as configuration metadata (report filters, field selections, grouping logic). We do not migrate report query results. The written spec includes report name, filter criteria, sort order, and chart type (if applicable) so the Odoo admin can recreate each report in Odoo's Reporting section or using Odoo Studio for custom reports.

SalezShark Campaign membership records (Contacts and Leads enrolled) migrate as crm.tag records on the relevant crm.lead, with tag category set to campaign. Email campaign content and templates do not migrate; we deliver a written campaign spec for the Odoo admin to rebuild in Odoo's Email Marketing app or a connected email platform.