Migrate from Bitrix24 to Salesforce Sales Cloud

Bitrix24 Companies map to Salesforce Account. The COMPANY_LEGAL, REQUISITES, and BANK_REQUISITES composite data structures carry legal entity details that we decompose into standard Account fields (BillingAddress, Phone, Website) plus custom fields for requisites data. Company is the first record type we import because Deals carry a foreign-key reference to the parent Company. We use company ID as the dedupe key during import to prevent duplicate Account creation.

Bitrix24 Contacts map to Salesforce Contact. The CONTACT_COMPANY multi-link resolves to AccountId at migration time by matching the Bitrix24 company name to the Salesforce Account name. Bitrix24 custom fields on Contact (from crm.contact.userfield.list) map to Salesforce custom fields by type: string to Text, enum to Picklist, date to Date, file to ContentDocumentLink. PHONE and EMAIL multivalue fields map to Salesforce standard phone and email with additional custom phone/email fields for overflow.

Bitrix24 Leads map to Salesforce Lead. Lead status values (NEW, IN_PROCESS, CONVERTED, JUNK, BAD) map to Salesforce Lead Status with a custom field bx_lead_source__c carrying the original Bitrix24 SOURCE_ID for audit. Bitrix24's converter field (the CRM.person entity) preserves the converted Contact or Deal reference for accounts that already went through the Bitrix24 conversion flow.

Bitrix24 Deals map to Salesforce Opportunity. The Bitrix24 StageId resolves to a Salesforce StageName and RecordTypeId by matching the stage name within the corresponding Pipeline (mapped to a Salesforce Sales Process). Bitrix24 OPPOWORKFLOW items (deal history log) are not migrated as records; they are summarized as custom text fields on the Opportunity for audit. The StageProbability is set per-stage from the Bitrix24 probability percentage.

Bitrix24 Pipelines (crm.pipeline.list) each carry a set of stages (crm.stage.list) with a sort order and probability percentage. Each Bitrix24 Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the migrated stage values. Stage probability percentages map to Salesforce StageProbability with rounding to the nearest integer.

Bitrix24 Smart Processes are user-defined CRM entities that create a unique REST namespace (crm.item.{entity_code}) per process. We read the entity schema dynamically at scoping time via crm.item.{entity_code}.fields.list, extract field types, and create a matching Salesforce Custom Object with the same display name and a __c API name. Lookup fields to Contacts, Companies, and Deals resolve to the corresponding Salesforce IDs at migration time. Every customer has a different Smart Process set; we handle them as configuration-dependent objects rather than a fixed mapping.

Bitrix24 Products (catalog items with SKU, price, description, and image) map to Salesforce Product2. ProductCode maps from bx_product_code. Standard Pricebook entries are created during import with the ListPrice preserved. Products must be imported before any Deal that carries line items.

Bitrix24 line items linked to Deals map to Salesforce OpportunityLineItem. We resolve Pricebook2Id, Product2Id, and the parent OpportunityId at migration time. Quantity, UnitPrice, and TotalPrice migrate directly. If the Bitrix24 deal has no linked product (manual amount entry), the Opportunity is created with Amount instead of line items.

Bitrix24 Estimates (crm.quote.list) link to Deals and carry line items from the Product catalog. They map to Salesforce Quote, which requires the Opportunity to exist first (Quote is a child of Opportunity). Quote status, total amount, and currency migrate directly. Signed Estimate PDFs migrate as ContentDocument attached to the Quote record.

Bitrix24 Activity records (crm.activity.list) include calls, emails, meetings, and tasks with timestamps, body content, and direction. We migrate calls as Task with TaskSubtype=Call and CallDurationInSeconds; emails as EmailMessage with body and HasAttachment flags; meetings as Event with StartDateTime and EndDateTime; tasks as Task. Activities are fetched via batch API calls constrained by the plan-tier rate limit (50 burst on Standard, 250 on Enterprise). We set ActivityDate to the original Bitrix24 timestamp to preserve timeline ordering.

Bitrix24 standalone Tasks (separate from CRM Activities) carry subtasks, checklists, observers, and time-tracking data. Subtasks become child Task records linked by ParentTaskId. Checklists are stored as a JSON custom field on the parent Task because Salesforce native checklists require the Lightning Flow Checklistitem resource. Time logs migrate as custom number fields. The 100-task limit on Bitrix24's free plan is a source-plan constraint we flag during scoping; it does not affect the migration destination.

Bitrix24 Users map to Salesforce User records. We resolve by email match (the most reliable unique identifier across both platforms). Any Bitrix24 User without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Bitrix24 user type (employee, external) maps to Salesforce UserRole and Profile.

Bitrix24 CRM settings (pipeline definitions, deal stages, lead statuses, custom field schemas) are exported via crm.pipeline.list, crm.status.list, and crm.userfield.list. We translate these into Salesforce metadata: Record Types on Opportunity, Lead, and custom objects; Sales Processes per pipeline; and global picklist values for migrated custom fields. Settings migration runs before any data import so that the destination schema is complete and validated in a Sandbox before production.