Migrate from Bitrix24 to Odoo CRM

Bitrix24 Companies map to Odoo Contacts with the is_company flag set to True. 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.

Bitrix24 Contacts map to Odoo res.partner records with is_company set to False. 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.

Bitrix24 Deals map to Odoo crm.lead records with type='opportunity'. 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.

Bitrix24 Leads map to Odoo crm.lead records with type='lead'. 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.

Bitrix24 Pipelines are read via crm.pipeline.list and crm.stage.list. 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.

Bitrix24 Products from the catalog map to Odoo product.template records with Standard Pricing. 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.

Bitrix24 Smart Processes are customer-defined CRM entities stored under crm.item.{entity_code}. Each Smart Process creates a unique REST namespace with its own field schema. We read every Smart Process entity definition at scoping time, extract all custom fields, and pre-create matching Odoo custom fields on the appropriate standard object (Contact, Company, or Opportunity) or as a separate crm.lead.tags entry for simple enumerations. Complex Smart Processes with multi-level hierarchies require a custom mapping document for the Odoo implementation partner to build a dedicated Odoo module.

Bitrix24 Estimates map to Odoo sale.order records in draft state. Line items are preserved with product references resolved to the imported product.template IDs. The linked Bitrix24 Deal becomes the Odoo crm_id on the Sale Order. We import Estimates in draft state to allow Odoo admin to review and confirm after migration rather than converting to confirmed Sale Orders that could trigger inventory or accounting actions.

Bitrix24 Tasks exist in two contexts: CRM-linked Tasks and the standalone Tasks module. CRM-linked Tasks migrate to Odoo crm.lead activities (log records). Standalone Tasks with subtasks and checklists migrate to project.task if the Odoo Project app is installed; otherwise they become CRM activities with a note about the reduced context. The 100-task limit on Bitrix24 free plan is verified at scoping time, and we flag any account that has triggered or is near the limit before migration begins.

Bitrix24 does not include activities in CSV export. We extract email, call, meeting, and note records via batch REST API calls (crm.activity.items.list with 50-record pagination) to close this gap. Each activity type is mapped: emails become CRM Log notes with subtype email; calls become activities with subtype call and duration preserved; meetings become calendar events; notes become CRM Log records. The parent record (Contact, Company, or Deal) is resolved by name or email match before inserting. API rate limits on Bitrix24 Standard (50 burst) mean large activity histories require extended extraction windows.

Bitrix24 Drive files attached to CRM entities are stored in Bitrix24 document storage. There is no bulk file export API; files must be downloaded individually via the document API. We do not include Drive files in the standard migration scope. We provide a written inventory of all CRM-linked documents with their Bitrix24 URLs so the customer's admin can download them manually or via a separate file migration engagement after the CRM data is in Odoo.

Bitrix24 responsible users on Deals, Contacts, Companies, and Leads are resolved by email match against Odoo res.users. We extract every distinct owner referenced across CRM records at scoping time. Any owner without a matching Odoo user is held in a reconciliation queue; the Odoo admin provisions missing users before the import phase resumes. Inactive Bitrix24 users are mapped to inactive Odoo users to preserve the assignment audit trail.