Migrate from Sellsy to Odoo CRM

Sellsy bundles Individuals and Companies in a single Contact export with a type discriminator (personne morale / personne physique). We split the export by the type attribute before import. Each Individual maps to a res.partner record with style=contact. Name, email, phone, address, and custom field values migrate directly. Owner (sellsy staff) maps to Odoo User on the created_by_uid and write_uid fields. The customer chooses whether to create a parent company partner for each Individual or leave them standalone in Odoo.

Sellsy Corporation records map to res.partner with style=company. Corporate name, SIRENE or company registry data, address, revenue range, and industry classification migrate as partner fields. The linked staff owner maps to Odoo User. If the customer uses Sellsy's SIRENE enrichment, we preserve the official company identifiers (SIREN, SIRET) in a custom Char field on the Odoo partner record.

Sellsy Opportunities map directly to Odoo crm.lead records. Pipeline stages from Sellsy map to Odoo Stage names within the customer's Odoo CRM pipeline. The opportunity amount (montant) migrates to the expected_revenue or planned_revenue field; probability migrates as probability. Owner assignment uses email matching against Odoo Users. Closed Won and Closed Lost outcomes map to Odoo's won and lost stage values.

Each Sellsy pipeline becomes an Odoo CRM Stage within the customer's pipeline configuration. Stage order and probability percentages migrate from Sellsy. Odoo CRM's Kanban drag-and-drop stage management requires that we configure the stage sequence before opportunity records are imported so that the default stage is set correctly on insert.

Sellsy Invoices require the Odoo Accounting module to be installed and configured before import. Invoice header data (partner, date, number, due date) maps to account.move. Line items map to account.move.line with account_id resolved from the Odoo chart of accounts. Tax amounts, discounts, and SmartTags migrate to Tags on the move record. Invoice status (draft, sent, paid) maps to Odoo's move_state workflow. We flag that the Odoo Accounting app must be activated and a fiscal position / chart of accounts configured before this object imports.

Sellsy Orders map to Odoo Sale Order records. Product lines migrate as sale.order.line with product_id resolved via the Odoo product catalog. Order total, discount, and SmartTags transfer to the sale.order record. If Odoo Inventory is active, the stock.picking workflow is triggered after sale.order confirmation; we do not trigger confirmation during migration to allow the customer's team to review before fulfilment activation.

Sellsy Credit Notes (API support added in v2.86.0) map to Odoo account.move with type=out_refund. The linked original invoice reference migrates to the Odoo reconcile field if the original account.move record has already been imported; otherwise the reference is stored in a custom field for manual reconciliation after import. SmartTags transfer to Odoo Tags on the refund move.

Sellsy Products map to Odoo product.template (for product type and pricing) and product.product (for stock-tracked variants). Product code from Sellsy maps to the default_code field. Pricing rules migrate to Odoo pricelist items. The product catalog must be imported before Invoice and Order records to satisfy product_id foreign key constraints.

Sellsy Staff records map to Odoo res.users. We resolve by email match. Staff role and privilege information in Sellsy does not map directly to Odoo's access-control groups — the Odoo administrator assigns access rights based on the staff member's intended role in Odoo. We flag that Sellsy's Staff privilege model is not a direct equivalent of Odoo's user groups and document the mapping decision for the administrator.

Sellsy Tasks map to Odoo project.task records. Assignee, due date, status, and description migrate. If the customer does not have the Odoo Project app active, tasks migrate as a standalone CRM activity log against the related partner or opportunity record instead. The customer confirms the target app during scoping.

Sellsy Activities (appointments, calls, logged interactions) map to Odoo mail.message records linked to the parent crm.lead or res.partner. Call logs and meeting entries preserve timestamps and body content. Activity type (call, meeting, email) is stored as a custom field on the mail.message to maintain the original categorisation. We note that Odoo does not expose a native activity timeline per Contact the same way Sellsy does; the CRM Activity view in Odoo shows a subset of logged activities.

Sellsy SmartTags are a tagging layer applied to Invoices, Orders, and Credit Notes. In Odoo, Tags are available on crm.lead, account.move, and sale.order records via the mail.activity.mixin or ir_attachment tag system. We map SmartTags to Odoo Tags on the corresponding model. Where the destination Odoo model has no native Tags field, we create a custom Char field to hold the tag values, flagged during scoping for the customer's administrator to confirm.

Sellsy custom fields on Invoices, Contacts, and Corporations are read via GET /custom-fields and mapped to Odoo custom fields created in Odoo Studio or via the ORM before migration. Field type mapping follows: Sellsy text maps to Odoo Char, Sellsy number to Float or Monetary, Sellsy date to Date, Sellsy checkbox to Boolean. Custom fields that reference other Sellsy objects (e.g., a lookup from an Invoice to a Contact) are resolved to the corresponding Odoo record ID at migration time.