---
title: "Bitrix24 to Odoo CRM Migration: Field Mapping & Rollback"
description: "Migrate Bitrix24 to Odoo CRM with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/bitrix24/to/odoo-crm"
---

# Bitrix24 to Odoo CRM migration

We migrate Contacts, Companies, Deals, and Smart Processes from Bitrix24 into Odoo CRM with the import dependency order enforced, pipeline stages remapped to Odoo stage configuration, and Bitrix24 Smart Process schemas translated into Odoo custom fields before any data moves. Activity history is fetched via batch API to close the gap left by Bitrix24 CSV exports.

Short answer

FlitStack AI migrates contacts, opportunities, leads, crm stage configurations and product templates from Bitrix24 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: 2-4 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/bitrix24/to/odoo-crm#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Bitrix24 ![](https://flitstack.ai/platforms-trim/bitrix24.webp)

Destination Odoo CRM ![](https://flitstack.ai/platforms-trim/odoo-crm.webp)

Contact Opportunity Lead CRM Stage Configuration Product Template

Mapped field by field · sample run · one-click rollback

## What moves from Bitrix24 to Odoo CRM?

Moving from Bitrix24 to Odoo CRM is a cross-platform structural migration that requires resolving fundamental differences in how each platform organises CRM data.

Read the full summary

Bitrix24 uses a flat entity model where Leads, Deals, Contacts, and Companies are separate objects, while Smart Processes provide a fully custom entity type per customer. Odoo CRM consolidates some of these concepts under a Contact-centric model and uses Pipeline Stages configured per-crm.activity rather than a separate Pipeline entity. Bitrix24's native CSV export omits activity history — emails, calls, comments, and tasks — and we close this gap through batch REST API extraction. Odoo's open-source Community edition requires self-hosting and manual patching; the Enterprise edition ($70/user/mo) provides hosted cloud, automatic updates, and a support channel. We do not migrate Bitrix24 Workflows, Business Process Automation templates, Telephony configs, or Drive files; these require a separate rebuild scope with an Odoo implementation partner or the customer's internal admin.

1:1

### Company → Contact (company type)

Bitrix24 Companies map to Odoo Contacts with the is\_company flag set to True.

How it maps

The legal name, address fields, phone, email, and requisites from Bitrix24 become the corresponding fields on the Odoo res.partner record. We resolve the Odoo partner ID before importing any child Contact records that link to this Company via the CONTACT\_COMPANY multi-link. Bitrix24 Company Industry and Type map to Odoo custom fields or tags depending on whether the customer uses the Enterprise tags module.

1:1

### Contact → Contact (individual)

Bitrix24 Contacts map to Odoo res.partner records with is\_company set to False.

How it maps

The parent\_id field is resolved to the previously imported Company record by name or domain match. Bitrix24 custom fields on Contact (crm.contact.userfield.list) are read at scoping time and mapped to Odoo custom res.partner.fields. Multi-select fields from Bitrix24 map to Odoo tags or many2many fields depending on the field cardinality.

1:1

### Deal → Opportunity (crm.lead)

Bitrix24 Deals map to Odoo crm.lead records with type='opportunity'.

How it maps

The deal stage maps to an Odoo CRM Stage id that we pre-create by name-match against the destination pipeline. The responsible Bitrix24 user maps to the Odoo user\_id by email lookup. Closed-Won and Closed-Lost outcomes from Bitrix24 become Odoo Stage values. Deal amount and currency migrate to Odoo's expected\_revenue and currency\_id fields.

1:1

### Lead → Lead (crm.lead type=lead)

Bitrix24 Leads map to Odoo crm.lead records with type='lead'.

How it maps

Lead status, source, and responsible user are preserved as custom fields or standard fields on the Odoo Lead. The Lead-to-Contact conversion that Bitrix24 handles natively is handled in Odoo through the crm.lead / convert wizard after migration: we preserve the lead's conversion state in a custom field so the Odoo admin can complete the conversion manually post-import if needed.

configuration

### Pipeline → CRM Stage Configuration

Bitrix24 Pipelines are read via crm.pipeline.list and crm.stage.list.

How it maps

Each Bitrix24 Pipeline becomes a named CRM Stage sequence in Odoo under the CRM app's Pipeline configuration. Stage sort order and colour attributes migrate to Odoo's sequence and legendcolour fields. We configure stage probabilities to match Bitrix24 percentages where available.

1:1

### Product (Catalog) → Product Template

Bitrix24 Products from the catalog map to Odoo product.template records with Standard Pricing.

How it maps

SKU, product name, description, and list price migrate directly. We flag any inactive Bitrix24 products for Odoo admin review before import because Odoo does not have a soft-inactive product concept natively.

******What moves 12 objects

Bitrix24 Odoo CRM

- Company Contact 1:1
- Contact Contact 1:1
- Deal Opportunity 1:1
- Lead Lead 1:1
- Pipeline CRM Stage Configuration transformed
- Product Product Template 1:1

\+ 6 more in the mapping below

## How Bitrix24 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            | Bitrix24                                                                  | Odoo CRM                                                                             |
| -------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Pricing model        | Flat-rate per plan; headcount growth does not inflate the bill linearly   | Per-user monthly on all editions; headcount scales cost linearly                     |
| Entity model         | Separate Leads, Contacts, Companies, Deals, and Smart Processes           | Contact-centric with Leads; Opportunities grouped by Pipeline and Stage              |
| Custom entities      | Smart Processes — fully custom REST namespaces per customer entity        | Custom fields on standard objects in Community; custom modules in Enterprise         |
| Communication stack  | Built-in Telephony, Chat, and Video integrated with CRM timeline          | No native telephony; chat and video require separate apps or third-party integration |
| Free tier viability  | Free plan with limits: 5GB storage, 100 tasks, 50-day inactivity deletion | Community edition is free and self-hosted; no inactivity deletion risk               |
| Implementation model | Self-service with optional partner; faster onboarding for SMBs            | Typically requires an Odoo implementation partner for production deployment          |
| Activity export      | CSV export omits emails, calls, comments, SMS entirely                    | CRM Log activities are stored in the crm\_lead table and accessible via ORM API      |

## What to watch for in a Bitrix24 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.

high

### Smart Processes have no direct Odoo equivalent

Bitrix24 Smart Processes are fully custom CRM entities with their own REST namespaces, fields, and relationships.

How we handle it

Odoo Community does not support custom CRM objects without a custom module built by an Odoo developer; Odoo Enterprise adds a Studio tool for creating custom fields on standard objects but still lacks a true custom entity type. We read every Smart Process schema at scoping, map simple properties to custom fields on Contact or Opportunity, and document complex multi-relationship Smart Processes for the customer's Odoo implementation partner to scope as a separate custom module build. Skipping this step leaves the customer without the data that lives in their most complex Bitrix24 entity.

high

### Activity history must be fetched via API separately from CSV

Bitrix24's native CSV export captures only left-side entity fields — names, statuses, dates, responsible users.

How we handle it

Emails, logged calls, meeting records, comments, and SMS are excluded entirely. We do not treat CSV as a complete export. We use the Bitrix24 REST API's batch methods (crm.activity.items.list) to extract secondary data, but the Standard plan rate limit of 50 requests per burst on standard plans and 250 on Enterprise makes large activity histories slow to extract. We scope activity extraction as a separate phase and warn the customer if the activity volume will extend the project timeline significantly. If the source account is on the free plan, we also verify it has not triggered the 100-task limit, which can block task export.

high

### Odoo Community requires server management that Bitrix24 cloud does not

Many Bitrix24 customers are on the cloud-hosted plan and have no infrastructure team.

How we handle it

Odoo Community is self-hosted: it requires a Linux server, database administration, SSL certificates, reverse proxy configuration, and manual patching on each Odoo version release. Odoo Enterprise ($70/user/mo) addresses this with hosted cloud and automatic updates, but the Enterprise subscription adds significant cost. We scope the Odoo edition decision early. If the customer chooses Community, we document the server requirements and recommend an Odoo hosting provider or the customer's IT team manages the instance. Migration into a self-hosted environment adds an infrastructure setup phase that is outside the data migration scope.

medium

### Bitrix24 Telephony and Chat have no Odoo native equivalent

Bitrix24's built-in telephony (VOIP, call recording, call routing) and live chat are tightly integrated with the CRM timeline — calls and chats are logged automatically to Contact and Deal records without manual entry.

How we handle it

Odoo has no native telephony or live chat module in Community; these require third-party apps from the Odoo Apps store or external integrations with Asterisk, Twilio, or similar. During migration scoping, we identify every Contact and Deal with a telephony interaction in the activity history. These interactions migrate as activity log records in Odoo CRM, but the automatic CRM-timeline logging workflow requires rebuilding as a separate integration project with an Odoo partner or the customer's IT team.

medium

### Import dependency order must be enforced — orphaned records block Odoo

Odoo enforces referential integrity on parent-child relationships during data import.

How we handle it

Contacts require a parent Company to be resolved before insert; Deals require a Contact or Company to be resolved; Estimates require a Deal. Bitrix24 Smart Processes with multi-entity lookups add further dependency chains. We sequence imports in this order: Companies first, then Contacts (resolving parent\_id to the imported Company), then Leads, then Deals (resolving contact\_id and company\_id), then Products, then Estimates, then Activities, then Smart Process data. Any deviation from this sequence in a self-service import attempt results in orphaned records that Odoo rejects at insert time. We enforce this sequence programmatically and validate record counts after each phase before proceeding.

## How the migration runs

1. ### Discovery and source audit

   We audit the Bitrix24 source portal across plan tier, API rate limit envelope, CRM entity counts (Companies, Contacts, Deals, Leads, Smart Process entities), activity volume per type (emails, calls, meetings, notes), and Drive file count.

   What this step covers

   We also identify all active Smart Process schemas (entity codes, field types, relationships) because each requires a custom mapping design. We extract owner and user lists and check for any account near the 100-task limit on free plans. The discovery output is a written migration scope document with record counts per entity, a Smart Process inventory, and an Odoo edition recommendation (Community vs Enterprise).

2. ### Destination schema design and Odoo edition setup

   We design the Odoo CRM schema before any data moves.

   What this step covers

   This includes configuring CRM Stages to match Bitrix24 pipeline stages by name and probability, creating custom fields on res.partner and crm.lead to receive Bitrix24 custom field data, pre-creating Smart Process translation maps for simple enumerations, and documenting complex Smart Processes that require a custom Odoo module. If Odoo Enterprise is chosen, we configure the CRM app in the Odoo cloud instance. If Community is chosen, we document the server, database, and SSL requirements and hand off infrastructure setup to the customer's IT team or hosting provider before the data migration phase begins.

3. ### Sandbox migration and reconciliation

   We run a full migration into an Odoo test database using production-like data volume.

   What this step covers

   The customer's CRM lead or Odoo admin reconciles record counts across all entity types, spot-checks 25-50 records against the Bitrix24 source for field-level accuracy, and reviews the Smart Process mapping before signing off. Activity history reconciliation is particularly important here because it is the most likely source of partial data due to API pagination limits. Any mapping corrections, custom field additions, or stage configuration adjustments happen in this phase, not in production.

4. ### Owner reconciliation and user provisioning

   We extract every distinct Bitrix24 user referenced as a responsible user on any CRM record.

   What this step covers

   Each user is matched by email to an existing Odoo res.users record. Users without a matching Odoo account are placed in a reconciliation queue. The Odoo admin provisions any missing users (active or inactive depending on whether the original Bitrix24 user is still with the company) before record import resumes. Because Odoo uses user\_id as a required field on many standard CRM objects, this step is a hard gate: migration cannot proceed past Deal import without a complete owner resolution map.

5. ### Production migration in dependency order

   We run the production migration in strict dependency order: Companies (as parent Contacts), individual Contacts (with parent\_id resolved), Leads, Deals (with contact\_id and company\_id resolved), Products (to support Estimate line items), Estimates (in draft state), Activity history (emails, calls, meetings, notes via batch API), and Smart Process data (mapped to custom fields or deferred to a custom module).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. Bitrix24 API rate limits are respected with exponential backoff and batch chunking to avoid burst rejections on Standard-tier accounts.

6. ### Cutover, delta sync, and automation handoff

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

   What this step covers

   We deliver a written inventory of Bitrix24 Workflows, Business Process Automation templates, and Telephony configs that require rebuild in Odoo, with Odoo Workflow Action recommendations for each. Drive file URLs are handed off in a documented list for the customer to download manually. We support a one-week hypercare window for reconciliation issues raised by the sales team. We do not rebuild Bitrix24 automations as Odoo server actions inside the migration scope; that is a separate engagement with an Odoo implementation partner.

![](https://flitstack.ai/platforms/bitrix24.png) Bitrix24 ![](https://flitstack.ai/platforms/odoo-crm.svg) Odoo CRM

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Odoo CRM Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**8-14 weeks** Large or heavily customised accounts

Pricing reflects record volume, Smart Process complexity, and whether additional Odoo modules beyond CRM are in scope. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Bitrix24 to Odoo CRM →](https://flitstack.ai/contact)

## Why teams move from Bitrix24 to Odoo CRM

- Bitrix24 reviewers on Capterra and G2 consistently describe the platform as feeling abandoned in 2024-2025, citing slow feature releases, unresolved bug reports, and a deteriorating mobile experience especially on Android. Odoo, by contrast, publishes quarterly release notes with active development across its full application suite. Teams whose core CRM workflows depend on a responsive platform choose Odoo for its visible development cadence and the accountability of a European-headquartered open-source company.
- Data ownership and portability become critical for teams that have outgrown Bitrix24's export limitations. Bitrix24's native CSV export omits activities, comments, and telephony logs, and the REST API rate limit of 50 requests per burst on standard plans makes complete data extraction slow and expensive at scale. Odoo's open-source Community edition gives customers full database access and the ability to run direct SQL exports, removing the export ceiling entirely and eliminating vendor lock-in for businesses that need raw data portability.
- Bitrix24's flat-rate pricing undercuts competitors at scale but becomes expensive for small teams on low-tier plans that need basic automation and telephony credits. Odoo's per-user model at the lower Standard tier (around $25/user/mo) often undercuts Bitrix24's Professional plan ($249/month flat) for teams under five users, and the Community edition eliminates the per-month cost entirely for teams comfortable with self-hosting. ITQlick rates Odoo CRM lower on features (80/100) than Bitrix24 (90/100) but notes that Odoo's total cost of ownership including implementation is more favourable for businesses with modest CRM requirements.
- Odoo's modular architecture allows CRM to coexist with Accounting, Inventory, Manufacturing, and Project Management in a single database, reducing the need for third-party integrations that Bitrix24 partially replaces with its own all-in-one model. Businesses that have grown beyond CRM and need ERP-level capabilities find that Odoo's native module integration provides tighter data consistency than Bitrix24's marketplace apps and Zapier-based connections to external tools.
- Bitrix24's Android mobile app suffers from notification failures under moderate load and inconsistent push delivery, creating real productivity gaps for field sales and remote teams. Odoo's mobile app provides a more consistent experience across iOS and Android with full CRM access, activity logging, and document capture, and its open-source mobile codebase means bugs are visible and fixable by the community rather than dependent on Bitrix24's internal mobile team priorities.

Questions, answered

## Bitrix24 to Odoo CRM migration questions

How long does a Bitrix24 to Odoo CRM migration take?

Straightforward migrations with under 5,000 Contacts, 2,000 Deals, and no Smart Processes land between two and four weeks. Migrations with multiple Smart Process entities, large activity histories (over 100,000 activity records), or multi-module Odoo targets (CRM + Accounting or Inventory) stretch to eight to fourteen weeks because of schema translation work, batch API extraction time on Bitrix24's 50-request burst limit, and Odoo configuration complexity. The Odoo edition decision (Community vs Enterprise) also affects timeline if the customer needs server infrastructure set up for a self-hosted environment.

Do Bitrix24 Workflows and Business Process Automation templates migrate to Odoo?

No. Bitrix24 Workflows and Business Process Automation (BizProc) templates use a rules-based visual builder that is not compatible with Odoo's workflow model. We do not migrate them as code. We deliver a written inventory of every active Bitrix24 Workflow and BizProc with its trigger, conditions, actions, and a recommended Odoo Workflow Action or server action equivalent. The customer's Odoo implementation partner or internal admin rebuilds them post-migration. Telephony configurations, call routing rules, and IVR flows similarly do not migrate because Odoo has no native telephony equivalent.

Do we lose historical activity data (calls, emails, meetings, notes)?

No, if activity history is in scope. Bitrix24's native CSV export omits activities entirely, so we close this gap by fetching emails, calls, meetings, and notes via the Bitrix24 REST API batch methods. Each activity type maps to an Odoo CRM Log activity record linked to the parent Contact, Company, or Deal. The Bitrix24 Standard plan rate limit of 50 requests per burst makes large activity histories slow to extract — we scope this as a separate phase and warn the customer if the volume will extend the timeline. Bitrix24 Drive files are not included in the standard migration scope because there is no bulk file export API.

Can FlitStack AI migrate Bitrix24 Smart Processes to Odoo?

Partially. Smart Processes with simple field types (string, number, date, single-select enum) are mapped to Odoo custom fields on the appropriate standard object (Contact, Company, or Opportunity) during migration. Smart Processes with complex multi-entity lookups, nested hierarchies, or cross-entity relationships require a custom Odoo module to be built by an Odoo developer or partner because Odoo does not have a native equivalent to Bitrix24's custom entity type. We document every Smart Process schema at scoping and flag any that cannot be handled with standard field mapping so the customer can budget for a custom module build as a separate engagement.

What is the difference between migrating to Odoo Community vs Enterprise?

Odoo Community is free, open-source, and self-hosted — it requires a Linux server, PostgreSQL database, and manual version management. This model suits teams with an IT infrastructure or a preferred hosting provider, but it adds an infrastructure setup phase and ongoing maintenance responsibility. Odoo Enterprise ($25-$70/user/mo) provides cloud-hosted deployment with automatic updates, a support channel, and access to Studio for creating custom fields without code. The migration process is identical for both editions at the data layer; the difference is in the Odoo configuration environment and who manages the server. We help the customer evaluate which edition fits their operational capacity and budget during discovery.

Does FlitStack AI set up the Odoo server and configuration, or just migrate data?

Data migration only. We do not provision Odoo servers, install the Odoo application, configure the CRM module, or rebuild Bitrix24 automations inside the migration scope. For Odoo Community deployments, we document the server requirements and recommend hosting partners, but server setup is the customer's responsibility or a separate engagement with an Odoo implementation partner. For Odoo Enterprise cloud, we can work within an existing Odoo instance the customer has already provisioned. We recommend involving an Odoo implementation partner for CRM configuration, pipeline stage design, and automation rebuild regardless of edition.

## Related migrations

[![](https://flitstack.ai/platforms-trim/odoo-crm.webp) Migrate to **Odoo CRM** Every source we move into Odoo CRM, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/odoo-crm)

### [Odoo implementation](https://flitstack.ai/services/odoo-implementation)

[Set up Odoo CRM and migrate into it as one engagement.](https://flitstack.ai/services/odoo-implementation)

[See the service →](https://flitstack.ai/services/odoo-implementation) [**Aweber to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/aweber/to/odoo-crm) [**Zoho CRM to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zoho-crm/to/odoo-crm) [**Salesforce to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/odoo-crm) [**Attio to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/odoo-crm) [**Flowlu to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/flowlu/to/odoo-crm) [**Dynamics 365 to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/odoo-crm) [**Bitrix24 to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/salesforce-sales-cloud) [**Bitrix24 to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/dynamics-365-sales) [**Bitrix24 to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/hubspot)

## Sources: official documentation

1. [Export and import data — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html)
2. [Import products — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/sales/sales/products_prices/products/import.html)
3. [Odoo Online programmatic throughput limits — Odoo Forum](https://www.odoo.com/forum/help-1/odoo-online-throughput-limits)
4. [Data Cleaning — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/productivity/data_cleaning.html)
5. [Datetime field reference — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/developer/reference/backend/orm.html#datetime-fields)
6. [Upload size limit in Odoo — Odoo Forum (128 MiB cap)](https://www.odoo.com/forum/help-1/upload-size-limit-in-odoo-221095)
7. [Fields and widgets — Odoo 19.0 documentation (Studio)](https://www.odoo.com/documentation/19.0/applications/studio/fields.html)

Get a quote

## Moving from Bitrix24 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](https://flitstack.ai/contact)
