---
title: "Bitrix24 to Salesforce Migration: Field Mapping & Rollback"
description: "Migrate Bitrix24 to Salesforce 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/salesforce-sales-cloud"
---

# Bitrix24 to Salesforce migration

We migrate Contacts, Companies, Deals, Leads, and Smart Processes from Bitrix24 into Salesforce with the deal-contact linkage resolved through dependency-ordered sequencing, Bitrix24 REST API rate limits handled via batch chunking, and every Bitrix24 custom field mapped to its Salesforce equivalent before any data moves.

Short answer

FlitStack AI migrates accounts, contacts, leads, opportunities and record type + sales process + stages from Bitrix24 to Salesforce, 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: 4-6 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/salesforce-sales-cloud#what-moves)

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

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

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Account Contact Lead Opportunity Record Type + Sales Process + Stage

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

## What moves from Bitrix24 to Salesforce?

Moving from Bitrix24 to Salesforce is a schema translation across two architecturally distinct CRMs.

Read the full summary

Bitrix24 uses flat-rate pricing and a unified Deals-and-Pipelines model; Salesforce uses per-user licensing with a Lead-Contact-Account-Opportunity hierarchy. We resolve the import dependency chain (Companies first, then Contacts, then Deals) by fetching Bitrix24 entities via REST API batch calls rather than relying on the native CSV export, which omits activities, comments, and email history. Smart Processes in Bitrix24 are customer-defined objects with unique REST namespaces; we read their schema dynamically and map them to Salesforce custom objects. Activity history (calls, emails, SMS) is not included in Bitrix24 exports and must be fetched separately via the activity API, which is constrained by the plan-tier rate limit. Workflows, automations, telephony integrations, and Bitrix24 Drive files do not migrate; we deliver a written inventory of every automation for the customer's admin to rebuild in Salesforce Flow.

1:1

### Company → Account

Bitrix24 Companies map to Salesforce Account.

How it maps

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.

1:1

### Contact → Contact

Bitrix24 Contacts map to Salesforce Contact.

How it maps

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.

1:1

### Lead → Lead

Bitrix24 Leads map to Salesforce Lead.

How it maps

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.

1:1

### Deal → Opportunity

Bitrix24 Deals map to Salesforce Opportunity.

How it maps

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.

configuration

### Pipeline Stage → Record Type + Sales Process + Stage

Bitrix24 Pipelines (crm.pipeline.list) each carry a set of stages (crm.stage.list) with a sort order and probability percentage.

How it maps

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.

1:1

### Smart Process → Custom Object

Bitrix24 Smart Processes are user-defined CRM entities that create a unique REST namespace (crm.item.{entity\_code}) per process.

How it maps

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.

******What moves 13 objects

Bitrix24 Salesforce

- Company Account 1:1
- Contact Contact 1:1
- Lead Lead 1:1
- Deal Opportunity 1:1
- Pipeline Stage Record Type transformed
- Smart Process Custom Object 1:1

\+ 7 more in the mapping below

## How Bitrix24 and Salesforce 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                                                                                        | Salesforce                                                                                                   |
| ----------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Lead model              | Leads and Contacts are separate objects with separate lifecycles                                | Lead and Contact are separate objects with explicit Convert action and Account hierarchy                     |
| Company model           | Companies stand alone with a CONTACT\_COMPANY multi-link to Contacts                            | Accounts are the parent entity with Contacts and Opportunities as children                                   |
| Custom object model     | Smart Processes are user-defined entities with custom REST namespaces (crm.item.{code})         | Custom Objects are API-named (\_\_c suffix) with configurable field types and lookups from Professional tier |
| Pricing model           | Flat-rate per plan; headcount growth does not linearly inflate monthly cost                     | Per-user per month; Enterprise starts at $165/user, Professional at $80/user                                 |
| Pipeline structure      | Pipelines defined per CRM with stages sorted by order, applicable to Deals and Smart Processes  | Record Types with Sales Processes whitelisting stage values; unlimited per org                               |
| Activity history export | Not included in CSV export; requires separate batch API calls constrained by 50-req burst limit | Task, Event, and EmailMessage objects; bulk loadable via Bulk API 2.0 with parent-record resolution          |
| Automation              | Workflow Rules, BizProc, and SLA triggers gated at Professional and Enterprise plans            | Salesforce Flow (record-triggered, scheduled, screen) from Professional; Process Builder deprecated          |

## What to watch for in a Bitrix24 to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### CSV export omits activity history and comments

Bitrix24's native CSV export captures only left-side fields (names, statuses, dates, responsible users) for Leads, Deals, Contacts, and Companies.

How we handle it

Emails, calls, SMS, comments, and task checklist data are excluded entirely. We do not treat CSV as a complete data source. We use the REST API's batch list methods (crm.activity.list, crm.timeline.comment.list) to pull secondary data, but the 50-request burst limit on standard plans and the lack of a bulk export endpoint for activities makes this slow for large accounts. We scope activity extraction separately and warn customers if the account's activity volume will exceed reasonable migration timelines.

high

### Smart Process schema is unique per customer

Every Bitrix24 customer creates different Smart Processes with different field sets, lookup relationships, and entity codes.

How we handle it

There is no standard migration path because each Smart Process maps to a different Salesforce custom object. We read the Smart Process schema dynamically at scoping time via crm.item.{entity\_code}.fields.list, but the destination schema must be designed from scratch in Salesforce. If the customer has five Smart Processes with cross-referencing lookups, we create five custom objects with the matching relationships. This work is scoped and priced separately if the initial discovery reveals complex Smart Process interdependencies.

medium

### Import dependency order enforced by foreign-key constraints

Bitrix24 Deals carry a CONTACT\_ID and COMPANY\_ID reference.

How we handle it

Salesforce Opportunities require AccountId and OwnerId. We enforce the correct import sequence: Companies first, then Contacts, then Leads, then Opportunities. Skipping or reordering this sequence results in orphaned deal records in Salesforce (Opportunities with no AccountId) or records with no OwnerId. We build a dependency graph at scoping time and execute each phase with a row-count reconciliation report before the next phase begins.

medium

### Bitrix24 Drive files cannot be bulk-exported

Drive files attached to CRM entities (Contacts, Companies, Deals) are stored in Bitrix24's document storage.

How we handle it

There is no bulk file export API; files must be downloaded individually. We do not migrate Drive files as standard scope. If the customer has a small number of critical documents (under 500), we can download them individually via the Bitrix24 disk.file.download endpoint and attach them as ContentDocument records in Salesforce, but this is manual work and priced separately. Large file volumes require a dedicated file migration workstream.

medium

### Automation rebuild is out of scope

Bitrix24 Workflow Rules, BizProc automations, and SLA triggers do not migrate to Salesforce Flow because they are architecturally different systems with different trigger models, action types, and limit structures.

How we handle it

We do not rebuild them as code. We deliver a written inventory of every active Bitrix24 automation (trigger object, conditions, actions, plan tier required) with a recommended Salesforce Flow equivalent for the customer's admin or a Salesforce partner to rebuild post-migration. This is a standard deliverable included in the migration scope; the rebuild itself is a separate engagement.

## How the migration runs

1. ### Discovery and plan-tier audit

   We audit the source Bitrix24 portal across plan tier (Free/Basic/Standard/Professional/Enterprise), custom fields on every CRM entity, Smart Process list and field schema, pipeline count and stage definitions, activity volume estimates, and telephony and Drive usage.

   What this step covers

   We confirm the REST API rate limit envelope (50 burst on Standard, 250 on Enterprise) and flag whether any source account is on the free plan or approaching the 50-day inactivity threshold. The discovery output is a written migration scope, a Smart Process schema map, and a destination Salesforce edition recommendation.

2. ### Schema design and Smart Process mapping

   We design the destination schema in Salesforce.

   What this step covers

   This includes pre-creating all custom objects (from Smart Process schema), custom fields with type-mapped Salesforce types, Record Types on Opportunity and Lead per Bitrix24 pipeline, Sales Processes per pipeline, picklist values migrated from Bitrix24 status lists, and a custom field bx\_original\_id\_\_c on every migrated object to preserve the Bitrix24 record ID for audit. Schema is deployed to a Salesforce Sandbox via metadata API for validation before production migration begins.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.

   What this step covers

   The customer's RevOps lead spot-checks 25-50 random records per object against the Bitrix24 source, verifies Smart Process lookups resolve correctly, and signs off the schema and mapping before production migration begins. Any field mapping corrections, picklist value mismatches, or Smart Process schema changes happen in the Sandbox iteration, not in production.

4. ### Owner and user reconciliation

   We extract every distinct Bitrix24 user referenced as a responsible user on Contacts, Companies, Deals, Leads, Tasks, and Activities.

   What this step covers

   We match by email against the Salesforce destination org's User table. Bitrix24 users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision (with active or inactive status matching the original Bitrix24 user's active/departed state). Migration cannot proceed past record import because OwnerId references are required on Opportunity and Lead.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Accounts (from Companies), Contacts (with AccountId resolved), Leads, Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries, Line Items, Quotes, Activity history (Tasks, Events, EmailMessages via API batch calls), Tasks (standalone with subtask resolution), and Smart Processes (last, with their inter-object lookups resolved).

   What this step covers

   Each phase emits a row-count reconciliation report. API rate-limit handling uses exponential backoff and chunking to stay within the plan-tier envelope.

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

   We freeze Bitrix24 writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

   What this step covers

   We deliver the automation inventory document to the customer's admin team listing every Bitrix24 Workflow, BizProc, and SLA trigger with its trigger conditions, actions, and a recommended Salesforce Flow equivalent. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild automations or configure Salesforce Flow inside the migration scope; that is a separate engagement.

![](https://flitstack.ai/platforms/bitrix24.png) Bitrix24 ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

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 · Salesforce 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

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

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

A quote scales with record volume, Smart Process complexity, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Bitrix24 to Salesforce

- Salesforce dominates in customer service and support capabilities, scoring 85.48 percent on feature coverage versus Bitrix24's 55.17 percent. Teams that use Bitrix24 for combined sales and service workflows cite Service Cloud as the primary driver to migrate when the service function matures and requires entitlements, case teams, omni-channel routing, and SLA management beyond what Bitrix24's basic ticketing provides.
- Bitrix24's market position is significantly smaller than Salesforce's: 9,599 customers versus 145,471 in the sales management category, with Salesforce holding 14.32 percent market share versus Bitrix24's 0.95 percent. Teams migrating to Salesforce gain access to the AppExchange ecosystem with over 9,000 listings, including native ERP connectors, CPQ, and revenue intelligence tools that have no Bitrix24 equivalent.
- Salesforce's AI capabilities (Einstein Lead Scoring, Einstein Relationship Insights, Einstein Analytics) provide predictive and relational intelligence that Bitrix24's AI tools do not match for enterprise sales operations. McKinsey research indicates AI-driven CRM activities can increase sales by 50 percent and reduce call time by 60-70 percent, and Salesforce's Einstein platform is the primary implementation vehicle for those gains in the CRM space.
- Bitrix24's cluttered interface and steep learning curve consistently generate negative reviews from non-technical users, with Capterra reviewers rating ease of use at 4.0 versus Salesforce's 4.1 on the same Capterra comparison. Teams that onboarded Bitrix24 as an SMB tool find Salesforce's structured data model and AppExchange ecosystem easier to extend as the organization scales without the UI complexity that accumulates in Bitrix24 as more modules are activated.
- Bitrix24's free plan carries a 50-day inactivity auto-deletion that destroys the entire account without warning if no user logs in, combined with a 5GB shared storage cap and a 100-task hard limit. Teams that use Bitrix24 as a back-office system or seasonal tool lose data permanently. Salesforce's per-user model does not carry these traps, making Salesforce more reliable as a long-term system of record.

Questions, answered

## Bitrix24 to Salesforce migration questions

How long does a Bitrix24 to Salesforce migration take?

Migrations under 20,000 Contacts and 5,000 Deals with no Smart Processes land between four and six weeks and complete in one to two Sandbox iterations plus one production run. Migrations with active Smart Processes (requiring schema design and custom object pre-creation), large activity histories (over 300,000 records), or multi-pipeline Bitrix24 setups move to eight to fourteen weeks because of API extraction time, Smart Process mapping complexity, and Salesforce Sandbox validation cycles. Discovery and scoping add two to three weeks regardless of size.

Do Bitrix24 Workflows, BizProc automations, and telephony integrations migrate to Salesforce?

No. Bitrix24 Workflow Rules and BizProc (Business Process) automations are structurally different from Salesforce Flow and cannot be migrated as code. Telephony integrations (Bitrix24's built-in VOIP, call recording, and IVR) have no Salesforce Sales Cloud equivalent and require a third-party CTI adapter (NICE, Five9, or a Salesforce-native dialer) post-migration. We do not rebuild automations or configure CTI inside the migration scope. We deliver a written inventory of every active Bitrix24 automation with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent for the customer's admin or a Salesforce partner to rebuild post-migration.

What happens to Bitrix24 Drive files during migration?

Bitrix24 Drive files (documents attached to CRM entities) cannot be bulk-exported; there is no bulk file export API and files must be downloaded individually. We do not migrate Drive files as standard scope. If the customer has a small number of critical documents (under 500), we can download them via the disk.file.download endpoint and attach them as ContentDocument records in Salesforce, but this is priced separately because it is manual work. Large file volumes require a dedicated file migration workstream. Bitrix24's document management hierarchy does not map to Salesforce's ContentWorkspace (Library) model.

Can we keep Bitrix24 for internal operations while moving sales to Salesforce?

Yes. A hybrid stack is common for teams that use Bitrix24 for HR, tasks, projects, or internal communications but want Salesforce for the sales process. We migrate the CRM objects (Contacts, Companies, Deals, Leads, Smart Processes) to Salesforce and leave the operational modules (Tasks, Projects, HR, Telephony) in Bitrix24. The customer maintains both subscriptions during the transition and can decommission Bitrix24 once the CRM migration is validated. We coordinate the cutover so that no new CRM records are created in Bitrix24 after the migration window opens.

Do we lose historical call, email, and meeting data?

Activity history is not included in Bitrix24's native CSV export and must be fetched separately via crm.activity.list. We extract calls, emails, meetings, and tasks via batch API calls, but the plan-tier rate limit (50 requests on Standard, 250 on Enterprise) makes large activity migrations slower. We scope activity extraction separately and warn customers if the volume will push timelines beyond six weeks. For accounts with fewer than 50,000 activity records, we can typically extract them within the standard migration timeline. For larger volumes, we recommend a phased approach: core CRM records first, activity history in a second phase.

How do you handle Bitrix24 Smart Processes during migration?

Smart Processes are customer-defined entities with unique REST namespaces (crm.item.{entity\_code}) that have no Salesforce standard equivalent. We read each Smart Process schema dynamically at scoping time via crm.item.{entity\_code}.fields.list, extract field types and lookups, and design a matching Salesforce Custom Object. Cross-Smart Process lookups (one Smart Process referencing another) require a two-pass import: first Smart Process, second Smart Process with the lookup IDs resolved from the first pass. Smart Process migration is priced after discovery because the number and complexity of processes varies per customer.

What if some Bitrix24 users do not have Salesforce accounts yet?

We extract every distinct Bitrix24 user referenced on any CRM record (as a responsible user or owner) and match by email against the Salesforce User table. Users without a matching Salesforce User are held in a reconciliation queue. The customer's Salesforce admin provisions the missing users (active or inactive depending on whether the original Bitrix24 user is still employed) before we proceed to record import. Migration cannot complete for records that require an OwnerId because Salesforce enforces the foreign-key constraint. We flag any user without an email match as an error record and pause that phase until the queue is cleared.

## Related migrations

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

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

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

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Close to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/salesforce-sales-cloud) [**SuiteCRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/suitecrm/to/salesforce-sales-cloud) [**Jobber to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/salesforce-sales-cloud) [**Sugarcrm to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sugarcrm/to/salesforce-sales-cloud) [**Attio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/salesforce-sales-cloud) [**Pipedrive to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/pipedrive/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) [**Bitrix24 to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/odoo-crm)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
6. [Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV](https://dev.to/prince_6a5fbc059971cef8c8/salesforce-data-migration-7-challenges-and-how-to-solve-them-3bb7)
7. [Salesforce Duplicate Management — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/151012/salesforce-duplicate-management-importing-duplicates)

Get a quote

## Moving from Bitrix24 to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
