Migrate from Bigin by Zoho CRM to Twenty CRM

Bigin Contacts map directly to Twenty CRM Person records. We map First Name, Last Name, Email, Phone, and Address fields. Owner assignment maps to the Twenty CRM workspace Member by email match. Any Bigin custom contact fields (created via Developer Console with <topping_namespace>__<field_label> naming) are pre-validated against Twenty CRM's custom field system and mapped explicitly. Contacts linked to Companies in Bigin are matched to Twenty CRM Organizations by domain or name before import so the relationship is satisfied at insert time.

Bigin Companies (API name: Accounts) map to Twenty CRM Organizations. We use the Company domain as a matching key for deduplication if the Organization already exists. Organization address, industry, size, and any custom fields migrate as custom properties on the Organization record. Company-Contact linkages are preserved through the Organization-Person relationship in Twenty CRM.

Bigin Deals map to Twenty CRM Opportunities. The Deal Amount, Closing Date, Stage, and Description migrate directly. The Bigin Deal owner maps to the Twenty CRM Opportunity assignee by email. Any Bigin custom deal fields are mapped to custom Opportunity fields. We flag Deals without a linked Contact or Company at migration time so the customer can decide whether to attach them to a generic Organization or clean up the data before import.

Bigin Pipelines and their sub-pipelines represent a hierarchical container that has no direct Twenty CRM equivalent. We flatten each Bigin pipeline into a named Opportunity Stage group in Twenty CRM. Sub-pipeline names become stage display names, and sub-pipeline order maps to stage sort order. If Bigin has multiple top-level pipelines (3 on Express, unlimited on Premier), we create separate stage groups in Twenty CRM and add a custom pipeline_name__c field on Opportunity to preserve the original grouping context.

Bigin Products map to Twenty CRM Products. We migrate Product Name, Unit Price, Tax, and Description fields. Product-Opportunity line-item relationships in Bigin (if used for quoting) map to Opportunity line items in Twenty CRM. Custom product fields created in Bigin via the Developer Console are mapped to Twenty CRM custom product fields.

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Twenty CRM Tasks. Due date, status, priority, and assignee all transfer. We resolve Bigin task owners to Twenty CRM workspace Members by email and set the linked record (Person, Organization, or Opportunity) using Twenty CRM's foreign-key references. Tasks without a valid linked record are imported as orphaned Tasks with a note flagging the missing parent.

Bigin Events (meetings, appointments) migrate to Twenty CRM Tasks with the activity type set to calendar. Start and end times, location, and recurrence data transfer. Recurring events in Bigin are exported individually at the occurrence level so that each occurrence lands as a separate Task in Twenty CRM. Attendee information is preserved as a custom field on the Task since Twenty CRM's standard model does not include a dedicated attendee object.

Bigin Call logs migrate to Twenty CRM Tasks with activity type set to call. Duration, subject, outcome, and any call notes transfer to custom fields on the Task. Call recordings stored as URLs in Bigin migrate as a custom URL field on the Task. We flag any Calls without a linked Contact or Company during scoping.

Bigin Notes migrate to Twenty CRM Comment records attached to the relevant Person, Organization, or Opportunity. The Note body (rich text) transfers to the Comment text field. Note attachments are handled separately (see Attachments mapping). Notes are excluded from Bigin's Bulk Read API, so we use individual record API calls, which consume credits at a higher rate; we budget API credits accordingly during scoping and pace requests to stay within the daily credit window.

Bigin file Attachments migrate to Twenty CRM as file attachments linked to Person, Organization, or Opportunity records. Bigin's Bulk Read API cannot export Attachments, so we use individual record API requests. We flag any file size or type constraints during scoping and handle downloads individually. For large Attachment volumes, we estimate credit consumption and schedule the migration window to avoid hitting Bigin's 100,000 credit daily ceiling on paid plans.

Bigin User records (name, email, role, profile) are matched to Twenty CRM workspace Members by email. The migration user performing the export is matched first, then any additional users. Owners assigned to Deals and Contacts are resolved via this User mapping. Any Bigin user without a matching email in the Twenty CRM destination is flagged for the customer to provision manually before record import resumes.