Migrate from Bitrix24 to Twenty CRM

Bitrix24 Company records map directly to Twenty CRM Company. We extract company name, phone, email, requisites, address, and custom fields via crm.company.list. The Bitrix24 COMPANY_ID multi-link field on Contacts is resolved by inserting Companies first, then matching on company name during Contact import. Any Bitrix24 Company without a clear name-match in Twenty CRM is held in a reconciliation queue with the option to create as a new Company or merge into an existing one.

Bitrix24 Contact records map to Twenty CRM Person objects. The Bitrix24 CONTACT_COMPANY multi-link is resolved against the Company records inserted in the previous step. Name, phone, email, address, job title, and custom fields migrate via crm.contact.list. We use email as the deduplication key and flag duplicate Person records for customer review before final import.

Bitrix24 Deals map to Twenty CRM Opportunity. Stage, amount, currency, responsible user, and close date migrate directly. The dealstage property maps to the Twenty CRM pipeline stage. We resolve the CONTACT_ID and COMPANY_ID foreign keys to the newly inserted Twenty CRM Person and Company records before inserting Opportunities, preventing orphaned opportunity records.

Bitrix24 Leads require a split: Leads with no converted Contact map to Twenty CRM Person records in a pre-contact state. Leads that have been converted to Contacts in Bitrix24 are not re-imported as separate records; we confirm they are present in the Contact import. We preserve the original Bitrix24 Lead status and source in custom fields on the Person record for reporting continuity.

Bitrix24 pipeline stages are defined per-pipeline via crm.pipeline.list and crm.stage.list. We read the existing stage schema and map stage names to Twenty CRM pipeline stages, preserving sort order and probability where Bitrix24 defines it. The customer configures the Twenty CRM pipeline and stages before migration so that stage values land in the correct dropdown.

Bitrix24 Smart Processes are user-defined CRM entities with their own REST namespace (crm.item.{entity_code}). Each Smart Process in the source account is dynamically discovered at scoping time, and we map it to a Twenty CRM Custom Object of matching name. Custom field types (string, enum, date, file, link) are mapped to their Twenty CRM equivalents. Any Smart Process that references a Contact, Company, or Deal via a lookup field is sequenced after its prerequisite entities are inserted.

Bitrix24 Products stored in the product catalog (with SKU, price, description) migrate to Twenty CRM as a custom object or standard CRM product entity. The product-deal linkage is preserved by resolving the product reference at the time of Deal-to-Opportunity migration, ensuring line items reference the correct migrated product records.

Bitrix24 Estimates link to Deals and carry line items from the Product catalog. We import Estimates as Opportunity records or as a linked custom object, depending on the customer's reporting needs. The line-item data (product reference, quantity, price) migrates as structured fields on the Twenty CRM record.

Bitrix24 custom fields on Contacts, Companies, Deals, and Leads are read via crm.*.userfield.list at scoping time. We map enum options, date formats, and file field references to their Twenty CRM equivalents. Enum picklists in Bitrix24 become dropdown or multi-select fields in Twenty CRM. Fields with no equivalent in Twenty CRM are flagged for the customer to configure as custom fields post-migration.

Bitrix24 Owners (responsible_user_id on Deals, Contacts, Companies) map to Twenty CRM WorkspaceMembers. We extract distinct owner references across all CRM entities and match by email address. Owners without a matching Twenty CRM user go to a reconciliation queue for the customer to provision before record import resumes.

Bitrix24 activity records (emails, calls, meetings, notes) are not included in CSV export and must be retrieved via batch API calls to crm.activity.list. We extract the activity body, timestamp, type, and responsible user, then insert into Twenty CRM as Note or TimelineEntry records linked to the parent Person, Company, or Opportunity. The Bitrix24 50-request burst rate limit on Standard plans makes activity extraction slow for large accounts; we scope this separately and warn customers if activity volume will extend the migration timeline.

Bitrix24 Tasks linked to CRM entities (Contacts, Companies, Deals) migrate to Twenty CRM Task records with the same title, description, due date, status, and responsible user. Task-subtask relationships are preserved as parent-task references where the destination supports them. Tasks unattached to CRM entities migrate as standalone Twenty CRM Tasks.