Migrate from Bitrix24 to Microsoft Dynamics 365 Sales

Bitrix24 Contacts map directly to Dynamics 365 Contact. 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.

Bitrix24 Companies map to Dynamics 365 Account. 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.

Bitrix24 Deals map to Dynamics 365 Opportunity. 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.

Bitrix24 Leads map to Dynamics 365 Lead. 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.

Bitrix24 pipeline stages (crm.pipeline.list, crm.stage.list) map to Microsoft Dynamics 365 Sales Process stage values. 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.

Bitrix24 Smart Processes are user-defined CRM entities with individual REST namespaces (crm.item.{entity_code}). 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.

Bitrix24 Products from the product catalog (SKU, price, description) map to Dynamics 365 Product. ProductCode maps from Bitrix24's article number or SKU field. We import Products before Deals so that ProductId is available for Opportunity Product Line Items. The product-deal linkage migrates as OpportunityProductDetail records in Dynamics 365.

Bitrix24 Estimates map to Dynamics 365 Quote. Quote header fields (total amount, status, expiration date) migrate directly. Line items from the Bitrix24 Estimate link to Dynamics 365 Quote Details referencing the imported Product records. Quote-Account linkage resolves via AccountId after the Account import phase.

Bitrix24 CRM Tasks map to Dynamics 365 Task. Status, Priority, Due Date, and Subject transfer directly. The responsible Bitrix24 user resolves to the corresponding Dynamics 365 User by email match. Subtasks, checklists, and observers are preserved as custom fields or related records if the customer requires them; otherwise they are flagged for manual rebuild. The 100-task free-plan limit is checked during scoping and the customer is advised to upgrade before import if the limit applies.

Bitrix24 Owners (responsible users) map to Dynamics 365 User records. We resolve owners by email address. Any Bitrix24 Owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId is required on Opportunity and Contact in Dynamics 365, making this a blocking dependency for later phases.

Bitrix24 activity records (logged calls, emails, meeting notes) are fetched via batch REST API calls (crm.activity.list) rather than CSV export. Activities are mapped to Dynamics 365 ActivityPointer and related entities: calls to PhoneCall, emails to Email, and calendar events to Appointment. Activity-party relationships (Attendees, Contacts) migrate as ActivityParty records. The Bitrix24 REST API rate limit of 50 requests on standard plans makes large activity volumes slow; we chunk activity extraction in batches and apply exponential backoff.

Bitrix24 custom fields on Contacts, Companies, Deals, and Leads are read via crm.*.userfield.list during scoping. Each custom field maps to a typed Dynamics 365 column: Single Line of Text (string), Whole Number (integer), Date Only (date), Option Set (enumeration), Two Options (boolean). Enum option values in Bitrix24 map to Option Set labels in Dynamics 365. Custom fields are pre-created in the destination environment before any record import begins.

Bitrix24 Drive files attached to CRM entities are not migratable via the Bitrix24 API (no bulk file export; individual download required per file). We document the affected entity list (Contacts, Companies, Deals with attachments) and provide a file manifest with download links and target SharePoint document location paths for the customer's admin to complete manually. Dynamics 365 Record Attachment is not the target; SharePoint integration via the native Dataverse-SharePoint connector is the recommended destination.

Bitrix24's multiple deal pipelines map to Dynamics 365 Record Types on Opportunity. Each Record Type receives its own Sales Process (stage set) and Page Layout, ensuring stage values remain scoped per line of business. Pipeline ordering and pipeline-specific stage probability percentages migrate as part of the Sales Process configuration step.