CRM migration
Field-level mapping, validation, and rollback between Bigin by Zoho CRM and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Bigin by Zoho CRM
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between Bigin by Zoho CRM and Freshsales.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Bigin by Zoho CRM organizes data around Pipelines and sub-pipelines containing Deals, while Freshsales follows the Accounts-Contacts-Opportunities model with Sales Cycles and a separate Leads module. These architectural differences require a schema redesign before migration begins. We map each Bigin pipeline and its deal stages to a Freshsales Sales Cycle with matching stage names, then preserve Deal owner assignments and stage history in the corresponding Opportunity record. Bigin's credit-based API requires pacing during export, and its Bulk Read API excludes Notes and Attachments entirely, so we fall back to individual record API calls for those object types. Workflows, automation rules, and sequences do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Freshsales. Custom fields created via Bigin's Developer Console use the <namespace>__<field_label> convention and require explicit mapping to Freshsales custom field API names during scoping.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Bigin by Zoho CRM object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Bigin by Zoho CRM
Contact
Freshsales
Contact
1:1Bigin Contact records map directly to Freshsales Contact records. The mapping preserves First Name, Last Name, Email, Phone, Address, and lifecycle fields. Bigin's Owner assignment maps to Freshsales Owner by email match. We validate that every Contact's email is unique against the Freshsales Contact dedupe key before insert to prevent duplicates from a previously uncleaned Bigin database.
Bigin by Zoho CRM
Company
Freshsales
Account
1:1Bigin Company records (API name: Accounts) map to Freshsales Account records. The Company domain name becomes the Account Website field and serves as the dedupe key during import. We preserve Company-Contact linkages by importing Accounts before Contacts and resolving the AccountId lookup at Contact insert time.
Bigin by Zoho CRM
Deal
Freshsales
Opportunity
1:1Bigin Deals map to Freshsales Opportunities. The Bigin deal stage maps to a Freshsales Sales Cycle stage, and the pipeline assignment maps to a Freshsales Sales Cycle configuration that we create during schema design. Closed-Lost and Closed-Won reasons from Bigin custom fields migrate as text fields on the Opportunity record.
Bigin by Zoho CRM
Pipeline
Freshsales
Sales Cycle
lossyEach Bigin Pipeline with its sub-pipeline and stage structure maps to a Freshsales Sales Cycle with corresponding stage names and probabilities. Bigin's Express plan allows 3 pipelines; Premier allows unlimited. We replicate this structure in Freshsales by creating one Sales Cycle per Bigin Pipeline. Stage probability percentages migrate from Bigin to Freshsales stage configuration. If Bigin uses a single pipeline, we create a single Sales Cycle and map the stages directly.
Bigin by Zoho CRM
Product
Freshsales
Product
1:1Bigin Product catalog records map to Freshsales Product records with Standard Price Book entries created during import. Product name, unit price, tax settings, and description migrate directly. Custom product fields created via Bigin's Developer Console follow the namespace convention and map to Freshsales custom fields pre-created during schema design.
Bigin by Zoho CRM
Task
Freshsales
Task
1:1Bigin Task records linked to Contacts, Companies, or Deals migrate to Freshsales Task records with Owner, due date, status, and priority preserved. Task-to-parent linkages migrate by resolving the parent Contact, Account, or Opportunity lookup at migration time. Due date ordering is preserved in Freshsales by setting the Activity Date to the original Bigin timestamp.
Bigin by Zoho CRM
Event
Freshsales
Event
1:1Bigin Event records migrate to Freshsales Event records with Start Time, End Time, Location, and recurrence data preserved. Note that Bigin's Bulk Read API squashes recurring events into a single entity, so we flag this during scoping and migrate recurring events as a single Event record with recurrence metadata. Individual event instances beyond the squash are not recoverable from the Bulk Read export.
Bigin by Zoho CRM
Call
Freshsales
Call Log
1:1Bigin Call records associated with Contacts, Companies, or Deals migrate to Freshsales Call Log records. Call duration, subject, outcome, and timestamp migrate directly. Call-to-parent linkages resolve at migration time against the imported Contact, Account, or Opportunity records. We flag any Call records whose parent contact has not yet been imported and resolve them in a second pass.
Bigin by Zoho CRM
Note
Freshsales
Note
1:1Bigin Notes migrate to Freshsales Note records linked via the parent record's lookup field. Notes are excluded from Bigin's Bulk Read API and must be retrieved via individual record API calls, which consume 1 credit each versus the 3 credits per Get Records call. We scope the Notes volume before migration and budget API credits accordingly. Parent-record lookups are resolved by matching the Note's parent record ID against the imported Contact, Company, or Deal.
Bigin by Zoho CRM
Custom Field
Freshsales
Custom Field
1:1Bigin 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 scoping, pre-create matching Freshsales custom fields of equivalent type (text, number, date, picklist, multi-select), and validate field types before migration so that data is not rejected by Freshsales validation rules. Any picklist values in Bigin that do not exist in Freshsales require picklist value creation before import.
| Bigin by Zoho CRM | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Sales Cyclelossy | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Event | Event1:1 | Fully supported | |
| Call | Call Log1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Bigin by Zoho CRM gotchas
Credit-based API limits vary by plan and can throttle migrations
Bulk Read API excludes Notes, Attachments, Emails, and cross-module records
Import field mapping is complicated and unintuitive for users
Undo import window is limited to 30 days
Free plan is single-user with a 500-record hard cap
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the source Bigin account across plan tier, record counts per module (Contacts, Companies, Deals, Products, Tasks, Events, Calls, Notes, Attachments), custom field inventory using the namespace convention, pipeline and sub-pipeline structure, and active workflow count. We estimate API credit consumption based on the record counts and the Notes-and-Attachments volume requiring individual calls, and we assess whether the Bigin account is on the Free plan (1 user, 500 records, 5,000 credits per day) which requires a different pacing strategy than paid plans.
Schema design and mapping
We design the destination Freshsales schema: creating Sales Cycles to match Bigin Pipelines with stage names and probabilities, pre-creating Freshsales custom fields for every Bigin namespace field with type-matched field creation, and finalizing the Contact-to-Contact, Company-to-Account, Deal-to-Opportunity, and activity-to-activity mapping tables. Bigin's sub-pipeline structure is resolved during this step into either a flattened Sales Cycle stage model or a custom field carryover strategy agreed upon with the customer.
Sandbox migration and validation
We run a full migration into a Freshsales sandbox environment using production-like data volumes. The customer's admin validates record counts across all modules, spot-checks 20-30 records for field-level accuracy, and confirms that the Sales Cycle configuration reproduces the Bigin pipeline visibility the team relies on. Any mapping corrections are applied to the schema before production migration begins. This step is included in all standard migration scopes.
Owner reconciliation
We extract every distinct Owner referenced on Contact, Company, Deal, Task, Event, and Call records and match by email against the Freshsales destination User table. Any Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references must be resolved before standard object import begins because OwnerId is a required field on most Freshsales objects.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Bigin Companies) first with domain-based dedupe, then Contacts with AccountId resolved, then Products and Pricebook entries, then Opportunities with Sales Cycle, stage, owner, and custom fields resolved. Tasks, Events, Calls, and Notes follow using individual API calls for Notes to bypass the Bulk Read exclusion. Each phase emits a row-count reconciliation report before the next phase begins. We pace API calls against Bigin's credit budget and handle 429 rate-limit responses with exponential backoff.
Cutover, delta migration, and handoff
We freeze writes in Bigin during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver a written inventory of every active Bigin workflow and automation rule with its trigger, conditions, and actions documented for the customer's admin to rebuild in Freshsales. We support a three-day hypercare window to resolve reconciliation issues raised during the first business days in Freshsales.
Platform deep dives
Bigin by Zoho CRM
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Bigin by Zoho CRM and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Bigin by Zoho CRM: Credit-based system: 5,000 credits/24h on Free; 50,000 + (user licenses × 250) capped at 100,000/24h on Express, Premier, and Zoho One. Concurrency cap of 5 simultaneous API calls per user on Free, 10 on paid editions, with a sub-cap of 10 across resource-intensive operations..
Data volume sensitivity
Bigin by Zoho CRM exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Bigin by Zoho CRM to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Bigin by Zoho CRM to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Bigin by Zoho CRM
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.