Migrate from Zendesk Sell to Odoo CRM

Sell Leads migrate 1:1 to Odoo CRM Lead (crm.lead model). The sell lead_source property maps to Odoo's source_id (crm.lost_reason is for losses, not sources). We preserve all custom Lead fields as Odoo custom fields on crm.lead via Studio or a data migration script. The lead's owner maps to Odoo user_id by email match. Unqualified leads that were never converted in Sell remain as Odoo Leads for the sales team to work through in Odoo's Kanban pipeline view.

Sell Contacts require a schema split in Odoo. Each Sell Contact becomes an Odoo res.partner record with type='contact' linked to a parent Partner (type='contact' or 'invoice') representing the company. If the Sell Contact has an associated Company, we create that company as a res.partner with type='company' first, then create the Contact as a child Partner linked via parent_id. For contacts without a company, we create a standalone Partner record. Email, phone, address, and custom Contact fields map directly; Odoo's partner fields (street, city, country, website) accept the Sell Contact address payload.

Sell Companies map to Odoo res.partner records with type='company'. The company name becomes the Partner display name; the company domain maps to the website field for deduplication. We create the company Partner before any child Contact Partners so that the parent_id reference resolves at insert time. Industry, employee count, and custom Company fields migrate as custom fields on res.partner.

Sell Deals map to Odoo CRM Opportunity (crm.lead with type='opportunity'). The deal name becomes the Opportunity name, amount maps to planned_revenue, probability maps to Odoo's probability field, and stage maps to crm.stage via the pipeline's stage sequence. Loss reasons from Sell custom properties map to crm.lost_reason records created during schema setup.

Sell Pipelines are custom workflow containers that map to Odoo crm.team records. Each Sell Pipeline becomes a crm.team, and the pipeline's name becomes the team name. Team members (Sell Users) map to crm.team.member records by email match against res.users. If Odoo is self-hosted, team assignment uses crm.team member relations; on Odoo Online, the team field on crm.lead serves the same scoping.

Sell Stages are children of Pipelines and map to Odoo crm.stage records scoped to the corresponding crm.team. Stage ordinal position and win/loss flags migrate from Sell: stage.sequence sets Odoo stage order, and is_won maps to Odoo's onchange logic that advances to the Won stage. We configure stage names to match Sell naming conventions unless the customer requests renaming during scoping.

Sell Tasks migrate to Odoo mail.activity records linked to the target crm.lead (Opportunity) or res.partner (Contact/Company). Task fields map as follows: name becomes activity's summary, date_deadline carries the due date, completed_at maps to date_done, and status maps to Odoo's activity state (planned, today, overdue, done). Owner mapping uses email match to res.users for the user_id on the activity. Attachments on Tasks migrate as mail.message attachments via Odoo's ir.attachment model.

Sell Notes attached to Contacts, Deals, Leads, or Companies migrate as Odoo mail.message records with message_type='notification' linked to the target record via res_model and res_id. We preserve note body as HTML content in the message body. Parent record references resolve after both the parent record and its Odoo ID are known, so Notes import last in the activity phase. Tags on Notes migrate to Odoo message.main attachment_tags if the customer activates the Discuss module.

Sell Line Items attach to Deals and contain product name, quantity, unit price, and discount. Odoo treats Line Items as Sale Order Lines only when the Sale app is active and the Opportunity is converted to a Sale Order. We map Line Items to Odoo custom fields on crm.lead (line_item_product, line_item_qty, line_item_price) during the migration, and flag that if the customer activates Odoo Sale, these fields can be converted to Sale Order Lines via Odoo's Convert to Quotation action post-migration.

Sell Users (sales reps and admins) export with email, role, and territory. We match Sell Users to Odoo res.users by email. Any Sell User without a matching Odoo res.users account enters a reconciliation queue for the customer's admin to provision before Contact and Deal import resumes, because Owner fields on Opportunities and Contacts require a valid user_id in Odoo.

Sell custom fields on Leads, Contacts, Deals, and other objects map to Odoo custom fields created via Settings > Technical > Database Structure > Fields or via a data migration module. Custom field type resolution happens during scoping: text fields map to char or text, picklist fields map to selection, date fields map to date, numeric fields map to float or integer. We resolve Sell's numeric custom field IDs against their field keys before creating Odoo fields, and build a lookup table to apply values during the import phase.

Sell Tags applied to Contacts, Deals, and Leads map to Odoo crm.tag records. Each unique tag value creates a crm.tag record, and the tag association migrates as crm.lead.tag_rel entries linked to the Opportunity or Lead. Odoo tags are shared across Leads and Opportunities, matching Sell's tag model.

Sell call logs, call outcomes, and call duration migrate as Odoo mail.activity with activity_type_id set to phone. Call recording URLs (if stored as external links in Sell) migrate as ir.attachment records pointing to the original recording URL, attached to the same crm.lead or res.partner. Call disposition and outcome text map to custom fields on the activity if the customer has Odoo Studio active.