Migrate from Bigin by Zoho CRM to Salesforce Sales Cloud

Bigin Contacts have no built-in lead-to-contact lifecycle, so we design the split rule during scoping. Bigin Contacts that represent unqualified prospects (no associated Deal, no purchase history) map to Salesforce Lead. Bigin Contacts attached to Deals or with activity history suggesting a qualified sales relationship map to Salesforce Contact tied to an Account. We preserve any Bigin custom lifecycle or status fields in a custom Salesforce field for audit and segmentation.

Bigin Companies (API name: Accounts) map directly to Salesforce Account. Company name becomes Account Name; website becomes Website; industry and phone migrate to equivalent fields. Account is created before Contact import so that AccountId lookup is satisfied at the moment of Contact insert. Bigin's Company-Contact linkage is preserved as Salesforce Account-Contact relationships.

Bigin Deals map to Salesforce Opportunity. The Bigin deal stage maps to Salesforce StageName via the corresponding Sales Process. Closed-Lost and Closed-Won dates migrate as CloseDate and StageName. Deal amount migrates to Amount. We resolve the Contact (WhoId) and Account (WhatId) references before Opportunity insert.

Bigin Pipelines (up to 3 on Express, unlimited on Premier) become Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process that whitelists the exact stage values from Bigin. Stage probability percentages migrate from Bigin to Salesforce StageProbability, rounded to the nearest integer. This configuration happens in the destination org Sandbox before any record data is migrated.

Bigin Products map to Salesforce Product2 records with Standard Price Book entries created during import. ProductCode migrates from Bigin's SKU field. Price book entries are activated during migration so that OpportunityLineItems can reference them.

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Salesforce Task with Status, Priority, ActivityDate, and subject preserved. Task assignment resolves Bigin owner email to Salesforce User ID via the User mapping. The WhatId on Task points to the migrated Account or Opportunity.

Bigin Events migrate to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Recurring events in Bigin are exported as individual Event records; we note any recurrence patterns for the customer admin to rebuild as Salesforce Event recurrence rules. EventRelation records link attendees to migrated Leads, Contacts, and Users.

Bigin Call logs migrate to Salesforce Task with TaskSubtype=Call. Call duration, disposition, and outcome migrate to custom Task fields. The WhoId on the Task points to the migrated Contact or Lead; ActivityDate preserves the original call timestamp for timeline ordering.

Bigin Notes migrate to Salesforce Note records. Bigin's Bulk Read API excludes Notes, so we use individual Bigin API calls per Note record, which consume credits at a higher rate. Notes are linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. Large note migrations require explicit credit budgeting during scoping.

Bigin Attachments migrate to Salesforce ContentDocument and ContentVersion records. Like Notes, Attachments are excluded from Bigin's Bulk Read API and require individual API calls, which consume more credits per record. We extract attachment metadata (filename, MIME type, size, record association) first, then download and re-upload files through Salesforce's Attachment or Files object. Any file size or format limits are flagged during scoping.

Bigin custom fields created via Developer Console use the <topping_namespace>__<field_label> naming convention. These map to Salesforce custom fields with the __c suffix and require explicit field-type validation during scoping (text to text, number to number, date to date, picklist to picklist). Custom fields are scoped per module in Bigin and map to the equivalent Salesforce object. We pre-create the destination custom fields before any record data loads to avoid field-missing import failures.

Bigin Users (pipeline owners) map to Salesforce User records by email match. We extract every distinct owner referenced on Deals, Contacts, Companies, Tasks, Events, and Calls and match by email against the destination Salesforce org. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import proceeds.