Freshsales to Salesforce migration
We migrate Leads, Contacts, Accounts, Deals, and Activities from Freshsales into Salesforce Sales Cloud with the Leads-Contacts split resolved during scoping, pipeline stage data preserved, and every Freshsales field mapped to a typed Salesforce equivalent before cutover.
FlitStack AI migrates leads, contacts, accounts, opportunities and record type + sales process from Freshsales to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Freshsales to Salesforce?
Moving from Freshsales to Salesforce Sales Cloud is a structural migration driven by scale and ecosystem depth.
Read the full summary
Freshsales treats Leads and Contacts as separate lifecycle-stage objects; Salesforce splits the same concept into a Lead object (unqualified prospects) and a Contact object (qualified records attached to Accounts). We resolve that split during migration design, map Freshsales Deal pipelines to Salesforce Opportunity Record Types and Sales Processes, and preserve the full activity timeline using the Bulk API 2.0 for large engagement histories. Freddy AI scoring, Sales Sequences, and built-in telephony do not have direct Salesforce equivalents at the same tier; we flag these gaps and deliver a written rebuild plan for the customer's admin. Workflows, automations, and bot sessions do not migrate as code.
Lead → Lead
Freshsales Leads migrate 1:1 to Salesforce Lead.
How it maps
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.
Contact → Contact
Freshsales Contacts migrate 1:1 to Salesforce Contact.
How it maps
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.
Account → Account
Freshsales Accounts migrate 1:1 to Salesforce Account.
How it maps
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.
Deal → Opportunity
Freshsales Deals map to Salesforce Opportunity.
How it maps
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.
Deal Pipeline → Record Type + Sales Process
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.
How it maps
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.
Product → Product2
Freshsales Products map to Salesforce Product2 records with Standard Price Book entries created during import.
How it maps
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.
- LeadLead1:1
- ContactContact1:1
- AccountAccount1:1
- DealOpportunity1:1
- Deal PipelineRecord Typetransformed
- ProductProduct21:1
+ 7 more in the mapping below
How Freshsales and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Freshsales | Salesforce |
|---|---|---|
| Lead vs Contact model | Separate Leads and Contacts with lifecycle stages and conversion workflow | Separate Lead and Contact objects with explicit Account association and Convert action |
| Pipeline structure | Multiple pipelines on Pro and above; Kanban and list views | Unlimited Opportunity record types and sales processes from Professional tier ($80/user/mo) |
| Custom objects | App-level setup via Freshworks developer platform, plan-gated | Available from Professional tier ($80/user/mo) without app setup overhead |
| Pricing model | $9/user/mo Growth, $39/user/mo Pro; per-minute telephony and bot session add-ons | $25/user/mo Starter, $80/user/mo Professional; bundled features by edition, no per-minute telephony |
| AI features | Freddy AI scoring and deal insights on Pro $39/user/mo tier only | Einstein AI available from Professional tier with Sales Cloud Einstein add-on |
| Integration ecosystem | Freshworks Marketplace with under 1,000 apps | AppExchange with over 7,000 apps including ERP, CPQ, and revenue intelligence depth |
| Telephony | Built-in calling with per-minute charges, no monthly cap | No native telephony; partner solutions (Five9, AWS Connect) or third-party VoIP via AppExchange |
What to watch for in a Freshsales to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Freddy AI scores do not migrate to Salesforce Einstein
Freddy AI contact scoring and deal predictions are Freshsales Pro-tier features that have no direct Salesforce equivalent.
How we handle it
Einstein AI in Salesforce Sales Cloud uses a different scoring model, training data, and activation triggers. We preserve Freddy AI raw scores in a custom field fs_freddy_score__c on the migrated Lead and Contact for manual re-scoring in Einstein, but the scores themselves do not transfer as live Einstein data. We flag any Freshsales custom fields prefixed with ai_ or freddy_ during scoping so the customer can plan for Einstein re-training on the Salesforce side.
Freshsales Sales Sequences stop executing after migration
Freshsales Sales Sequences (Pro-tier) are a sales engagement cadence feature.
How we handle it
They do not auto-execute in Salesforce because Salesforce Sales Cloud does not have a native sequence runner at the same tier. We migrate the sequence definitions (step count, step types, delays, email templates) as a written inventory document, but the sequences themselves are inactive in Salesforce until the customer implements a Sales Engagement product (Salesforce High Velocity Sales, Sales Engagement, or a third-party cadence tool such as Outreach, Salesloft, or Apollo). We identify every Contact and Lead that was in an active sequence at migration time so the customer's sales team can resume cadence manually or via the new cadence tool.
Built-in telephony call logs and recordings require API access and plan tier
Freshsales built-in calling is per-minute billed with no monthly cap.
How we handle it
Call records and recordings migrate as Tasks (TaskSubtype=Call) and ContentDocument attachments respectively, but call recordings require API access and may be limited by the source Freshsales plan tier (Enterprise for audit logs). We sample call record volumes during scoping, estimate per-minute billing exposure for the migration window, and flag if call recording URLs are inaccessible via the Freshsales API before committing to a recording migration scope. Salesforce has no native per-minute telephony; the customer selects a partner VoIP solution (Five9, AWS Connect, Zoom Phone via AppExchange) post-migration.
Freshsales file storage limits differ from Salesforce data storage allocation
Freshsales storage scales with plan tier (2GB/user Growth, 5GB/user Pro, 100GB/user Enterprise).
How we handle it
Salesforce Sales Cloud data storage is allocated org-wide (5GB for Essentials, 10GB for Professional and above) and is shared across all standard and custom objects. A migration with large attachment volumes from a Freshsales Enterprise account (100GB/user) can silently exceed Salesforce org storage limits. We sample attachment sizes during scoping, project total migration volume, and alert the customer if the destination Salesforce edition's storage allocation is insufficient. Options include purchasing additional Salesforce storage or trimming attachment scope by date threshold.
Freshsales Classic to Suite migration has a post-migration email cliff
If the source Freshsales account is a Classic product being migrated to Salesforce (rather than Freshsales Suite), there is no direct email disable cliff because email lives in Salesforce post-migration.
How we handle it
However, if the customer is simultaneously migrating from Freshsales Classic to Suite or another platform, Freshworks automatically disables outgoing emails post-migration and workflows stop executing. We coordinate the migration window with Freshworks support timelines to minimize disruption regardless of whether the source is Classic or Suite.
How the migration runs
Discovery and Freshsales plan audit
We audit the source Freshsales account across plan tier (Free/Growth/Pro/Enterprise), active pipeline count, custom object schemas, Sales Sequence definitions, Freddy AI field usage, telephony call record volumes, attachment sizes, and territory assignments.
What this step covers
We pair this with a Salesforce edition recommendation: Professional ($80/user) covers most Freshsales Pro migrations with custom objects and Flow; Enterprise ($165/user) is required for territory management, advanced forecasting, or large engagement histories. The discovery output is a written migration scope document with record counts per object and a destination Salesforce edition recommendation.
Schema design and Record Type configuration
We design the destination Salesforce schema in a Sandbox org before production migration.
What this step covers
This includes provisioning custom fields (fs_lifecycle_stage__c, fs_freddy_score__c, fs_territory__c and others identified during discovery), Record Types (one per Freshsales pipeline), Sales Processes (stage whitelist per Record Type), and Page Layouts scoped per Record Type. Custom object schemas are pre-created in Salesforce with __c API names matched to the source Freshworks developer platform schema. Validation rules and required-field constraints are identified so they can be temporarily bypassed during the data load phase.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-equivalent data volume.
What this step covers
The customer's RevOps lead reconciles record counts (Leads, Contacts, Accounts, Opportunities, Tasks, Events), spot-checks 25-50 records against the Freshsales source, and validates that Account-Contact relationships, Opportunity-Account links, and pipeline stage assignments are correct. Any mapping corrections, custom field type adjustments, or Record Type misconfigurations are resolved in Sandbox before production migration begins.
Owner reconciliation and User provisioning
We extract every distinct Freshsales Owner referenced on Leads, Contacts, Accounts, Deals, Tasks, and Events and match by email against the Salesforce destination org's User table.
What this step covers
Any Freshsales Owner without a matching Salesforce User goes to a reconciliation queue. The customer's Salesforce admin provisions missing Users and assigns the correct profiles and roles before record import. OwnerId references must be valid on all standard object inserts; this step gates all downstream imports.
Production migration in dependency order
We run production migration in record-dependency order: Users (validated), Accounts (from Freshsales Companies), Contacts (with AccountId resolved), Leads (with lifecycle stage preserved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries, Tasks and Events (via Bulk API 2.0 for histories over 100,000 records), Custom Objects (last, with pre-created schema), and Attachments (via ContentVersion with storage budget verified).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Freddy AI scores and territory assignments are imported as custom field values after the core record import completes.
Cutover, validation, and Sequence rebuild handoff
We freeze Freshsales write access during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver the Sales Sequence inventory document and the Freddy AI field reference list to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Freshsales workflows or sequences as Salesforce Flow inside the migration scope; that is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Freshsales to Salesforce →Why teams move from Freshsales to Salesforce
- Teams outgrow Freshsales reporting depth and pipeline customization limits. G2 and Capterra reviews cite limited custom report builders and inability to slice pipeline data across multiple dimensions as the reason RevOps leaders move. Salesforce's reporting engine supports cross-object joined reports, custom fiscal period settings, and territory-based forecasting that Freshsales Growth and Pro cannot match without exporting to a BI tool.
- The AppExchange ecosystem (7,000+ listings) versus Freshworks Marketplace (under 1,000) is a decisive factor for companies with ERP, CPQ, contract lifecycle management, or revenue intelligence needs. Reviewers on Reddit and comparison sites cite difficulty finding Freshsales integrations for niche tools as a driver to Salesforce where these apps are AppExchange-native or certified.
- Salesforce's custom objects are available from Professional tier ($80/user/mo) without the app-level developer platform setup that Freshsales requires. Companies whose data model needs custom record types (Properties, Projects, Subscriptions, Locations) move to Salesforce because the tier gate is lower and the schema design is declarative rather than code-driven.
- Freddy AI deal predictions and contact scoring are locked behind Freshsales Pro at $39/user/mo, and the chatbot session credits are a one-time 500-session allocation with no disclosed top-up pricing. Salesforce Einstein AI is available as an add-on from Professional tier with a transparent per-user license model, and Einstein Activity Capture handles contact and calendar sync without per-minute billing exposure.
- Customer support quality at scale drives the switch. ExpertMarket research scores Freshsales 4.2/5 versus Salesforce's 5/5 for customer support, with Salesforce offering 24/7 live phone support, a community forum, knowledge base, and email chat. Enterprise teams citing support responsiveness as a SLA requirement consistently move toward Salesforce.
Questions, answered
Freshsales to Salesforce migration questions
How long does a Freshsales to Salesforce migration take?
Most Freshsales migrations land between four and six weeks for accounts under 25,000 Contacts and 5,000 Deals with no custom objects or territory-based routing. Migrations with custom objects, multiple Freshsales Deal pipelines, large engagement histories (over 500,000 activity records), or complex territory assignments move to ten to sixteen weeks because of Salesforce schema design, Bulk API time, and Record Type configuration. The Freshsales plan tier matters: Pro and Enterprise accounts with Sales Sequences and Freddy AI data require additional rebuild documentation that adds to the scoping phase.
Do Freshsales Workflows, Sequences, and Freddy AI features migrate to Salesforce?
No. Freshsales Workflows and Salesforce Flow are different automation models with different triggers, actions, and limits. Sales Sequences are a sales engagement cadence feature that has no direct Salesforce Sales Cloud native equivalent. Freddy AI scoring and deal predictions are Freshsales-specific and do not transfer to Salesforce Einstein. We do not migrate these as code or live data. We deliver a written inventory of every active Freshsales sequence with step logic and a recommended Salesforce Sales Engagement product (High Velocity Sales, Sales Engagement, or a third-party cadence tool). Freddy AI scores are preserved as a custom field (fs_freddy_score__c) for manual Einstein re-training. Workflows are documented with a recommended Salesforce Flow equivalent.
Can we keep Freshworks products (Freshdesk, Freshchat) while moving sales to Salesforce?
Yes. A hybrid stack is common. Freshdesk continues to handle customer support cases, Freshchat continues to handle customer chat, and Salesforce Sales Cloud handles the sales process from Lead creation through Opportunity close. We configure the Freshworks-to-Salesforce integration during migration (if an integration exists via AppExchange or Freshworks Marketplace) so that Contact records are shared and case data is linked. The customer continues paying for Freshworks support and chat tools at the existing tier while moving sales seat licensing to Salesforce.
Do we lose historical deal stage data and pipeline activity during migration?
No. We migrate Freshsales Deal stage history as Salesforce Opportunity stage history via the OpportunityHistory object. Pipeline assignment from Freshsales maps to the Salesforce Record Type and Sales Process we configure before migration, preserving which pipeline each Deal belonged to. Activity timestamps (created_date, last_modified_date) migrate to Salesforce SystemModstamp and LastModifiedDate to preserve record age and audit trail. Call logs migrate as Tasks with TaskSubtype=Call; calendar events migrate as Salesforce Events with timing and location preserved.
How do we handle the built-in telephony call records and per-minute billing after migration?
Freshsales built-in calling is per-minute billed with no monthly cap. We migrate call records as Salesforce Tasks (TaskSubtype=Call) with duration and disposition preserved. Call recordings migrate as ContentDocument attachments where accessible via the Freshsales API. Salesforce Sales Cloud has no native per-minute telephony; the customer selects a VoIP partner solution (Five9, AWS Connect, Zoom Phone) via AppExchange post-migration. Per-minute billing exposure ends when the team decommissions Freshsales telephony.
What happens to Freshsales bot session data and chat transcripts?
Freshsales Freddy AI chatbot sessions are a one-time 500-session allocation on the plan, not a monthly refresh. There is no disclosed pricing for additional session packs. Chat transcripts and bot session logs are not standard CRM objects and are not migratable via the Freshsales REST API as structured records. We document the bot configuration (welcome message, decision trees, integration points) as a written spec so the customer's admin can rebuild the chatbot logic in a Salesforce-compatible chatbot platform (Salesforce Service Cloud chatbot, Drift, or Intercom) post-migration.
Can FlitStack AI also migrate Freshsales custom objects and advanced custom fields from Enterprise?
Yes. We migrate Freshsales custom object records to Salesforce custom objects when the source app schema is documented. All custom fields (standard and advanced) migrate as Salesforce custom fields with type-mapped equivalents. Advanced custom fields that require Freshsales Pro or Enterprise are flagged if the destination Salesforce edition is lower. We pre-create the Salesforce destination schema (custom objects, fields, picklists, lookups) in a Sandbox before production migration to ensure the schema is validated before any data moves. If the source app schema is undocumented, we preserve raw records in a staging format and flag for manual schema mapping before final import.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → monday CRM to SalesforceMapping · history · rollbackCustomer.io to SalesforceMapping · history · rollbackHoneyBook to SalesforceMapping · history · rollbackActiveCampaign to SalesforceMapping · history · rollbackBlackbaud to SalesforceMapping · history · rollbackTwenty CRM to SalesforceMapping · history · rollback Freshsales to HubSpotMapping · history · rollbackFreshsales to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Freshsales / Freshmarketer Migration FAQs — Freshworks Support
- What are custom field limits? — Freshsales Suite Support
- Freshsales bulk upsert — Freshworks Support
Get a quote
Moving from Freshsales to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote