Migrate your Bitrix24 data

Contacts are standard CRM objects with a well-documented REST schema (crm.contact.*). We map name, phone, email, address, custom fields, and the CONTACT_COMPANY multi-link. Bitrix24 enforces a Company link as optional but recommends it; we preserve the distinction during import.

Companies store legal-entity client data with phone, email, requisites, and a direct link to Contacts. The REST API exposes crm.company.* with full CRUD. We preserve company-contact linkage by sequencing Companies before Contacts in the import order.

Deals are the pipeline-work object in Bitrix24 CRM. They carry stage, amount, currency, responsible user, and a linked Contact or Company. We map Deals after Contacts/Companies and link by name-matching to preserve the relationship graph.

Leads are the top-of-funnel object before a Contact or Deal exists. Bitrix24 supports lead status, source, and custom fields. We import Leads and handle the conversion mapping: converting a Lead creates a new Contact and/or Deal automatically on the Bitrix24 side.

Pipeline Stages are defined per-Pipeline and carry a sort order and status color. We read the existing pipeline schema via crm.pipeline.list and crm.stage.list, then map destination stages by name or create new ones, preserving stage history where supported.

Smart Processes are user-defined CRM entities created by the customer. Each creates a separate REST namespace (crm.item.{entity_code}). We read the entity schema dynamically, but because every customer's Smart Process structure is unique, we handle them as mapping work scoped per-engagement.

Products are stored in a product catalog with SKU, price, and description. They can be linked to Deals as line items. We import Products and preserve the deal-product linkage by sequencing Products before Deals.

Estimates (Quotes) link to Deals and carry line items from the Product catalog. We import estimates with their linked deal reference and line-item data via crm.quote.*.

Custom fields are supported on Contacts, Companies, Deals, and Leads via crm.*.userfield.list. We read the field schema at scoping time and map values by type (string, enum, date, file). Enum options must be matched explicitly — new values created in the destination are recorded as warnings.

Activities — emails, logged calls, calendar events, and tasks — are stored in the timeline and are not included in native CSV exports. The REST API can fetch them individually, but the volume and the 50-request burst limit make full activity history migration impractical for accounts with more than a few thousand records.

Tasks are a dual-nature object: they exist inside the CRM module and also as a standalone Tasks module with subtasks, checklists, observers, and time tracking. The 100-task limit on the free plan is a migration-critical flag — we alert customers if their import will exceed this threshold before the free plan cutover.

Drive files attached to CRM entities (contacts, deals, companies) are stored in Bitrix24's document storage. There is no bulk file export API; files must be downloaded individually. We do not migrate Drive files as a standard step and flag the gap during scoping.