Bitrix24 to Dynamics 365 migration
We migrate Contacts, Companies, Deals, Leads, and Smart Processes from Bitrix24 into Microsoft Microsoft Dynamics 365 Sales with the Lead-versus-Contact split resolved up front, Bitrix24's free-plan CSV export gaps handled via REST API, and every Bitrix24 custom field mapped to a typed Dynamics 365 field before cutover.
FlitStack AI migrates contacts, accounts, opportunities, leads and sales process + stages from Bitrix24 to Dynamics 365, 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-7 weeks.

What moves from Bitrix24 to Dynamics 365?
Moving from Bitrix24 to Microsoft Microsoft Dynamics 365 Sales is a structural migration across two fundamentally different CRM architectures.
Read the full summary
Bitrix24 uses a flat-rate, all-in-one model with unlimited users on free and a unified contact-company relationship; Microsoft Dynamics 365 Sales uses per-seat licensing and separates Leads (unqualified prospects) from Contacts (qualified buyers attached to Accounts). We resolve the Lead-Contact split during scoping, map Bitrix24's Smart Processes to Dynamics 365 custom tables, and handle Bitrix24's CSV export limitation by pulling activities directly from the REST API within the rate-limit envelope. Automations, pipelines, workflows, telephony configs, and Drive files do not migrate; we deliver a written inventory of every Bitrix24 automation and pipeline for the customer's Dynamics 365 admin to rebuild post-migration.
Contact → Contact
Bitrix24 Contacts map directly to Dynamics 365 Contact.
How it maps
The primary key is the contact's email address, used as the dedupe identifier during import. The CONTACT_COMPANY multi-link from Bitrix24 resolves to an AccountId lookup in Dynamics 365 after the Account import phase completes. Custom fields on Bitrix24 Contact (crm.contact.userfield.list) map to typed Dynamics 365 fields by data type: string to Single Line of Text, integer to Whole Number, date to Date Only, and enumeration to Option Set.
Company → Account
Bitrix24 Companies map to Dynamics 365 Account.
How it maps
Company name serves as the dedupe key. Bitrix24 requisites and legal entity fields map to Account fields including Address fields (street, city, state, postal code, country). We import Account first so that AccountId is available as a foreign key before the Contact import phase begins, preventing orphaned Contact records in Dynamics 365.
Deal → Opportunity
Bitrix24 Deals map to Dynamics 365 Opportunity.
How it maps
The dealstage property maps to Opportunity StageName, and the associated Bitrix24 pipeline maps to a Microsoft Dynamics 365 Sales Process and Record Type that we configure before migration. Closed-Lost reason, closed amount, currency, and responsible user migrate as Opportunity fields. Deal-to-Contact linkage resolves via name-matched lookup on the Contact name field after Contact import completes.
Lead → Lead
Bitrix24 Leads map to Dynamics 365 Lead.
How it maps
Lead status, source, and responsible user transfer directly. Bitrix24 lead conversion (creating a Contact or Deal from a Lead) is handled as a pre-migration flag: we import all Bitrix24 Leads as-is into Dynamics 365 Lead and document which Leads have already been converted in Bitrix24 so the customer's admin can perform the corresponding Lead Convert action in Dynamics 365 post-migration.
Pipeline Stage → Sales Process + Stage
Bitrix24 pipeline stages (crm.pipeline.list, crm.stage.list) map to Microsoft Dynamics 365 Sales Process stage values.
How it maps
We read the stage sort order and probability from Bitrix24 and replicate the same stage structure as a Microsoft Dynamics 365 Sales Process. The customer selects whether to create one unified Sales Process or separate processes per pipeline during scoping.
Smart Process → Custom Table (Custom Entity)
Bitrix24 Smart Processes are user-defined CRM entities with individual REST namespaces (crm.item.{entity_code}).
How it maps
Each Smart Process requires a corresponding Dynamics 365 custom table with columns pre-created to match the Smart Process field schema. We read the entity schema dynamically during scoping, pre-create the destination custom table via the Dataverse API, and import records in a final phase after all standard object imports are complete. Smart Process records with lookups to Contacts, Companies, or Deals resolve the parent reference at migration time.
- ContactContact1:1
- CompanyAccount1:1
- DealOpportunity1:1
- LeadLead1:1
- Pipeline StageSales Processtransformed
- Smart ProcessCustom Table1:1
+ 8 more in the mapping below
How Bitrix24 and Dynamics 365 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 | Dynamics 365 |
|---|---|---|
| Contact and company model | Single CRM entity with Contact carrying a COMPANY_ID multi-link to Companies | Separate Account and Contact objects; Contacts attach to Accounts via an explicit lookup relationship |
| Lead model | Leads exist as a separate top-of-funnel object convertible to Contact or Deal | Separate Lead object convertible to Contact tied to Account; requires explicit split rule at migration time |
| Custom objects | Smart Processes available on Standard ($124/mo) and above as user-defined entities with individual REST namespaces | Custom tables available on Sales Professional ($65/user/mo) and above; no setup fee for custom entities |
| Pricing model | Flat-rate per-plan, not per-seat; $124/mo Standard for the entire team, $249/mo Professional | Per-user per-month; $65/user/mo Sales Professional scales linearly with headcount |
| Automation | Workflow Designer and BizProc (Business Process) Designer gated behind Professional plan | Power Automate and Microsoft Dynamics 365 Sales automation available from Sales Enterprise ($95/user/mo) |
| Telephony | Built-in VOIP with call recording, IVR, and routing on Standard and above | No native telephony; Teams integration or a third-party ISV such as Five9 or Nuance provides comparable functionality |
| Activity export | CSV export captures left-side fields only; emails, calls, comments, and SMS require separate REST API batch calls | Activities migrate via Dataverse REST API with ActivityPointer/ActivityParty pattern; native CSV import not suitable for large histories |
What to watch for in a Bitrix24 to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Bitrix24 CSV export omits all activity history
The native CSV export in Bitrix24 only captures left-side fields for Leads and Deals (names, statuses, amounts, responsible users).
How we handle it
Emails, calls, SMS, comments, and meeting notes are stored in the activity timeline and are not included in any CSV export. We pull all activity records via crm.activity.list REST API calls, but the 50-request burst limit on standard Bitrix24 plans (2 req/sec sustained) makes large activity migrations slow. We scope activity extraction separately at discovery and warn customers if the account has more than 100,000 activity records, because migration timelines scale directly with activity volume under the rate-limit constraint.
Dynamics 365 requires a Lead-Contact split that Bitrix24 does not enforce
Bitrix24 does not distinguish between a prospect and a qualified contact; all CRM entities live in a single Contact model with a lifecycle flag.
How we handle it
Dynamics 365 uses separate Lead and Contact objects, and the split rule must be defined before migration begins. We design the split during scoping: typically Bitrix24 Leads import as Dynamics 365 Leads, and Bitrix24 Contacts import as Dynamics 365 Contacts with a linked Account. Any Bitrix24 Contact records that represent unqualified prospects need to be evaluated against the split criteria and routed accordingly. Skipping this design step results in Contacts without Accounts or Leads that should have been converted on day one.
Smart Processes create non-standard REST namespaces that require pre-schema mapping
Bitrix24 Smart Processes are user-defined entities; each creates its own REST namespace at crm.item.{entity_code}.
How we handle it
The field schema (field types, required flags, lookups) varies per Smart Process and per customer. We read each Smart Process schema dynamically during scoping, but we cannot migrate data into a destination custom table that does not yet exist. Pre-creating Dynamics 365 custom tables with matching columns is a prerequisite phase that must complete before Smart Process data can import. If the customer has more than five Smart Processes, the schema pre-creation phase adds a minimum of three to five days to the migration timeline.
Bitrix24 free-plan 50-day inactivity auto-deletion must be addressed before migration
Bitrix24 free-plan accounts are permanently deleted after 50 consecutive days of inactivity, and the entire CRM dataset is lost with no guaranteed restoration.
How we handle it
During migration scoping, we confirm the source Bitrix24 account has an active paid plan or an automated daily login via API token. Any account identified as inactive or at risk enters a protective monitoring protocol. We will not open a migration window on an account that is within 14 days of the inactivity threshold without a confirmed protective measure in place.
Workflows, automations, and telephony configs do not migrate
Bitrix24 Workflow Designer and BizProc (Business Process) automations are configuration-as-code that has no direct equivalent in Microsoft Dynamics 365 Sales .
How we handle it
Power Automate and Dynamics 365 native workflows are the replacement targets but require a separate rebuild engagement. Similarly, Bitrix24's built-in telephony configuration (IVR menus, call routing rules, VOIP settings) does not transfer to Dynamics 365, which has no native telephony module. Teams integration provides meeting scheduling and calling for users with Microsoft 365 E5 or a Teams Phone license, but VOIP setup requires a separate configuration. We deliver a written pipeline and automation inventory document listing every Bitrix24 workflow, BizProc, and telephony rule for the customer's admin to rebuild.
How the migration runs
Discovery and scoping
We audit the source Bitrix24 account via the REST API, capturing Contacts, Companies, Deals, Leads, Smart Processes, Products, Estimates, pipeline schemas, custom field definitions, and owner list.
What this step covers
We also estimate activity volume (emails, calls, tasks, meeting notes) by sampling crm.activity.list. We pair this with a Microsoft Dynamics 365 Sales edition recommendation: Sales Professional ($65/user/mo) covers most migrations; Sales Enterprise ($95/user/mo) is required if the customer needs advanced AI insights, conversation intelligence, or multiple sales processes; Sales Premium ($150+/user/mo) if sales playbook and Viva Sales are in scope. The discovery output is a written migration scope with record counts, pipeline map, Smart Process schema inventory, and automation list.
Lead-Contact split design and Dynamics 365 schema pre-creation
We define the Lead-Contact split rule based on the customer's Bitrix24 data.
What this step covers
Any Bitrix24 Contact record with a lifecycle status below a defined threshold maps to Dynamics 365 Lead; records above the threshold map to Dynamics 365 Contact. We then pre-create the Dynamics 365 environment: custom tables for each Smart Process, custom columns on standard entities (Contact, Account, Opportunity, Lead), Record Types per pipeline, Sales Processes per pipeline, and Option Set values for Bitrix24 enumerations. Schema is deployed into the destination Dynamics 365 Sandbox for validation before any data moves.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using production-like data volume from the Bitrix24 source.
What this step covers
The customer's Dynamics 365 admin reconciles record counts across all entities, spot-checks 25-50 records against the Bitrix24 source for field-level accuracy, and validates the Lead-Contact split logic. Any mapping corrections, missing picklist values, or schema gaps are resolved here. Sandbox sign-off is required before production migration begins.
Owner reconciliation and User provisioning
We extract every distinct Bitrix24 Owner referenced on CRM records and match by email against the destination Dynamics 365 User table.
What this step covers
Owners without a matching Dynamics 365 User go to a reconciliation queue. The customer's admin provisions any missing Users (active or inactive depending on whether the original Bitrix24 owner is still active). This step is a hard blocker for subsequent import phases because OwnerId is required on Opportunity, Contact, and Lead.
Production migration in dependency order
We run production migration in strict dependency sequence: Accounts (from Companies, AccountId resolves), Contacts (with AccountId linked), Leads (with split applied), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Price List entries (if importing quoting), Quote Headers and Quote Details, then Smart Process custom tables (last, because they often have lookups to standard entities).
What this step covers
Activity history (calls, emails, meetings) migrates via Dataverse REST API in chunks with exponential backoff. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze writes to Bitrix24 during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record.
What this step covers
We deliver the pipeline, automation, and telephony inventory document to the customer's admin team for rebuild in Power Automate and Microsoft Dynamics 365 Sales processes. We support a one-week hypercare window where we resolve reconciliation issues raised by the sales team. We do not rebuild Bitrix24 Workflows or BizProc automations as Power Automate flows inside the migration scope; that is a separate engagement or an internal admin task.
Bitrix24 - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Pricing reflects record volume, custom object complexity, and whether Bitrix24 Smart Processes require pre-creation of Dynamics 365 custom tables. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Bitrix24 to Dynamics 365 →Why teams move from Bitrix24 to Dynamics 365
- Teams running Bitrix24 inside a Microsoft-centric environment (Office 365, Teams, SharePoint, Exchange) cite integration friction as a daily productivity drain. Bitrix24's REST API and webhook connectors require custom configuration to keep emails, calendar events, and documents in sync. Microsoft Dynamics 365 Sales is natively built on the Microsoft stack: contacts sync with Exchange, meetings schedule through Teams, and SharePoint document management attaches to Account and Opportunity records without third-party connectors. One reviewer on Reddit noted moving to Dynamics 365 after two years on Bitrix24 specifically because Office 365 subscriptions, Teams, and SharePoint integration were already in place and Bitrix24 could not close the gap.
- Microsoft Dynamics 365 Sales supports over 9,000 AppExchange-certified integrations versus Bitrix24's smaller third-party marketplace. Organizations requiring native CPQ (CPQ Ninja, Salesforce CPQ), ERP connectors (SAP, Oracle, NetSuite), revenue intelligence (Clari, Gong), or contract lifecycle management (DocuSign CLM, Conga) move to Dynamics 365 because these connectors are AppExchange-certified rather than routed through Zapier or Albato. Reviewers on Capterra and ITQlick consistently cite the ecosystem depth as a reason Dynamics 365 wins at evaluation against Bitrix24.
- Enterprise and mid-market organizations with complex, multi-territory pipeline reporting find Bitrix24's analytics surface insufficient without significant custom development. Microsoft Dynamics 365 Sales with its native reporting engine and Power BI integration supports multi-dimensional pipeline analysis across product lines, sales territories, and non-standard fiscal periods. A case study from OnTargIT evaluating the move away from Bitrix24 specifically calls out Dynamics 365's adaptability and proactive response capabilities as reasons cited by revenue operations teams for switching.
- Bitrix24's free plan carries three compounding traps for teams migrating data out: a 5GB shared storage cap, a 100-task hard limit, and a 50-day inactivity auto-deletion of the entire account. Organizations that used Bitrix24 as a low-cost entry CRM and have since scaled find the flat-rate pricing of Dynamics 365 ($65/user/mo Sales Professional) more predictable for reporting and licensing audits, especially when combined with existing Microsoft 365 E3 or E5 commitments that include Dynamics 365 licensing entitlement.
Questions, answered
Bitrix24 to Dynamics 365 migration questions
How long does a Bitrix24 to Microsoft Microsoft Dynamics 365 Sales migration take?
Standard-tier migrations under 15,000 Contacts, 5,000 Deals, and no Smart Processes complete in four to seven weeks. Enterprise accounts with large activity histories (over 200,000 records), multiple Smart Processes, or complex custom field schemas move to ten to fifteen weeks because of Bitrix24 REST API rate-limit handling, Smart Process schema pre-creation, and the pipeline rebuild inventory work. Microsoft Dynamics 365 Sales implementation timelines cited by implementation partners range from six to fourteen months for full enterprise deployments, but our data migration scope focuses on record transfer and does not include the broader Dynamics 365 implementation work.
What happens to Bitrix24 Smart Processes during migration?
Bitrix24 Smart Processes are user-defined CRM entities (each with its own crm.item.{entity_code} REST namespace) that have no direct Microsoft Dynamics 365 Sales equivalent out of the box. We pre-create a Dynamics 365 custom table for each Smart Process during the schema design phase, mapping field types and any lookup relationships to standard entities (Contact, Account, Opportunity). The custom table is created in a Sandbox first, validated, then deployed to production before the Smart Process data imports. Smart Process records with lookups to other CRM entities resolve their parent references during the import phase. Any Smart Process that contains more than ten custom fields or multi-level lookups requires additional schema mapping time.
Do Bitrix24 Workflows and automations migrate to Dynamics 365?
No. Bitrix24 Workflow Designer and BizProc (Business Process) Designer automations are configuration-as-code that does not have a structural equivalent in Microsoft Dynamics 365 Sales or Power Automate. We do not migrate them as executable automation. We deliver a written inventory document listing every Bitrix24 workflow and BizProc with its trigger, conditions, and actions, along with a recommended Power Automate or Dynamics 365 native workflow equivalent. The customer's Dynamics 365 admin or a Microsoft partner rebuilds the automations post-migration. Telephony configurations (IVR, call routing, VOIP rules) are documented separately and are rebuilt through Teams Phone or a Dynamics 365-compatible telephony ISV.
Can we keep Bitrix24 for non-CRM modules while moving only the CRM data to Dynamics 365?
Yes. Bitrix24 includes Tasks, Drive, HR, and project management modules beyond the CRM. We scope only the CRM objects (Contacts, Companies, Deals, Leads, Smart Processes, Products, Estimates, and Activities) for migration to Microsoft Dynamics 365 Sales . Tasks and Projects can remain in Bitrix24 or be migrated separately through a dedicated project management migration. We do not handle Bitrix24 Drive file migration in the standard CRM scope; those files are documented in a file manifest for manual transfer to SharePoint. The customer can run Bitrix24 and Dynamics 365 in parallel during a transition period, but we strongly recommend a hard cutover date to avoid write conflicts.
How do we handle the Bitrix24 free-plan export gaps during migration?
Bitrix24's native CSV export only captures left-side fields and does not include emails, calls, comments, or SMS from the activity timeline. We do not use CSV export as a primary data source. We use Bitrix24's REST API crm.activity.list endpoint to pull activity records in batches of 50 (the burst limit on standard plans), applying exponential backoff to stay within the 2 req/sec sustained envelope. For large activity volumes, we extract activities as a parallel phase to the primary record migration to maximize throughput. The customer receives a complete activity manifest showing how many records were pulled per type and any gaps due to API pagination or access restrictions on the source account.
Do we lose historical data if our Bitrix24 account has already been inactive for 40+ days?
Potentially yes. Bitrix24 free-plan accounts are permanently deleted after 50 consecutive days of inactivity. Any account at or beyond this threshold has likely already been deleted and the data is unrecoverable. We do not open a migration scope on a Bitrix24 account that shows signs of pending deletion without a confirmed protective measure in place (an active paid plan or an automated daily API login). If the account is on a paid tier (Standard, Professional, Enterprise), the inactivity deletion risk does not apply and the migration can proceed normally. We check account status during discovery and flag any inactive-free-plan accounts immediately.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Zendesk Sell to Dynamics 365Mapping · history · rollbackPipedrive to Dynamics 365Mapping · history · rollbackField Services Workflow and Logistics to Dynamics 365Mapping · history · rollbackHubSpot to Dynamics 365Mapping · history · rollbackOdoo CRM to Dynamics 365Mapping · history · rollbackZoho CRM to Dynamics 365Mapping · history · rollback Bitrix24 to SalesforceMapping · history · rollbackBitrix24 to HubSpotMapping · history · rollbackBitrix24 to Odoo CRMMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Bitrix24 to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote