Migrate from Bigin by Zoho CRM to Pipedrive

Bigin Contacts map directly to Pipedrive Persons. Email, phone, address, owner assignment, and lifecycle fields migrate as typed Person fields. Bigin's custom Contact fields (created via Developer Console with the <topping_namespace>__<field_label> naming convention) map to Pipedrive custom Person fields. We validate the namespace prefix against Pipedrive's custom field registry during scoping and flag any field-label collisions before migration.

Bigin Companies (API name: Accounts) map to Pipedrive Organizations. Company name, website, address, industry, and owner assignment transfer directly. We preserve the Company-to-Contact linkage as a Person-Organization relationship in Pipedrive by mapping Company_ID as the Organization_ID on the corresponding Person record during import.

Bigin Deals map to Pipedrive Deals with stage mapped to Pipedrive Stage. The key structural decision is how Bigin's named Pipelines and sub-pipelines map to Pipedrive's Pipeline and Stage hierarchy. For single-pipeline accounts we create one Pipedrive Pipeline; for multi-pipeline Premier accounts we create multiple Pipedrive Pipelines and assign the corresponding Deal Stage values to each. We preserve deal value, close date, probability, owner, and any custom deal fields.

Bigin Pipelines and sub-pipelines containing named stage lists become Pipedrive Pipelines with Stages configured in the same order. Stage probability percentages migrate from Bigin to Pipedrive Stage probability fields. Bigin's Express plan caps at 3 pipelines and Premier allows unlimited; we match the destination pipeline count to the source tier's entitlement.

Bigin Products (name, unit price, tax, description) map to Pipedrive Products. ProductCode migrates from Bigin's SKU field. We create Pipedrive Price entries linked to each Product so that Products can be added to Deals as line items. Custom Product fields from Bigin's Developer Console namespace map to Pipedrive custom Product fields.

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Pipedrive Activities with type set to Task. Due date, status (open/done), priority, and owner assignment transfer. Task linkages are preserved by setting the linked Person, Organization, or Deal ID as the activity_id in Pipedrive's Activity record. Pipedrive's Activity model supports one parent resource per activity, so multi-linked Tasks use the primary link and secondary links are noted in a custom field.

Bigin Events map to Pipedrive Activities with type set to Meeting. Start time, end time, location, and recurrence data transfer. Note that Bigin's Bulk Read API collapses recurring events into a single entity, so recurring meeting series may appear as one record in Pipedrive after migration. We flag recurring event detection during scoping so the customer can decide whether to expand them manually post-migration or accept the collapsed representation.

Bigin Call logs migrate to Pipedrive Activities with type set to Call. Duration, subject, outcome (disposition), and owner assignment transfer to the corresponding Pipedrive Activity fields. Call recording URLs stored in Bigin's Call module do not migrate through the standard API and are flagged in the scope document for manual re-upload if the customer has a recording retention requirement.

Bigin Notes migrate to Pipedrive Activities with type set to Note. Note content migrates as the Activity's subject and note field. Notes are excluded from Bigin's Bulk Read API, so we use individual record API calls which consume credits at the standard rate (1 credit per call). We estimate the Notes volume during scoping and include it in the credit budget. For large Note migrations (over 5,000 records) we recommend scheduling the migration during off-peak hours to manage credit consumption.

Bigin custom fields created via the Developer Console use the <topping_namespace>__<field_label> naming convention and are scoped per module. We map these explicitly during scoping, validating the topping namespace and field label against Pipedrive's custom field registry. Multi-select picklist, date, currency, and user lookup field types map to their Pipedrive equivalents. Fields without a Pipedrive type equivalent are documented in the scope as manual-rebuild candidates. We do not migrate Formula fields as Pipedrive does not support formula fields as a standard object field type.

Bigin Users (name, email, role) map to Pipedrive Users by email address match. Owner assignments on Contacts, Organizations, Deals, and Activities reference the matched User ID in Pipedrive. Any Bigin Owner without a matching Pipedrive User email goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Bigin users are mapped to inactive Pipedrive users so historical attribution is preserved without granting active seat access.