Migrate from Bitrix24 to Nutshell

Bitrix24 Companies map to Nutshell Accounts. We extract company name, phone, email, address, website, and custom fields via crm.company.list and map to Account fields. Company is the first object imported because Nutshell Accounts must exist before we can link People (Contacts) to them. The ACCOUNT_COMPANY multi-link in Bitrix24 resolves to the Account field on Nutshell People.

Bitrix24 Contacts map to Nutshell People. We extract name, email, phone, address, responsible user, and custom fields via crm.contact.list. The CONTACT_COMPANY multi-link field resolves to the AccountId in Nutshell by matching Company name to Account name during import. If a Contact references multiple Companies, we attach the primary (first-listed) Company and flag the secondary associations for manual reconciliation.

Bitrix24 Deals map to Nutshell Deals with stage, amount, currency, responsible user, and linked Contact or Company. We resolve the linked Contact to a Nutshell People record by email match, and the linked Company to an Account by name match. Bitrix24's multi-pipeline structure maps to Nutshell's pipeline (Pro tier required for multiple pipelines); single-pipeline accounts map to Nutshell's default pipeline without configuration.

Bitrix24 Leads map directly to Nutshell Leads with status, source, and custom fields preserved. Lead conversion (creating a Contact and Deal from a Lead) in Bitrix24 is not automatically replicated in Nutshell; we import Leads as-is and document the conversion cases so the customer's admin can run the equivalent conversion in Nutshell post-migration.

Bitrix24 pipeline stages (from crm.pipeline.list and crm.stage.list) map to Nutshell stage values by name matching. Stage order and status colors migrate. If the destination Nutshell account uses Pro tier and the customer has multiple Bitrix24 pipelines, we configure one Nutshell pipeline per Bitrix24 pipeline with corresponding stage sets.

Bitrix24 Products from the product catalog map to Nutshell Products with SKU, price, description, and unit. Products are imported before Deals so that deal-product line item references resolve during Deal import. Bitrix24 product bundles map to Nutshell product entries with bundled pricing preserved as custom fields if needed.

Bitrix24 Estimates map to Nutshell Quotes linked to the corresponding Deal. We extract line items from crm.quote.item.list and map them to Nutshell Quote line items referencing the imported Products. If Bitrix24 Estimates include PDF attachments, we store them as file links in a Nutshell custom field for manual re-attachment.

Bitrix24 custom fields on Contacts, Companies, Deals, and Leads (fetched via crm.*.userfield.list) map to Nutshell custom fields of equivalent type. String, number, date, and enumeration fields map directly. Multi-select and checkbox fields map to Nutshell's multi-value field format. File fields are not migrated but are flagged for manual re-upload. Custom fields are pre-created in Nutshell before any data import begins.

Bitrix24 Smart Processes are customer-defined CRM entities with REST namespaces crm.item.{entity_code}. Nutshell has no custom object equivalent. We read the Smart Process entity schema dynamically, then evaluate each field: simple fields (string, number, date, enum) migrate as Nutshell custom fields on the relevant standard object (People, Account, or Deal). Complex Smart Processes with multi-level relationships or dependent picklists are documented as a separate schema map for the customer's admin to implement manually or via a third-party data tool post-migration.

Bitrix24 activities (emails, calls, tasks, calendar events) are stored in the timeline and excluded from CSV export. We fetch them via the REST API using batch list methods, respecting the 50-request burst limit on standard plans. Emails and calls migrate as Nutshell Activity records attached to the corresponding People or Deal by matching the related Contact or Deal name. Activity timestamps and content body are preserved; attachments are flagged for manual re-upload. The volume of activity records is scoped separately because large accounts can generate tens of thousands of activity rows requiring extended API extraction time.