Migrate from Bigin by Zoho CRM to Microsoft Dynamics 365 Sales

Bigin Contacts map directly to Dynamics 365 Contacts. We use email address as the dedupe key. Contact fields including name, email, phone, address, and any custom fields migrate as typed fields. Bigin's contact Owner assignment maps to the Dynamics 365 OwnerId by email-matched User lookup. Any contact without a matching Dynamics 365 User is placed in a reconciliation queue for the admin to resolve before the Contact phase completes.

Bigin Companies (API name: Accounts) map to Dynamics 365 Accounts. The company name becomes Account Name, and domain data maps to the Website field. We preserve any Company-Contact linkages and resolve AccountId on Contact records at migration time. Custom Company fields created via Bigin's Developer Console use the <topping_namespace>__<field_label> naming convention and map to equivalent Dynamics 365 custom fields with __c suffix.

Bigin Deals map to Dynamics 365 Opportunities. The Bigin Pipeline and Stage assignment determines the Opportunity's Sales Process and StageName in Dynamics 365. Deal amount, closing date, probability (Bigin's weighted pipeline value), and any custom deal fields migrate to Opportunity fields. We create the destination Sales Process configuration before Deals are imported so that stage values are valid at insert time.

Bigin Pipelines containing named sub-pipelines and deal stages map to Microsoft Dynamics 365 Sales Processes with corresponding Stage values. We pre-create a Sales Process per Bigin Pipeline in the destination Dynamics 365 org, whitelisting the relevant stage names and probabilities. Express plan is limited to 3 pipelines and Premier allows unlimited; we scope this during discovery to size the Sales Process configuration correctly.

Bigin Products (name, unit price, tax, description, and SKU) map to Dynamics 365 Product2 records with Standard Price Book entries created during import. ProductCode maps from Bigin's product SKU field. Line items attached to Deals migrate as Opportunity Product records once the Opportunity and Pricebook2 reference are resolved.

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Dynamics 365 Tasks with Subject, Description, Status, Priority, and ActivityDate preserved. The regardingobjectid reference is resolved at migration time using the parent record's destination ID. Task OwnerId maps by email-matched User lookup.

Bigin Events migrate to Dynamics 365 Events with StartDateTime, EndDateTime, Location, and Subject preserved. Recurring events in Bigin are exported as individual Event records (Bigin's Bulk Read squashes recurring series into a single entity), which we expand into individual recurring instances or flag for manual recreation in Dynamics 365 Calendar. The regardingobjectid reference is resolved at migration time.

Bigin Call logs (subject, duration, outcome, and recording reference) map to Dynamics 365 Tasks with TaskSubtype set to Call. Duration migrates to CallDurationInSeconds. The Regarding reference is resolved to the destination Contact, Company, or Deal ID. Call recordings are flagged as attachment references requiring separate file migration via SharePoint or Dynamics 365 Notes.

Bigin Notes migrate to Dynamics 365 Annotation records (Notes and Attachments). Notes are excluded from Bigin's Bulk Read API, so we use individual record API calls which consume 1 credit per record. For large Note volumes (over 5,000), we pace requests to stay within the daily credit budget and flag any budget risk during scoping. Notes are linked via objectid to the parent Contact, Account, or Opportunity.

Bigin file Attachments migrate to Dynamics 365 Annotation records with isdocument=true. Attachments are excluded from Bigin's Bulk Read API, requiring individual record API calls at higher credit cost. We flag any attachment exceeding Dynamics 365's 10 MB file size limit and recommend SharePoint document management for oversized files post-migration. The parent objectid reference is resolved at migration time.