Migrate from Bitrix24 to Mailchimp

Bitrix24 Contact records map to Mailchimp Audience Members. We use email as the dedupe key for insertion. Phone, address, and responsible user map to Mailchimp merge fields (PHONE, ADDRESS fields). Bitrix24 custom fields on Contact (crm.contact.userfield.list) map to Mailchimp merge fields of equivalent type: string fields become TEXT merge fields, date fields become DATE merge fields, enum dropdowns become dropdown merge fields. Subscription status (EMAIL_WORK, FM倒在地) from Bitrix24 maps to Mailchimp Status (subscribed, unsubscribed, pending, cleaned).

Bitrix24 Company records do not have a direct Mailchimp equivalent because Mailchimp tracks contacts at the individual subscriber level, not at the organizational level. We map Company name to a TEXT merge field (COMPANY) on the Audience Member and apply the company name as a Tag on every Contact linked to that Company. This preserves the company relationship for segmentation (e.g., tag-based filtering by client company) without creating a separate Company object in Mailchimp.

Bitrix24 Lead records map to Mailchimp Audience Members. The Lead Status field from Bitrix24 (NEW, IN_PROCESS, CONVERTED, JUNK, DUPLICATE) migrates as a TEXT merge field LEAD_STATUS for segmentation purposes. If the customer uses Bitrix24's lead score, we map it to a NUMBER merge field LEAD_SCORE. We deduplicate Leads against existing Contacts by email match before insertion to prevent duplicate subscribers in the Mailchimp Audience.

Bitrix24 custom fields (crm.*.userfield.list) on Contacts and Leads are mapped to Mailchimp merge fields during scoping. We read the field schema (field type, enum options, required flag) from Bitrix24 and create matching merge fields in the Mailchimp Audience. Enum options become dropdown merge fields with matching values. File-type custom fields do not migrate to Mailchimp because Mailchimp does not support file attachments on audience members.

Bitrix24 Products with SKU, price, and description map to Mailchimp Product records if the destination Mailchimp account has Commerce features enabled. Product-deal linkage is not preserved because Mailchimp Products are tied to e-commerce orders rather than CRM deal line items. We recommend the customer decide during scoping whether Commerce is required or whether Products can be documented as a reference table only.

Bitrix24 does not have a native tagging object on Contact and Lead like some CRMs, but teams commonly store tag-like data as multi-checkbox custom fields. We extract these values and create Mailchimp Tags per distinct checkbox option. This allows customers to rebuild segments in Mailchimp based on their original Bitrix24 tag taxonomy without manual re-entry.

Bitrix24 Deals carry pipeline stages, deal amounts, and contact links that have no Mailchimp equivalent. Mailchimp does not manage sales pipelines, deal values, or stage progression. We extract the deal amount and linked contact email as Note on the Audience Member for reference, but pipeline stages, deal IDs, and deal-specific fields are not migrated. The customer receives a written Deal export CSV for reference.

Bitrix24 pipeline stages are CRM workflow concepts with no Mailchimp analog. Mailchimp segments audiences by merge field values, tags, and engagement behavior, not by deal stage values. We do not migrate pipeline stages. We recommend the customer identify any stage-based data (e.g., customer segment tier) that should be stored as a Mailchimp merge field or tag instead.