Migrate your Bigin by Zoho CRM data

Standard contact record with name, email, phone, address, owner assignment, and lifecycle fields. Bigin's Contacts module is fully accessible via API with OAuth 2.0 and supports bulk export up to 200,000 records per job. We map Contacts 1:1 in most migrations.

Companies (API name: Accounts) store organizational records linked to contacts and deals. Full CRUD support via API. We preserve Company-Contact linkages during migration and map any custom Company fields that follow the topping namespace convention.

Deals are the core pipeline object in Bigin, tied to a Pipeline and Stage. Each Deal can have multiple tasks, events, calls, and notes attached. We preserve Deal stage history, owner assignments, and linked records during migration.

Pipelines are top-level organizational containers containing sub-pipelines and deal stages. Bigin allows multiple named pipelines per account (3 on Express, unlimited on Premier). We preserve the pipeline hierarchy and stage order when migrating between CRMs.

Product catalog module for line-item management on deals and invoices. Products have name, unit price, tax, and description fields. Fully exportable via API. We map Products including any custom product fields.

Task records linked to Contacts, Companies, or Deals with due dates, status, and owner assignments. Exportable via API and bulk read. We preserve task linkages to parent records and due date ordering.

Calendar events linked to records with start/end times and recurrence data. Bigin's bulk read API exports non-recurring events individually and squashes recurring events into a single entity. We handle recurring event flattening during import scoping.

Call logs associated with Contacts, Companies, or Deals containing duration, subject, and outcome. Exported via standard module API. We preserve call-to-record linkages.

Notes module stores free-text annotations on any record. Available in standard API but excluded from Bulk Read API. For large note migrations we use individual record API calls, which consume more credits.

File attachments stored against Contacts, Companies, Deals, or other modules. Full API support but excluded from Bulk Read. We migrate attachments via individual API requests and flag any file size or format restrictions upfront.

Custom fields created via the Developer Console use the <topping_namespace>__<field_label> naming convention and are scoped per module. We map these fields explicitly during migration scoping, validate their existence in the destination, and flag any missing destination fields for manual creation before migration runs.

User records include name, email, role, and profile. Bigin-to-Zoho CRM migrations map users by default and cannot be modified. In cross-vendor migrations we match users by email and flag unmatched owner IDs for reassignment.