Skip to content
Get a quote

Odoo CRM to Zoho CRM migration

We migrate Contacts, Leads, Opportunities, and Activity history from Odoo CRM into Zoho CRM with the crm.lead unified model split into separate Zoho Lead and Deal objects, custom fields retyped to match Zoho field types, and tags remapped to Zoho's Multi-Select Picklist format before cutover.

Short answer

FlitStack AI migrates contact + accounts, leads, deals, deal stages and zoho crm users / team assignments from Odoo CRM to Zoho 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: 3-5 weeks.

By

Source Odoo CRM
DestinationZoho CRM
Contact + AccountLeadDealDeal StageZoho CRM Users / Team assignment
Mapped field by field · sample run · one-click rollback

What moves from Odoo CRM to Zoho CRM?

Moving from Odoo CRM to Zoho CRM is a cross-platform schema translation, not a direct record copy.

Read the full summary

Odoo stores Leads and Opportunities in a single crm.lead table with a type discriminator, while Zoho maintains separate Lead and Deal (Opportunity) objects with distinct layouts and lifecycle stages. We resolve that structural split during scoping, map res.partner contact records into Zoho Contacts with their parent Accounts, and preserve Tags from crm.tag as Multi-Select Picklist values. Odoo Enterprise-only features — CRM Enterprise automation rules, AI lead scoring, Documents, and WhatsApp integration — do not migrate because they depend on Odoo's proprietary AI infrastructure and action framework. We deliver a written inventory of these features for the customer's admin to evaluate against Zoho's native alternatives (BluePrint, Canvas, Zia). Workflows, server actions, and custom XML view definitions cannot migrate and are excluded from standard scope.

1:N split

res.partner → Contact + Account

Odoo res.partner serves as both Contact and Company depending on the is_company flag and parent_id self-referential relationship.

How it maps

We split this into Zoho Account (when is_company=true or when the partner has child contacts) and Zoho Contact (when is_company=false). The parent_id becomes the Account lookup on Contact. Company type (individual vs organization) maps to Zoho's Account Type picklist.

1:1

crm.lead (type=lead) → Lead

Odoo crm.lead records with type='lead' map to Zoho Lead.

How it maps

Fields including name, contact_name, email_from, phone, source_id, and description migrate directly. Odoo's lead_priority maps to Zoho Lead Status or a custom priority field. The split between crm.lead type='lead' and type='opportunity' is applied at migration time as the first transform pass before any object-specific logic runs.

1:1

crm.lead (type=opportunity) → Deal

Odoo crm.lead records with type='opportunity' map to Zoho Deal.

How it maps

Key fields including expected_revenue, probability, date_closed, partner_id, and stage_id translate to Zoho Deal Amount, Stage, Expected Close Date, Contact Name lookup, and Pipeline stage. Odoo's probability field is preserved as a custom field because Zoho Deals use Stage-based probability by default.

configuration

crm.stage → Deal Stage

Odoo pipeline stages from crm.stage are mapped to Zoho Deal Stage picklist values within the target Deals pipeline.

How it maps

Stage order is preserved from the crm.team.stage.rel ordering table. Each stage maps to a Zoho Stage with matching or nearest-neighbor probability. We configure the Zoho Deals pipeline before migration so stage values are available during Deal import.

lookup

crm.team → Zoho CRM Users / Team assignment

Odoo Sales Teams (crm.team) map to Zoho CRM user assignments.

How it maps

Team members from member_ids are reconciled against Zoho Users by email. Teams with no direct Zoho equivalent are represented as a group of user assignments on Deals and Leads. If Zoho's built-in group or territory feature is enabled in the destination, we configure it during the Deals pipeline setup phase.

configuration

crm.tag → Multi-Select Picklist on Lead/Deal

Odoo crm.tag records applied via many2many to crm.lead are extracted as a flat tag list and mapped to a Zoho Multi-Select Picklist field on the Lead and Deal modules.

How it maps

We create the picklist field in Zoho before migration, add all distinct tag values as picklist options, and map the many2many relationship to comma-separated values during import. Tag count exceeding 50 distinct values may require splitting into multiple picklists or a Zoho custom Tags module.

What moves12 objects
Odoo CRMZoho CRM
  • res.partnerContactsplit
  • crm.leadLead1:1
  • crm.leadDeal1:1
  • crm.stageDeal Stagetransformed
  • crm.teamZoho CRM Userstransformed
  • crm.tagMulti-Select Picklist on Lead/Dealtransformed

+ 6 more in the mapping below

How Odoo CRM and Zoho 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.

DimensionOdoo CRMZoho CRM
Lead and Opportunity storageSingle crm.lead table with type='lead' or type='opportunity' discriminatorSeparate Lead module and Deal (Opportunity) module with distinct lifecycle stages
Contact and Account modelres.partner serves as both Contact and Company (no separate Account object)Separate Contact and Account objects with a mandatory Account lookup on Contact
Pipeline stagescrm.stage ordered per team via crm.team.stage.relZoho Deals have Stage picklist values scoped to the Deals module, with Blueprint visual workflow per stage
Custom object architectureCustom fields stored as database columns in the core table; custom addons create new model tablesCustom modules and custom fields created via UI with no database-level field declarations required
Pricing modelPer-app per-user: stacking multiple Odoo apps ($25-50/user/month) plus Odoo.sh hostingPer-user bundle: CRM in all plans at $14-$100/user/month with no per-app stacking
Email integrationGmail and email sync reliability cited as a recurring complaint across G2 and Reddit reviewsNative Zoho Mail with built-in Zoho SMTP and pre-built Gmail/Microsoft 365 connectors
SupportCommunity forums and paid Odoo Enterprise support with variable response times24/7 support via chat, email, and phone across all paid plans

What to watch for in a Odoo CRM to Zoho CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Odoo crm.lead unified model requires explicit split to Zoho Lead and Deal

Odoo stores both Leads and Opportunities in a single crm.lead table with a type discriminator field.

How we handle it

Zoho maintains separate Lead and Deal modules with distinct layouts, lifecycles, and field sets. We apply the type split as the first transformation step during migration. Records where type='lead' flow to Zoho Lead; records where type='opportunity' flow to Zoho Deal. If the customer has used Odoo's Lead-conversion action, the converted record retains type='opportunity' but gains a partner_id link — we preserve this relationship by setting the Zoho Deal's Contact Name lookup to the migrated Contact record. Migrations that skip this split design step result in orphaned Deals in Zoho with no Contact reference.

high

Zoho requires Accounts before Contacts; Odoo res.partner conflates both

Odoo res.partner serves as both Contact and Company depending on is_company and parent_id.

How we handle it

Zoho requires a separate Account record before a Contact can reference it. We extract the partner hierarchy during the first transform pass: partners flagged is_company=true (or with child partners) become Zoho Accounts first; all other partners become Zoho Contacts with parent_id resolving to the mapped Account ID. Partner records with no Company parent are imported as Contacts with no Account lookup, which is valid in Zoho but may require manual cleanup if the customer's Zoho admin enforces Account linking policy.

high

Odoo Enterprise-only modules do not install or migrate on Zoho

CRM Enterprise automation rules, AI lead scoring (crm.scoring.rule), Documents, WhatsApp integration, and Social marketing are Enterprise-exclusive Odoo modules that depend on Odoo's proprietary AI infrastructure and action framework.

How we handle it

These have no Zoho equivalent and cannot migrate as functional features. We export a written inventory of every active Enterprise feature — automation rule conditions, AI scoring thresholds, document storage paths — and the customer's admin evaluates these against Zoho BluePrint, Zia AI, and Zoho WorkDrive equivalents post-migration. The data underlying these features (activity logs, document records) migrates as standard records, but the automation logic does not.

medium

Odoo Custom Fields require Zoho schema pre-creation before data loads

Odoo custom fields on crm.lead are stored as columns in the PostgreSQL database.

How we handle it

When migrating to Zoho, the custom field must be created as a Zoho custom field (Picklist, Lookup, Multi-Select) before the data import begins, or the incoming values are rejected or discarded. We audit all custom columns in the Odoo crm_lead table during discovery, classify their types (selection, many2one, many2many, char, integer), create matching Zoho custom fields during the schema setup phase, and validate that field definitions are present before the first data batch loads. This is a reversible error — Zoho custom fields can be created and data reloaded — but it adds a cycle to the migration if skipped.

medium

Odoo direct PostgreSQL export may be required when XML-RPC is unavailable

Odoo Community edition and Odoo Online customers do not have guaranteed API access via XML-RPC without a Custom Plan subscription.

How we handle it

We check XML-RPC availability during discovery. When the API is unavailable, we connect directly to the Odoo PostgreSQL database with a read-only connection to extract crm_lead, res_partner, crm_tag, mail_activity, and ir_attachment records. This bypasses Odoo's ORM layer entirely and requires explicit field-level SQL mapping for custom addon columns, which we document as part of the export script before running.

How the migration runs

  1. Discovery and Odoo source audit

    We audit the source Odoo database across edition (Community vs Enterprise), installed custom addons, PostgreSQL schema, and Odoo version.

    What this step covers

    We enumerate all crm.lead records with type discriminator, all res.partner records with is_company and parent_id relationships, all crm.tag values, all mail.activity records with type and user_id references, and all ir.attachment records with res_model= crm.lead. We identify Enterprise-only modules (CRM Enterprise, Documents, WhatsApp, Social) from ir_module_module and flag them as non-migratable. We assess XML-RPC API availability and fall back to direct PostgreSQL export if the API is unavailable. The discovery output is a written migration scope and object inventory.

  2. Zoho CRM schema setup and custom field creation

    We create the Zoho CRM schema before any data migration begins.

    What this step covers

    This includes configuring the Deals pipeline with stage values that correspond to Odoo crm.stage records, creating any required Account Type and Industry picklist values to match Odoo partner categories, creating Multi-Select Picklist fields for Odoo tags, creating custom fields on Lead and Deal that correspond to Odoo custom columns on crm.lead, and creating Zoho Custom Modules for any Odoo custom addon model tables. Schema is validated in a Zoho sandbox or staging environment before production data loads.

  3. res.partner hierarchy extraction and Account-Contact split

    We extract the full Odoo res.partner hierarchy and run the Account-Contact split transformation.

    What this step covers

    Partners flagged is_company=true or with child partners become Zoho Accounts first. All other partners become Zoho Contacts with parent_id resolved to the mapped Account. The split runs as the first data-transform pass and produces two CSV batches: Accounts and Contacts. We load Accounts first so that the Account ID is available for Contact parent_id resolution during the Contact batch.

  4. crm.lead split and Lead/Deal migration

    We run the crm.lead split transformation as the second data-transform pass.

    What this step covers

    Records with type='lead' become Zoho Lead records; records with type='opportunity' become Zoho Deal records with the linked Contact or Account lookup resolved via email match against the previously migrated Contact and Account batches. Stage values are remapped from Odoo crm.stage IDs to Zoho Deals stage picklist values. Custom field values on crm.lead are mapped to the Zoho custom fields created in Step 2.

  5. Activity history and attachment migration

    We migrate mail.activity records as Zoho Tasks attached to the migrated Lead or Deal by resolving the Odoo user_id to Zoho User by email and the crm.lead res_id to the Zoho record ID.

    What this step covers

    Activity records are chunked into batches of 200 and loaded via Zoho CRM API with rate-limit handling and exponential backoff. ir.attachment records are exported from the Odoo filestore, uploaded to Zoho Files, and linked to the parent Lead or Deal record using the Zoho Files API. Large attachment batches (>1 GB total) are sequenced separately from primary data migration.

  6. Cutover, validation, and Enterprise feature handoff

    We freeze Odoo write access during the cutover window, run a final delta migration of any records modified during the migration run, then enable Zoho CRM as the system of record.

    What this step covers

    We deliver a reconciliation report comparing record counts in Odoo against Zoho for each module, spot-checking 25-50 records per module against source. We deliver the written Enterprise feature inventory document to the customer's admin team for BluePrint and Zia evaluation. We do not rebuild Odoo automation rules as Zoho BluePrint workflows inside standard migration scope; that is a separate engagement.

Odoo CRM Zoho CRM
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Zoho CRMRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

A quote scales with record volume, number of custom fields and custom addons, and whether Zoho Blueprint workflows are being designed during migration. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Odoo CRM to Zoho CRM →

Why teams move from Odoo CRM to Zoho CRM

  • Odoo Enterprise pricing stacks faster than Zoho for growing teams. Odoo charges per-user per-app — a team using CRM, Sales, and Invoicing quickly reaches EUR 30-50 per user per month before Odoo.sh hosting. Zoho CRM bundles CRM functionality across all plans at $14-$100 per user per month with no per-app stacking, making total cost of ownership more predictable for sales teams that need CRM without the full ERP stack.
  • Gmail and email integration in Odoo is a persistent complaint in G2 reviews and Reddit threads — email threads drop, conversations scatter across inboxes, and the Odoo-Gmail sync breaks under common configurations. Zoho CRM includes native Zoho Mail with built-in SMTP and a pre-built Gmail connector that does not require the same level of per-user OAuth configuration.
  • Odoo implementation complexity grows with business size — advanced features require additional configuration and developer hours, and per-app per-user pricing compounds quickly as more modules are added. Zoho CRM offers faster time-to-value for teams moving from Odoo because its UI is more opinionated and requires less upfront configuration to reach a functional sales pipeline.
  • Odoo Enterprise support response times frustrate teams encountering bugs during version upgrades, with some noting critical issues go unresolved for weeks. Zoho provides 24/7 customer support through chat, email, and phone at all paid tiers, which smaller teams and growing businesses cite as a decisive operational factor when evaluating long-term platform commitment.
  • Companies running Odoo Community face API access limitations since XML-RPC is gated behind the Odoo Custom Plan, forcing direct PostgreSQL connections for data export. Zoho CRM provides full REST API access on all plans including the Standard tier at $14 per user per month, eliminating the infrastructure dependency that Community edition customers face when planning a migration.

Questions, answered

Odoo CRM to Zoho CRM migration questions

How long does an Odoo CRM to Zoho CRM migration take?

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Opportunities with no custom addon modules. Migrations with custom addon modules, large activity histories (over 200,000 mail.activity records), many2many tag volumes exceeding 50 distinct tags, or Zoho Blueprint rebuild scope move to eight to twelve weeks because of schema design, custom field pre-creation, and the partner hierarchy split work.

Do Odoo automation rules, server actions, and AI lead scoring migrate to Zoho?

No. Odoo automation rules (base.action.rule, ir.actions.server scoped to CRM) are Enterprise-exclusive and tightly coupled to Odoo's action framework. AI lead scoring (crm.scoring.rule) depends on Odoo's proprietary algorithm. Neither can migrate as functional code to Zoho. We export a written inventory of every active Enterprise feature — automation trigger, conditions, actions, and AI scoring thresholds — and the customer's admin evaluates these against Zoho BluePrint for process automation and Zia AI for predictive scoring. Rebuilding these in Zoho is outside standard migration scope and is handled as a separate engagement.

Can we migrate from Odoo Community edition using the PostgreSQL database directly?

Yes. Odoo Community and Odoo Online customers without XML-RPC API access can export data directly via a read-only PostgreSQL connection to the Odoo database. We connect to the database, extract the relevant tables (crm_lead, res_partner, crm_tag, mail_activity, ir_attachment, and any custom addon tables), and run the same transformation pipeline. We document the SQL field mappings for custom addon columns explicitly as part of the export script. API-based export is used when XML-RPC is confirmed available to avoid touching the database directly.

Do we lose historical activity data (calls, emails, meetings, tasks) when migrating from Odoo to Zoho?

No. We migrate the full mail.activity history as Zoho Tasks. Activity type maps to Task Subject and a custom Task Type picklist. date_deadline, user_id (resolved to Zoho User by email), and note migrate as Due Date, Assigned To, and Description. Attachment references in ir.attachment migrate to Zoho Files with the correct parent record link. The activity timeline ordering is preserved by setting the Zoho Task Due Date to the original Odoo timestamp. Note-type mail.message records migrate as Zoho Notes attached to the parent Lead or Deal.

How do we handle Odoo Enterprise-only features in the migration?

CRM Enterprise, Documents, WhatsApp integration, Social marketing, and AI lead scoring are flagged as non-migratable at discovery. We export a written inventory of every active Enterprise feature — automation rules, AI scoring configurations, document storage references — so the customer's admin knows exactly what is lost and what needs rebuilding in Zoho. The underlying data (activity logs, document metadata, WhatsApp message records) migrates as standard records where applicable, but the Enterprise-specific features require Zoho-native alternatives (BluePrint, Zia, WorkDrive) that are evaluated post-migration.

Can FlitStack AI also migrate Odoo ERP modules beyond CRM?

Standard FlitStack AI CRM migration scope covers Leads, Opportunities, Contacts, Accounts, Activities, Tags, Attachments, Quotations, and Custom Objects. Odoo ERP modules beyond the CRM scope — Accounting (account.account), Inventory (stock.picking), Manufacturing (mrp.production), and HR (hr.employee) — are not included in standard CRM migration scope. If the customer is migrating a broader Odoo ERP instance to the Zoho ecosystem (Zoho Books, Zoho Inventory, Zoho People), we scope those as separate migration engagements with their own discovery, schema mapping, and timeline.

Get a quote

Moving from Odoo CRM to Zoho CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.

Get a quote