Migrate from Bitrix24 to Zoho CRM

Bitrix24 Companies map directly to Zoho CRM Accounts. The company legal name, phone, email, address, and requisites transfer to Account fields. Account is imported first — before Contacts and Deals — because both those objects carry a foreign-key reference to Account in Zoho CRM. Bitrix24's COMPANY_ID becomes the external ID on Zoho Account for dedupe validation during import.

Bitrix24 Contacts map to Zoho CRM Contacts with name, phone, email, address, and custom fields. The CONTACT_COMPANY multi-link from Bitrix24 resolves to a Zoho Account lookup at migration time via company name matching. Bitrix24 enforces a Company association on Contacts; we flag any Contact without a matching Account and place it in a reconciliation queue for the customer to resolve before import resumes.

Bitrix24 Leads map to Zoho CRM Leads with lead status, source, and custom fields preserved. We handle the Bitrix24-to-Zoho status value mapping: Bitrix24 statuses (NEW, IN_PROGRESS, CONVERTED, JUNK, etc.) map to Zoho Lead Status picklist values during the transform phase. Bitrix24's lead custom fields migrate to Zoho Leads custom fields that we pre-create based on the Bitrix24 field schema read at scoping time.

Bitrix24 Deals map to Zoho CRM Deals with stage, amount, currency, responsible user, and linked Contact or Company reference. We import Deals after Accounts and Contacts are committed so that the Account-Name lookup is satisfied. Bitrix24's pipeline stages map to Zoho Deal Stage values; if the customer uses multiple Bitrix24 pipelines, we create Zoho custom Status values or a lookup field to preserve pipeline segmentation.

Bitrix24 pipeline stages are read via crm.pipeline.list and crm.stage.list at scoping time. Each Bitrix24 stage (with its sort order and status color) is mapped to a Zoho CRM Deal Stage value. If the customer uses Bitrix24's Kanban-style pipeline views, we map stage sequence to Zoho Stage display order. Stage-specific automation rules in Zoho are noted for the customer's admin to rebuild as Workflows post-migration.

Bitrix24 Smart Processes are user-defined CRM entities, each exposing a unique REST namespace (crm.item.{entity_code}). We read the entity schema dynamically via crm.item.{entity_code}.fields at scoping time and generate equivalent Zoho Custom Modules with matching field types (string, enum, date, file, etc.). Because every customer's Smart Process configuration is unique, this step cannot be templated — we build the destination schema per migration. Enum option values from Bitrix24 map to Zoho Custom Module picklist options at migration time.

Bitrix24 Products stored in the product catalog (with SKU, price, description) map to Zoho CRM Products. Products must be imported before Deals so that deal line items can reference valid Product records. If Bitrix24 Products are linked to Deals via line items, we preserve the deal-product linkage by importing Products first and resolving the product reference by name or SKU at Deal import time.

Bitrix24 Estimates (Quotes) link to Deals and carry line items from the Product catalog. They map to Zoho CRM Quotes with the linked Deal reference preserved as a lookup. Note that Zoho's own migration documentation specifies a 200-subform record limit with 100 records per subform for Quote line items; we validate this constraint at scoping and flag if the customer's Estimate line-item volume exceeds the limit.

Custom fields on Contacts, Companies, Deals, and Leads are read via crm.*.userfield.list at scoping time. We map values by type: Bitrix24 string fields map to Zoho Single-Line fields; Bitrix24 date/datetime fields map to Zoho Date/DateTime fields; Bitrix24 enum fields map to Zoho Picklist fields with options generated from the Bitrix24 field options. File fields from Bitrix24 map to Zoho Attachments.

Bitrix24 activity history — emails, logged calls, SMS, and comments — is not included in native CSV exports. The REST API can fetch individual activities but the 50-request burst limit on standard Bitrix24 plans makes batch extraction slow. We scope activity extraction separately and migrate it via batch API where the account's activity volume and rate-limit budget allow. Zoho CRM stores activities as Notes, Tasks, and Events; we map migrated records to the appropriate Zoho activity type and link them to the parent Contact, Lead, Account, or Deal by name matching. Activities that cannot be extracted within reasonable migration timelines are excluded and noted in the final reconciliation report.

Bitrix24 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 part of standard scope. If the customer requires file migration, we scope it as a separate line item and extract files via individual authenticated download requests, then re-attach them to the corresponding Zoho CRM records.