Migrate from Bitrix24 to Pipedrive

Bitrix24 Leads map directly to Pipedrive Leads. We preserve the lead status, source, responsible user, and any custom fields via Bitrix24's crm.lead.list endpoint. The lead-to-contact conversion history is not carried forward; Pipedrive treats new Leads as fresh records. Any Bitrix24 lead scoring values stored in custom fields migrate to Pipedrive custom Lead fields for the sales team to act on after cutover.

Bitrix24 Companies map to Pipedrive Organizations. We extract via crm.company.list and preserve company name, address, phone, email, requisites, and custom fields. Organization is the first record type imported so that the Organization ID is available for resolving the Person-Organization link during Contact import. The Bitrix24 Company type or industry field maps to a Pipedrive custom field since Pipedrive Organizations lack a native type classification.

Bitrix24 Contacts map to Pipedrive Persons with a critical resolution step: Bitrix24 allows a Contact to link to multiple Companies via the CONTACT_COMPANY multi-link field, but Pipedrive Persons link to exactly one Organization. For contacts with a single primary company, we link to that Organization. For contacts with multiple active company links, we select the primary by most recent activity or most recent deal association, and flag the secondary company links in a custom notes field for the customer's admin to review and redistribute if needed.

Bitrix24 Deals map to Pipedrive Deals. Each Bitrix24 pipeline becomes a Pipedrive pipeline, and each Bitrix24 deal stage becomes a Pipedrive stage. We resolve the deal's primary Contact reference to a Person ID and the Company reference to an Organization ID at migration time. Stage probability percentages, currency, amount, and responsible user migrate directly. Closed-Lost and Closed-Won status from Bitrix24 map to Pipedrive's closed Won and closed Lost stage states.

We read Bitrix24 pipeline definitions via crm.pipeline.list and crm.stage.list, then create matching Pipedrive pipeline and stage structures before any Deal import. Stage ordering and color coding migrate. Probability values round to Pipedrive's stage probability field. The customer reviews and approves the stage map before production migration so that stage names and positions match their existing sales process.

Bitrix24 Products from the product catalog map to Pipedrive Products with name, SKU, price, and description preserved. Bitrix24's product tax rate and measurement unit fields map to Pipedrive custom product fields if configured. Product is imported before Deals so that the Product ID is available for resolving line-item references in Deal products.

Bitrix24 Estimates map to Pipedrive Proposals, which are available from Pipedrive Advanced tier onward. We preserve line items linked to the product catalog, the estimate total and currency, and the estimate status. Proposal PDFs and attachments are downloaded from Bitrix24 and reattached as files to the corresponding Pipedrive Proposal.

Bitrix24 Tasks map to Pipedrive Activities of type Task. Subtasks and checklists in Bitrix24 flatten to a single task description with line breaks or to a Pipedrive checklist on the Activity record. Observers and delegations are not supported in Pipedrive's Activity model and are documented in a separate task assignment audit file. Task status (in progress, completed, deferred) maps to Pipedrive Activity done status. Bitrix24's 100-task limit on free plans is a source-side constraint we flag during scoping.

Bitrix24 Smart Processes are customer-defined CRM entities that create unique REST namespaces per entity code. Each Smart Process maps to a set of Pipedrive custom fields on the closest standard object (Deal, Person, or Organization), with the Smart Process name preserved in a Pipedrive custom field label. If the Smart Process contains linked entities, we document the relationship in a custom field and a separate reference table. Pipedrive does not support a generic custom object entity type, so complex Smart Process schemas require the customer to review the flattened representation and decide which fields to retain.

Bitrix24 users referenced as responsible owners on Leads, Contacts, Companies, Deals, and Tasks are resolved by email match against the Pipedrive destination account's User table. Any Bitrix24 user without a matching Pipedrive User is placed in a reconciliation queue; the customer's Pipedrive admin provisions the missing User before record import resumes. Inactive Bitrix24 users are mapped to inactive Pipedrive Users to preserve deal attribution and ownership history.