Migrate from Bitrix24 to Freshsales

Bitrix24 Contact records map directly to Freshsales Contact. We extract via crm.contact.list and map name, phone, email, address, and custom fields by API field name. The CONTACT_COMPANY multi-link resolves to Freshsales Account by name matching the associated Bitrix24 Company name. Bitrix24 enforces a Company as a required link on Contact; Freshsales does not, so orphan Contacts without a matching Account are imported as standalone records and flagged for reconciliation.

Bitrix24 Company records map to Freshsales Account. We extract via crm.company.list and map company name, phone, email, website, address, and custom fields. The Account is created before any Contact import so that the Account-Contact relationship is satisfied at insert time. Bitrix24 requisites (legal entity banking details stored in custom fields) migrate as custom fields on the Freshsales Account if the destination schema includes them.

Bitrix24 Deals map to Freshsales Deals with stage, amount, currency, responsible user, and linked Contact or Company. We map dealstage to Freshsales deal stage by exact name match, creating the destination stage if it does not exist. Amount and currency migrate as-is. Bitrix24 Deal custom fields map to Freshsales custom deal fields by type: string, number, date, and enum map directly; file attachments do not migrate.

Bitrix24 Lead records map to Freshsales Lead. Both platforms use a Lead as the top-of-funnel object before a Contact or Deal exists. We extract via crm.lead.list and map lead status, source, name, phone, email, and custom fields. Lead status values from Bitrix24 are mapped to Freshsales Lead status options; unmapped statuses are assigned to a default status and flagged for admin review.

Bitrix24 pipeline stages are read via crm.pipeline.list and crm.stage.list. We create matching Freshsales deal stages by exact name match, preserving the Bitrix24 sort order as the stage display order. Stage probability percentages are not natively stored in Bitrix24 and do not transfer; the customer sets these in Freshsales settings post-migration.

Bitrix24 Product catalog entries (SKU, price, description) map to Freshsales Products. We extract via crm.product.list and create Freshsales Product records. Products linked to Deals as line items are sequenced after Products so that the product reference resolves at migration time. Bundle and package products require manual reassembly in Freshsales if they use Bitrix24-specific bundle logic.

Bitrix24 Estimates (Quotes) link to Deals and carry line items from the Product catalog. We extract via crm.quote.list and map to Freshsales Quotes, preserving the linked Deal reference and line-item data. Bitrix24 estimate status maps to Freshsales Quote status. Signed or approved quotes do not carry over the approval workflow state and are reset to draft in Freshsales.

Bitrix24 Smart Processes are customer-defined CRM entities with dynamic REST namespaces (crm.item.{entity_code}). We read each Smart Process entity schema at scoping time, map the fields by type (string to text, number to number, date to date, enum to picklist, link to lookup), and create corresponding Freshsales custom objects. Because every Smart Process schema is unique to the customer's Bitrix24 instance, this phase adds 1-2 weeks to scoping and a $500-$1,500 premium to the base migration cost.

Bitrix24 Tasks from the standalone Tasks module map to Freshsales Tasks. We extract via tasks.task.list and map title, description, responsible user, due date, and status. Bitrix24's 100-task limit on free plans means tasks are often truncated before migration; we alert customers to this before extraction and recommend a paid-tier export for complete task history. Subtasks and checklists flatten into a single task with the parent title; checklist items are appended to the task description.