Migrate from Freshsales to Salesforce Sales Cloud

Freshsales Leads migrate 1:1 to Salesforce Lead. The Freshsales lead_status and lifecycle_stage properties map to Salesforce Lead Status picklist values. We preserve any Freshsales Freddy AI scoring in a custom field fs_freddy_score__c on the Salesforce Lead for reporting continuity. HubSpot Lead object (Enterprise only) does not apply here; Freshsales is the source.

Freshsales Contacts migrate 1:1 to Salesforce Contact. The Freshsales contact lifecycle stage maps to a custom picklist field fs_lifecycle_stage__c on Contact since Salesforce Contact does not have a native lifecycle stage property. We resolve the AccountId reference at migration time by matching Freshsales Contact's parent Account name to the Salesforce Account created from the same source record.

Freshsales Accounts migrate 1:1 to Salesforce Account. The Account Name and Website (domain) become the primary dedupe key during import. All Contacts linked to this Account in Freshsales are imported after Account creation so that the AccountId lookup is satisfied at the moment of Contact insert. Industry, phone, address, and custom account fields migrate as Salesforce standard and custom fields.

Freshsales Deals map to Salesforce Opportunity. The Freshsales dealstage property maps to Salesforce StageName, the pipeline_id maps to an Opportunity Record Type we configure in Salesforce before migration, and close_date maps to CloseDate. Amount, probability, owner, and notes migrate directly. If Freshsales deal records include a linked Account (company) reference, we resolve that to the Salesforce AccountId on the Opportunity.

Each Freshsales Deal pipeline (supported on Pro and above) becomes a Salesforce Opportunity Record Type with a corresponding Sales Process that whitelists the mapped stage values. Stage probabilities from Freshsales migrate to Salesforce StageProbability values, rounded to Salesforce-allowed integers. If the source is Freshsales Growth, all Deals share one pipeline and map to a single Record Type.

Freshsales Products map to Salesforce Product2 records with Standard Price Book entries created during import. ProductCode migrates from the Freshsales SKU field. Note that Freshsales CPQ functionality is plan-gated (1 license on Growth) and CPQ-specific records (quotes, discount schedules) are flagged for review rather than migrated as standard OpportunityLineItem records.

Freshsales Tasks migrate to Salesforce Task. Status, Priority, ActivityDate, and description migrate directly. Owner resolution maps Freshsales owner email to Salesforce User.Id for assignment. If the task is linked to a Contact or Deal in Freshsales, we resolve the WhatId to the migrated Salesforce Opportunity or Account, and the WhoId to the migrated Contact.

Freshsales Events split by type: call log events migrate to Salesforce Task with TaskSubtype = Call and CallDurationInSeconds preserved; calendar-style events migrate to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Call disposition and recording URLs (where accessible via API) transfer to custom Task or Event fields. Event attendance data maps to EventRelation records.

Freshsales Sales Sequences (Pro and above) are referenced in the migration scope so that affected Contact and Lead records are identifiable, but sequences do not auto-execute in Salesforce. We deliver a written inventory of each Freshsales sequence with its steps, delays, email templates, and cadence logic mapped to a recommended Salesforce Sales Engagement product (High Velocity Sales, Sales Engagement, or a third-party cadence tool). The customer's admin rebuilds cadence logic post-migration.

Freshsales Territory assignments are Pro-tier only. We preserve territory data as a custom multi-select picklist field fs_territory__c on Contact and Opportunity during migration. If the customer licenses Salesforce Territory Management (Revenue Cloud or a separate add-on), we map territories to native Salesforce Territory objects and rebuild the assignment rules post-migration.

Freshsales custom objects created via the Freshworks developer platform require documented app schema to migrate reliably. We import custom object records 1:1 to Salesforce custom objects with __c API names matched to the source schema. All custom fields, picklist values, and lookup relationships are pre-created in the Salesforce destination org before data import. If the source app schema is undocumented, we preserve raw records in a staging format and flag for manual schema mapping.

Both standard and advanced custom fields exist in Freshsales depending on plan tier. We migrate all accessible custom field definitions and values. Advanced custom fields (field-level permissions, Pro or Enterprise-gated) are flagged if the source plan is higher than the destination Salesforce edition. All Freshsales custom fields are created as Salesforce custom fields with type-mapped equivalents (text, number, date, picklist, multi-select) before record import begins.

Freshsales file attachments migrate to Salesforce ContentDocument records uploaded via ContentVersion. File storage limits in Freshsales (2GB/user Growth, 5GB/user Pro, 100GB/user Enterprise) are sampled during scoping to project total attachment volume. If projected storage exceeds the destination Salesforce org's available data storage, we alert the customer before migration and scope a storage reduction strategy (attachment threshold by date, skip attachments above a size limit, or Salesforce storage add-on purchase).