Migrate from Freshsales to Zoho CRM

Freshsales Leads map to Zoho CRM Leads module with lifecycle stage properties mapped to Zoho Lead Status and custom fields. Lead source tracking, owner assignment, and custom field values preserve through direct field-to-field mapping. Any Freshsales Lead created from a converted Contact carries the original Contact ID in a custom field for traceability. Zoho's Lead Status picklist is reconciled against Freshsales' lifecycle stage values during schema review.

Freshsales Contacts map to Zoho CRM Contacts with all standard and custom fields preserved. The Freshsales contact-to-account association maps to Zoho's Contact-to-Account Lookup relationship, with AccountId resolved during import. Lifecycle stage values from Freshsales migrate to a Zoho custom picklist field fs_lifecycle_stage__c to preserve the original segmentation without conflicting with Zoho's native contact status model.

Freshsales Accounts map directly to Zoho CRM Accounts. Account name, address fields, industry, annual revenue, and phone/website data migrate with standard field mapping. The Freshsales account-to-contact association preserves as Zoho's Lookup(Contact, AccountId) relationship. We resolve Accounts before Contacts in migration order so that the AccountId foreign key is satisfied at Contact insert time.

Freshsales Deals map to Zoho CRM Deals. Pipeline stage names from Freshsales map to Zoho Stage Name values in the corresponding Zoho pipeline. Deal amount, probability, expected close date, owner, and associated Contact and Account lookups all migrate. If Freshsales uses multiple pipelines, we configure Zoho pipelines via Pipeline Management before migration so that the correct pipeline_id and stage_id references are applied per deal.

Freshsales pipeline configurations (stage names, stage order, probabilities) are read from the Freshsales API during scoping and replicated in Zoho CRM Pipeline Management. Each Freshsales pipeline becomes a Zoho pipeline with matching stage labels. Stage probability percentages migrate to Zoho stage Probability fields. If the source uses Freshsales Pro territory management, we replicate territories as Zoho CRM Territories where the destination plan supports them.

Freshsales Products (CPQ catalog items) map to Zoho CRM Products. Product name, SKU, unit price, and description migrate. CPQ license status (1 license on Growth, more on Pro) is flagged because Zoho does not have a direct CPQ licensing model; if the customer used Freshsales CPQ for quote generation, we document the Products and advise that Zoho Quotes require manual setup after migration. Product associations to Deals become Zoho Deals-Products line items.

Freshsales Tasks map to Zoho CRM Tasks with Subject, Status, Priority, Due Date, and Owner preserved. Task type (call, email, follow-up) is stored in a Zoho custom picklist field fs_activity_type__c if the destination does not have a native TaskSubtype equivalent on the task tier in use. Activity history is migrated after Contacts and Accounts to satisfy parent record lookups.

Freshsales Events (meetings, calls) map to Zoho CRM Events with start time, end time, location, and description preserved. Call duration and disposition migrate to custom Event fields if not natively supported in the destination Zoho edition. Meeting attendees are mapped to Zoho Event Invitee records where the destination supports that feature. Event-to-record associations preserve via the WhatId and WhoId fields.

Freshsales custom fields on Leads, Contacts, Accounts, and Deals migrate to Zoho CRM custom fields created during schema setup. We use Zoho's Field Types API to match Freshsales field types (text, number, picklist, date, checkbox, phone, email, URL) to the nearest Zoho equivalent. Advanced custom fields that require Freshsales Pro or Enterprise are flagged with a note that Zoho's corresponding field availability depends on the destination edition tier. Custom field API names are preserved where Zoho naming conventions allow.

Freshsales custom objects (created via the Freshworks developer platform) migrate to Zoho CRM custom modules. We require the source custom object schema (field names, types, relationships) from the customer before migration. Zoho custom modules are created in CRM Settings without requiring the developer platform. Lookup relationships between custom objects and standard objects (Contacts, Accounts, Deals) are replicated in Zoho as lookup fields, and dependency order is enforced so that parent modules migrate before child modules.

File attachments on Contacts, Accounts, and Deals migrate as Zoho CRM attachments linked to the corresponding record. Freshsales file storage limits (2GB per user on Growth, 5GB on Pro, 100GB on Enterprise) mean large attachment volumes are common on higher-tier source accounts. We sample attachment sizes during scoping and alert if projected total storage exceeds the destination Zoho CRM plan's allowance, which starts at 10GB org-wide on Standard and scales with higher tiers.

Freshsales Sales Sequences (Pro-tier only) do not migrate to Zoho CRM because Zoho has no native sequence cadence feature. Blueprint handles step-based process automation but not email or task cadence sequences. We extract the full sequence definitions (step order, delay, email template, action) and deliver them as a written sequence inventory document with recommended Zoho Workflow Rule or Blueprint equivalents for the customer's admin to rebuild. The sequences will not auto-execute post-migration regardless of whether they are listed as active in Freshsales.