Migrate from Bigin by Zoho CRM to Zoho CRM

Bigin Contacts map directly to Zoho CRM Contacts. The Bigin Developer Console custom field namespace <topping_namespace>__<field_label> convention is resolved during scoping by querying the Bigin API field metadata and creating matching custom fields in Zoho CRM before migration. Contact owner assignments migrate as Owner lookup references resolved by email match against the Zoho CRM User table.

Bigin Companies (API name: Accounts) map to Zoho CRM Accounts. The Company-Contact linkage is preserved through the AccountId lookup on the migrated Contact record. Any custom Company fields created via Developer Console follow the <topping_namespace>__<field_label> naming convention and require pre-creation in Zoho CRM before data import.

Bigin Deals map to Zoho CRM Deals. Each Bigin Pipeline and sub-pipeline becomes a Zoho CRM Sales Process and Deal Stage configuration that we deploy before migration begins. The dealstage value from Bigin maps to the corresponding StageName in the destination Sales Process. Closed-Won and Closed-Lost reason custom fields migrate to Zoho CRM Loss Reason and Won Reason picklist fields.

Bigin Pipelines and sub-pipelines require pre-configuration in Zoho CRM before Deal migration because the built-in migration tool does not allow mapping modifications. We create Zoho CRM Sales Processes and assign them to Record Types so that deal stages land in the correct scope. Express is limited to 3 pipelines; Premier supports unlimited. We preserve pipeline ownership assignments as Zoho CRM User assignments on the Deal records.

Bigin Products map to Zoho CRM Products, but the Products module is excluded from the built-in Zoho migration wizard and must be handled via direct API extraction from Bigin followed by Zoho CRM API insert. Product name, unit price, tax, and description fields migrate directly. Custom product fields follow the Developer Console naming convention and require pre-creation.

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Zoho CRM Tasks with Status, Priority, Due Date, and owner assignment preserved. The WhatId lookup resolves to the migrated Deals record ID. Tasks are available via both the built-in migration wizard and direct API; we prefer API for large task volumes to manage Bigin credit consumption.

Bigin Events map to Zoho CRM Events with Start DateTime, End DateTime, Location, and description preserved. Recurring events in Bigin are exported as a single entity via Bulk Read and require manual recreation or Events API batch insert in Zoho CRM. The built-in migration wizard notes that Reminders and Repeat options for activities are not synced to avoid duplicate notifications.

Bigin Call logs migrate to Zoho CRM Calls with duration, subject, disposition, and owner preserved. Call recordings stored as attachments require separate handling since the built-in wizard does not migrate record attachments. We flag any call recording file references during scoping and handle them as Zoho CRM Attachments on the Call record via API.

Bigin Notes migrate to Zoho CRM Notes, but Notes are excluded from Bigin's Bulk Read API and must be fetched via individual record API calls. This significantly increases credit consumption per Note (1 credit per API call versus 0.33 credits per record in Bulk Read). We scope the Notes volume separately and budget API credits accordingly.

Attachments embedded within Bigin Notes migrate to Zoho CRM Attachments linked to the parent Note record. File size limits (Zoho CRM caps individual attachments at 25 MB via API) are enforced during extraction. The built-in migration wizard supports Attachments in Notes but not Attachments inside CRM records, which is a documented limitation of the native tool.

Bigin Users migrate to Zoho CRM Users by email match. Owner assignments on Contacts, Accounts, Deals, Tasks, Events, and Calls reference User IDs that must resolve correctly during migration. Users must be provisioned in Zoho CRM before record migration begins; the built-in migration tool handles this automatically if both accounts share the same Zoho organization credentials.

Bigin Developer Console custom fields use the <topping_namespace>__<field_label> API naming convention and are scoped per module. We query the Bigin topping metadata during scoping, extract all custom field definitions (label, API name, type, picklist values), create matching custom fields in Zoho CRM with equivalent types and picklists, and then import data. Zoho CRM's custom field limits (unlimited on all paid tiers versus 10-25 on Bigin) remove this constraint at the destination.