Zendesk Sell to Odoo CRM migration
We migrate Leads, Contacts, Deals, Tasks, and custom fields from Zendesk Sell into Odoo CRM with the Partner split resolved upfront, pipeline-to-stage mapping configured before any records write, and Odoo's XMLRPC API used to handle large batch imports with parent-record lookup resolution across the Odoo object graph.
FlitStack AI migrates leads, partners, partner type=companies, opportunities and teams from Zendesk Sell to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Zendesk Sell to Odoo CRM?
Moving from Zendesk Sell to Odoo CRM is a migration driven by Sell's August 31, 2027 sunset deadline combined with Odoo's appeal as an open-source all-in-one business suite.
Read the full summary
The structural difference that shapes the entire migration is Odoo's Partner model: Sell maintains separate Contact and Company objects while Odoo collapses both into a single Partner record with a Contact Type field distinguishing internal contacts (company employees) from individual customers and suppliers. We resolve that schema split at scoping, map Sell's Pipeline and Stage hierarchy to Odoo's crm.team and stage configuration, and write all records through Odoo's XMLRPC API with batch chunking and exponential backoff on 429 responses. Sequences, workflows, and automation state do not migrate; we deliver a written inventory of every active Sell automation for the customer's team to rebuild in Odoo's Studio or Action rules framework. Custom fields migrate as Odoo custom fields on the equivalent model, and we flag any field types that require Odoo schema changes before import.
Lead → Lead (crm.lead)
Sell Leads migrate 1:1 to Odoo CRM Lead (crm.lead model).
How it maps
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.
Contact → Partner (res.partner)
Sell Contacts require a schema split in Odoo.
How it maps
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.
Company → Partner (res.partner) type=company
Sell Companies map to Odoo res.partner records with type='company'.
How it maps
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.
Deal → Opportunity (crm.lead)
Sell Deals map to Odoo CRM Opportunity (crm.lead with type='opportunity').
How it maps
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.
Pipeline → Team (crm.team)
Sell Pipelines are custom workflow containers that map to Odoo crm.team records.
How it maps
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.
Stage → Stage (crm.stage)
Sell Stages are children of Pipelines and map to Odoo crm.stage records scoped to the corresponding crm.team.
How it maps
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.
- LeadLead1:1
- ContactPartnersplit
- CompanyPartner type=company1:1
- DealOpportunity1:1
- PipelineTeamtransformed
- StageStagetransformed
+ 7 more in the mapping below
How Zendesk Sell and Odoo CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Zendesk Sell | Odoo CRM |
|---|---|---|
| Object model | Separate Contact and Company as distinct objects | Single Partner (res.partner) with Contact Type field toggling between individual and organization |
| Revenue object | Deal with standalone Pipeline and Stage hierarchy | CRM Opportunity with Stage inside a crm.team (pipeline equivalent) |
| Line items | Separate Line Items attached to Deal | Sale Order Line (requires Sale app activated; or stored as custom Opportunity fields) |
| Custom objects | Custom fields supported on all objects at Professional tier | Custom fields via Odoo Studio on all models; custom modules for new objects |
| Pricing model | Per-user: $19 Team, $49 Professional | Per-user: $24.90 Standard, $37.40 Custom; free tier with one app |
| Activity history | Native calls, emails, meetings, tasks with recording links | Activities (log note, phone call, meeting, task) with Portal attachments |
| Automation | Sequences and Workflow automation with cadence state | Action Rules (record-triggered), Server Actions, and Automated Actions via Studio |
What to watch for in a Zendesk Sell to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Sell sunset is August 31 2027 with data deletion
Zendesk's Service Data Deletion Policy triggers deletion of all Sell data on the sunset date or subscription end, whichever arrives first.
How we handle it
Organizations that begin migration after Q1 2027 face compressed timelines, specialist unavailability, and risk of data loss if the export phase exceeds available time. We treat every Sell migration as time-bound and schedule discovery calls targeting a migration start at least nine months before the deadline. Customers on Sell Professional or Enterprise should begin scoping now.
Odoo Partner model requires Contact-Company split
Odoo's res.partner is a single model representing both individuals and organizations.
How we handle it
Sell maintains separate Contact and Company objects, which must be split during migration: each Sell Contact with an associated Company creates a company Partner (type=company) first, then a contact Partner (type=contact) with parent_id pointing to the company. Contacts without a company create standalone Partners. Migrations that skip this design step create orphaned Partners with no organizational hierarchy, breaking Odoo's address sharing and company-level reporting.
Sequences and cadence state do not migrate
Sell Sequences store enrollment state, step history, and reply tracking tied to individual Contacts.
How we handle it
This data is not exportable as a discrete object and Odoo has no equivalent cadence-tracking model in its standard CRM app. We export Sequence metadata (name, step count, cadence type) as a reference document and flag active sequences for rep-level rebuild in Odoo Action Rules or a third-party sales engagement module. Enrollment state, reply rates, and step resume points are not migratable.
Odoo self-hosted requires XMLRPC access and server configuration
Odoo Online uses a REST-like API via XMLRPC against the database directly, which requires valid credentials with API access rights.
How we handle it
Self-hosted Odoo deployments additionally require network access to the server's XMLRPC endpoint, the database name, and appropriate user access levels for the migration user. We resolve Odoo API credentials during discovery, configure the migration user with appropriate access rights, and implement batch chunking with retry logic for large-volume writes.
Sell Line Items require Odoo Sale app activation
Sell Line Items (product, quantity, price, discount attached to Deals) do not have a native Odoo CRM equivalent outside of the Sale module, where they become Sale Order Lines.
How we handle it
We store Line Item data as custom fields on crm.lead during migration and flag that if Odoo Sale is activated, the customer's admin can use Odoo's Convert to Quotation feature to create proper Sale Order Lines from the Opportunity. Without Sale activated, the Line Item data is preserved but not linked to Odoo's product catalog.
How the migration runs
Discovery and Sell sunset timeline assessment
We audit the Zendesk Sell account across tier (Team or Professional), custom fields, pipeline count, active Sequences, active Workflows, and engagement volume.
What this step covers
We pair this with Odoo deployment type identification: Online (SaaS),.sh (PaaS), or self-hosted on-premise. The discovery output is a written migration scope with a Sell sunset gap analysis: if the migration start date is less than nine months from August 31 2027, we flag the account as urgent and compress the staging window.
Odoo schema design and Partner split rule definition
We design the Odoo destination schema before any data moves.
What this step covers
This includes creating crm.team records for each Sell Pipeline, crm.stage records with correct sequence for each Sell Pipeline's stages, crm.tag records for existing Sell tags, and custom fields on crm.lead and res.partner to accommodate all Sell custom field values. The Contact-Company split rule is defined here: we document whether Contacts without a Company in Sell create standalone Partners or are merged into existing company Partners by domain match.
Sandbox migration and data quality audit
We run a full migration into an Odoo staging environment (copy of the destination database) using production data volume.
What this step covers
The customer audits record counts (Leads in, Opportunities in, Partners in, Activities in), spot-checks 25-50 records against Sell source, and validates that Contact-Company hierarchy resolves correctly. Data quality issues (duplicates, blank required fields, malformed emails) are documented and corrected in Sell before the production migration phase. This stage can take one to two weeks depending on data cleanliness.
Owner and User reconciliation
We extract every distinct Sell User referenced on Deals, Contacts, and Tasks and match by email against Odoo's res.users table.
What this step covers
Any Sell User without a matching Odoo User account enters a named reconciliation queue. The customer's Odoo admin provisions missing users before production migration begins. This step gates the production migration because Odoo's Opportunity and Activity records require a valid user_id for the responsible user.
Production migration in dependency order
We run production migration in record-dependency order: res.users (provisioned, validated), res.partner records with type=company (from Sell Companies), res.partner records with type=contact (from Sell Contacts with parent_id resolved to company Partner), crm.lead records with type=opportunity (from Sell Deals with partner_id resolved and stage_id resolved), crm.lead records with type=lead (from Sell Leads), mail.activity records (Tasks and calls linked to crm.lead or res.partner by Odoo ID resolved at migration time), crm.tag_rel entries, and Line Item custom fields on crm.lead.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze Sell writes during cutover, run a final delta migration of records modified during the migration window, then enable Odoo as the system of record.
What this step covers
We validate 50 random Opportunity records, 50 Contact records, and 20 Activity records against Sell source data and deliver a reconciliation summary to the customer. We deliver the Workflow, Sequence, and automation inventory document to the customer's team for rebuild in Odoo Action Rules or Studio. We support a one-week post-cutover window to address immediate data issues; ongoing Odoo configuration, workflow rebuild, and admin training are outside standard migration scope.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and whether Odoo Sale or Inventory apps are activated to handle Line Items. Sell's sunset deadline is August 31, 2027, which we treat as a hard constraint for every project. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Zendesk Sell to Odoo CRM →Why teams move from Zendesk Sell to Odoo CRM
- Zendesk officially retired Sell on August 31, 2027. Zendesk's Service Data Deletion Policy triggers data destruction on that date or subscription end, whichever comes first, leaving no extension window. Teams using Sell as their CRM have no choice but to migrate or lose their data entirely, and waiting until 2026 Q4 or 2027 risks rushed timelines, constrained specialist availability, and data loss for records that cannot be exported in time. The migration deadline, not a feature gap, is the primary driver.
- Odoo provides an all-in-one ERP and CRM on a single platform, consolidating CRM, accounting, inventory, project management, and HR into one database. Teams migrating from Sell frequently cite reducing their total app stack as a secondary benefit, because Sell required separate tools for billing and operations that Odoo natively covers. This consolidation lowers per-license cost and eliminates the data silos that come from running separate CRM and ERP systems.
- Odoo's Community edition is free for unlimited users when self-hosted, and the Standard tier at $24.90/user/month undercuts Sell Professional at $49/user/month for teams of five or more. Reviewers on G2 and Capterra consistently flag Sell's per-user pricing as compounding cost as teams grow, especially for organizations that need seat access for sales reps, sales ops, and customer success. Odoo's pricing model is more predictable for growing teams with high user counts.
- Odoo is open-source with full database and code access, allowing technical teams to modify the CRM model, build custom modules, and self-host without per-user license constraints beyond infrastructure. Companies outgrowing SaaS licensing models and seeking data ownership move to Odoo specifically because it removes vendor lock-in. This is distinct from moving to another SaaS CRM and is a recurring theme in Odoo community discussions on Reddit r/Odoo.
- Odoo CRM excels in document and workflow management with native attachments, note hierarchies, and automated activity logging that integrates directly with Odoo's Document Management System. Sell's activity-centric interface is well-regarded for rep adoption but lacks the document depth that enterprises managing complex sales processes require. Teams with contract-driven or proposal-heavy sales cycles prefer Odoo's unified document and opportunity view.
Questions, answered
Zendesk Sell to Odoo CRM migration questions
How long does a Zendesk Sell to Odoo CRM migration take?
Most migrations land between four and six weeks for accounts under 15,000 Contacts and 3,000 Deals with clean data and no custom objects. Migrations with multi-pipeline structures, Line Item preservation, large activity histories, or self-hosted Odoo deployments requiring server-side XMLRPC configuration move to ten to fourteen weeks. Given Sell's August 31 2027 sunset deadline, any migration beginning after Q1 2027 carries elevated risk of incomplete data export. We strongly recommend starting discovery at least nine months before the deadline.
Do Sell Workflows, Sequences, and automations migrate to Odoo?
No. Sell Workflows and Sequences are automation features that have no direct Odoo equivalent in their current form. Sell Workflows use a trigger-condition-action model that does not map to Odoo's Action Rules, Server Actions, or Automated Actions without manual redesign. Sequences store cadence state (enrollment, step timing, reply tracking) that is not exportable and has no Odoo equivalent in standard CRM. We deliver a written inventory of every active Sell Workflow and Sequence with its trigger, conditions, and recommended Odoo Action Rule equivalent. The customer's Odoo admin or an Odoo partner rebuilds these post-migration.
How does the Contact-Company split work in Odoo?
Odoo uses a single res.partner model for both companies and individuals. Sell Contacts with an associated Company create two Odoo records: the Company as a res.partner with type='company', and the Contact as a res.partner with type='contact' linked via parent_id to the company Partner. Contacts without a Company create a standalone Partner record. We resolve the parent_id references during the import phase so that Odoo's address inheritance works correctly: a Contact's address can be inherited from its parent Company in Odoo. This split is designed during scoping and validated during the sandbox phase before production migration.
Can we migrate Sell call recordings to Odoo?
Call recordings stored as audio files in Sell are exported as file references or URLs. We migrate the call log metadata (duration, disposition, date, associated Contact and Deal) as Odoo mail.activity records with activity_type_id=phone. Call recording files migrate as ir.attachment records linked to the same crm.lead or res.partner if Sell provides a download URL or file storage path. Large file migration requires separate file storage planning if the customer uses Odoo Online, as attachment storage has size limits depending on the Odoo plan.
Do we migrate Sell data to Odoo self-hosted or Odoo Online?
Both are supported. Odoo Online uses XMLRPC against the cloud database and requires API access credentials with appropriate user rights. Odoo self-hosted deployments require network access to the XMLRPC endpoint, database name, and migration user credentials. Self-hosted migrations add complexity because server configuration (network access, database name, user provisioning) is the customer's responsibility, but they also offer unlimited user seats without per-user licensing constraints. We identify the deployment type during discovery and configure the API access accordingly.
Can Odoo CRM handle our accounting and inventory needs alongside CRM?
Yes. Odoo's modular architecture means the CRM app shares a database with Odoo Accounting, Inventory, Project Management, and other business apps. A Contact in Odoo CRM is the same res.partner record used in Odoo Accounting for invoices and in Odoo Purchase for supplier records. This integration is native and requires no middleware. We focus exclusively on the CRM migration scope and flag that activating additional Odoo apps (Sale, Inventory, Accounting) post-migration is a separate configuration step that the customer's Odoo partner or internal admin handles.
What happens to our Sell data after August 31 2027?
Zendesk deletes all Sell data per its Service Data Deletion Policy on the sunset date or when the subscription ends, whichever occurs first. After that date, Sell is inaccessible and no export is possible. We strongly recommend completing the Odoo migration and running both systems in parallel during a transition period of two to four weeks before cutting off Sell write access. Exporting a CSV from Sell before migration begins is advisable as a fallback backup, though CSVs do not preserve relationships (Contact-to-Company, Deal-to-Contact) that a structured API migration preserves.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → Act! to Odoo CRMMapping · history · rollbackMyCase to Odoo CRMMapping · history · rollbackDynamics 365 to Odoo CRMMapping · history · rollbackSuiteCRM to Odoo CRMMapping · history · rollbackMailchimp to Odoo CRMMapping · history · rollbackJonas Enterprise Service & Construction Software to Odoo CRMMapping · history · rollback Zendesk Sell to HubSpotMapping · history · rollbackZendesk Sell to PipedriveMapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Datetime field reference — Odoo 19.0 documentation
- Upload size limit in Odoo — Odoo Forum (128 MiB cap)
- Fields and widgets — Odoo 19.0 documentation (Studio)
Get a quote
Moving from Zendesk Sell to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote