Salesforce Service Cloud to Freshdesk migration
We migrate Cases, Contacts, Accounts, Entitlements, and conversation history from Salesforce Service Cloud into Freshdesk with Salesforce Bulk API extraction under daily request limits, SLA-to-service-level-agreement translation, and a full object graph preserved across the cutover window.
FlitStack AI migrates tickets, contacts, companies, conversations and ticket field updates from Salesforce Service Cloud to Freshdesk, 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: 2-4 weeks.

What moves from Salesforce Service Cloud to Freshdesk?
Moving from Salesforce Service Cloud to Freshdesk is a schema simplification migration.
Read the full summary
Service Cloud models support cases as a central node threading to Contact, Account, Entitlement, Case Comment, Case History, and Milestone records; Freshdesk consolidates these into Tickets, Contacts, Companies, and Conversations. We extract via Salesforce Bulk API under the org's daily request limit, resolve parent-child relationships before Freshdesk ingestion, and flag picklist value translation gaps that silently corrupt records during load. Entitlements and SLA milestone data map to Freshdesk Service Level Agreements with breach window timestamps preserved. Workflow rules, Flows, and Salesforce Omnichannel routing configurations do not migrate; we deliver a written inventory of these for the customer's Freshdesk admin to rebuild as scenarios. We do not provide post-migration admin support, training, or Freshdesk workflow rebuild as standard scope.
Case → Ticket
Salesforce Case maps to Freshdesk Ticket.
How it maps
The Case Record Type becomes Freshdesk Ticket Type for segmentation. Case Status (Open, Pending, Closed) maps to Freshdesk Status (Open, Pending, Resolved, Closed) with a translation table for any custom status values. Case Priority maps to Freshdesk Priority. The Salesforce Case Number becomes Freshdesk Display ID preserved as a custom field for cross-reference during reconciliation. The original Case created date and closed date transfer to Freshdesk created_at and resolved_at timestamps.
Contact → Contact
Salesforce Contact maps to Freshdesk Contact.
How it maps
The Contact email is the dedupe key. FirstName, LastName, Email, Phone, and Title transfer directly. Multi-address records (Salesforce supports mailing and other addresses) transfer the primary mailing address; secondary addresses become custom Freshdesk contact fields. Any Salesforce Contact custom fields require Freshdesk contact field creation before migration.
Account → Company
Salesforce Account maps to Freshdesk Company.
How it maps
The Account Name becomes Company name; Account Number becomes a custom field for reconciliation. Salesforce Account hierarchy (parent Account) does not have a direct Freshdesk equivalent. We store the parent Account name as a custom Company field and recommend rebuilding hierarchy in Freshdesk Groups if needed. Industry and Type picklist values require translation against Freshdesk's custom field options.
Case Comment → Conversation
Salesforce Case Comments (both public and private) map to Freshdesk Conversation records attached to the parent Ticket.
How it maps
The IsPublished flag determines whether the comment is a public note or an internal note in Freshdesk. Rich-text formatting in Salesforce Case Comments is sanitized to plain text with HTML stripped unless Freshdesk's HTML renderer is enabled. Private Case Comments migrate as Freshdesk internal notes with a flag preserved for audit.
Case History → Ticket Field Updates
Salesforce Case History tracks field-level changes (audit trail).
How it maps
Freshdesk does not have a native audit trail equivalent for field changes. We offer selective migration of Case History as a custom object or as activity log entries on the Freshdesk Ticket, or we flag this gap and recommend Freshdesk's built-in ticket activity log as the replacement. The customer chooses the scope during scoping.
EmailMessage → Conversation
Salesforce EmailMessage records attached to Cases migrate to Freshdesk Ticket Conversations.
How it maps
The email subject, body (HTML or plain text), from address, to address, and cc address transfer. Email attachments are extracted separately and linked via Freshdesk attachment API with the conversation reference preserved. Threading is maintained by ordering conversations by the Salesforce EmailMessage CreatedDate.
- CaseTicket1:1
- ContactContact1:1
- AccountCompany1:1
- Case CommentConversation1:1
- Case HistoryTicket Field Updatestransformed
- EmailMessageConversation1:1
+ 6 more in the mapping below
How Salesforce Service Cloud and Freshdesk 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 | Salesforce Service Cloud | Freshdesk |
|---|---|---|
| Ticket object model | Case object as central node with related Contacts, Accounts, Entitlements, Case Comments, Case History, and Milestones as separate objects | Ticket object as primary record with nested Conversations, Contact, and Company linked directly without separate related objects |
| SLA tracking | Entitlements and Case Milestones with RemainingTime, completion timestamps, and breach-window enforcement | Service Level Agreements with first-response and resolution targets configurable per ticket type |
| Picklist structure | Dependent picklists (Country gates State, Entitlement gates Milestone Type) enforced at record level | Flat custom fields with no dependency enforcement; values map from Salesforce picklist translation table |
| Agent and user model | User object with Profiles, Roles, and Case Team Members linked to Cases | Agent object with Groups and Roles scoped per ticket type, no direct User-to-User team concept |
| Case assignment | Case Assignment Rules plus Flow field updates with complex AND/OR conditions | Freshdesk Ticket Routing with automated assignments to Groups and Agents based on conditions |
| Pricing model | Per-seat at $75-$500/user/month billed annually plus add-ons | Per-agent from free to $79/agent/month; unlimited contacts across all paid plans |
| Custom fields | Custom fields on Case, Contact, Account, and custom objects with field-level security | Custom ticket fields scoped to ticket fields, contact fields, or company fields with no field-level security granularity |
What to watch for in a Salesforce Service Cloud to Freshdesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Conversation thread ordering requires parent-record resolution
Salesforce Case Comments and EmailMessages thread under a parent Case ID.
How we handle it
When migrating to Freshdesk, each Case Comment becomes a Conversation and each EmailMessage becomes a separate Conversation entry. The ordering of conversations is determined by the Salesforce CreatedDate timestamp. We batch conversation inserts per ticket and sort by CreatedDate to preserve the original thread order. If Salesforce records were created out of chronological order due to API latency or backdated edits, the thread may not read as sequential without manual reordering.
Attachment extraction from EmailMessage and Case Comment requires separate API calls
Salesforce EmailMessage and Case Comment attachments live as ContentDocumentLink records pointing to ContentVersion.
How we handle it
They do not transfer in the same API response as the parent record. We run a parallel extraction pass to collect all ContentVersion bodies referenced by migrating Cases, map them by LinkedEntityId, and insert them as Freshdesk ticket attachments linked by ticket_id. Attachments exceeding Freshdesk's 25MB per-file limit are flagged for manual handoff or chunking.
Picklist value translation gaps silently skip or corrupt records
Salesforce Case Origin (Email, Phone, Web, Chat) and Case Status picklist values do not always match Freshdesk's equivalent field options exactly.
How we handle it
A naive import drops records with unrecognized picklist values or lands them with null values. We build a Salesforce-to-Freshdesk picklist translation table during field mapping and run a pre-flight validation pass against the destination Freshdesk instance's field options before any records load.
Active Salesforce Flows and triggers fire on record insertion
Salesforce Flow record-triggered flows and Apex triggers respond to Case insertion events.
How we handle it
A bulk migration can generate unwanted email notifications to customers, create spurious follow-up tasks, or update related records (Contact last activity date, Account case counts) in ways that distort the post-migration state. We recommend deactivating Salesforce Flows before migration and re-activating them after validation. We include a Flow audit checklist as part of pre-migration planning.
SLA milestone breach timestamps require entitlement-to-SLA translation
Salesforce Entitlements enforce SLA breach windows by calculating remaining time from Case creation.
How we handle it
Freshdesk SLAs define target response and resolution times but do not natively preserve the Salesforce breach timestamp if the Case was already approaching breach. We carry forward the RemainingTime and breach timestamp as custom fields on the Freshdesk Ticket so that SLAs are not silently reset on migration. Customers using SLA enforcement dashboards in Salesforce should review Freshdesk SLA reporting equivalents before cutover.
How the migration runs
Discovery and Salesforce org audit
We audit the source Salesforce org across edition tier, record type count, custom fields on Case/Contact/Account/Entitlement, active Flows and triggers, picklist dependency chains, and engagement volume.
What this step covers
We extract API daily request consumption for the prior 30 days to determine migration window headroom. The discovery output is a written migration scope document listing record counts by object, custom field inventory requiring Freshdesk field creation, picklist translation requirements, and a Salesforce edition recommendation if the destination tier changes.
Freshdesk workspace configuration
We configure the Freshdesk destination workspace before any data loads.
What this step covers
This includes creating custom ticket fields matching Salesforce custom field types and labels, configuring Ticket Types and Status options against the Salesforce Record Type and Status translation table, setting up Service Level Agreements matching Salesforce Entitlement terms, creating Freshdesk Groups mirroring Salesforce Case Team structures, provisioning Freshdesk Agents mapped from Salesforce Users by email, and enabling the Knowledge Base module if article migration is in scope.
Sandbox migration and reconciliation
We run a full migration into the Freshdesk sandbox using production-like data volume.
What this step covers
The customer's support operations lead reconciles record counts (Tickets in, Contacts in, Companies in, Conversations in), spot-checks 25-50 random tickets against the Salesforce source, and validates SLA milestone preservation. Any mapping corrections happen in the sandbox, not in production. The customer signs off the sandbox reconciliation before production migration begins.
Salesforce Bulk API extraction under rate limits
We extract Salesforce records using Bulk API 2.0 with chunking and SOQL query splits by date range or record type to stay within the org's daily request limit.
What this step covers
We schedule extraction passes during off-peak hours (after 9PM source org local time) to maximize API headroom. Case Comments, EmailMessages, and ContentVersion attachments are extracted in parallel passes with parent Case ID as the linking key. We generate a pre-flight picklist validation report before extracting picklist-controlled records.
Production migration in dependency order
We run production migration in record-dependency order: Freshdesk Agents (validated against Salesforce Users by email), Companies (from Salesforce Accounts), Contacts (with Company_id resolved), Tickets (with Contact_id, Company_id, and SLA reference resolved), Conversations (Case Comments and EmailMessages sorted by CreatedDate), Entitlement-to-SLA associations, SLA milestone timestamps, and Knowledge Base articles last.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We run a delta migration pass for records modified during the production migration window.
Cutover, validation, and automation inventory handoff
We freeze Salesforce Case writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshdesk as the system of record.
What this step covers
We deliver a written inventory of every active Salesforce Flow, Process Builder flow, and Case Assignment Rule requiring rebuild as Freshdesk Ticket Routing rules or Automations. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's support team. We do not rebuild Salesforce Flows as Freshdesk automations 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 field count, and the number of Salesforce record types requiring Freshdesk ticket type configuration. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Salesforce Service Cloud to Freshdesk →Why teams move from Salesforce Service Cloud to Freshdesk
- Annual Salesforce licensing costs 3-4x more than Freshdesk at equivalent agent counts. Salesforce Service Cloud Enterprise at $175/user/month reaches $132,000/year for 10 agents versus Freshdesk Growth at $49/agent/month totaling approximately $30,948/year. Reviewers on G2 and Capterra consistently cite the total cost of ownership including add-ons, storage overages, and annual uplifts as the primary driver for switching to Freshdesk for teams that do not require Salesforce CRM integration.
- Salesforce Service Cloud complexity requires dedicated admin resources and external consultants for basic configuration changes. Freshdesk's interface is rated significantly higher for ease of use by mid-market support teams transitioning from Salesforce, with 7-Eleven, Hinge Health, and Digitrips citing rapid deployment and agent adoption as direct outcomes of Freshdesk's simpler configuration model versus the Salesforce admin dependency.
- Picklist dependencies, workflow triggers, and entitlement-milestone relationships create migration surface area that grows with Salesforce customization depth. Mid-market teams with minimal custom objects, no Apex triggers, and standard Case Assignment Rules can migrate in two to four weeks; teams with complex Flow automation, dependent picklists, and entitlement-managed SLAs face six to nine weeks of schema reconciliation before data moves. Freshdesk's flatter data model reduces this surface area for teams leaving Salesforce.
- Freshdesk Knowledge Base is available on all paid plans including Growth, while Salesforce Service Cloud restricts Knowledge to Enterprise and above at additional cost. Teams that rely on self-service knowledge articles for Tier-1 deflection find Freshdesk's included Knowledge Base reduces their monthly bill compared to Salesforce's entitlement-based approach.
- API rate limits on Salesforce lower-tier editions throttle bulk exports, forcing teams to batch operations over multiple off-peak windows. Freshdesk API imposes 700 requests per minute per app but does not carry the 24-hour rolling request count that constrains Salesforce Enterprise at 100,000 requests/day. Teams with active integrations (Outlook sync, custom REST endpoints) frequently exhaust Salesforce API headroom mid-extraction, making Freshdesk a more predictable integration target.
Questions, answered
Salesforce Service Cloud to Freshdesk migration questions
How long does a Salesforce Service Cloud to Freshdesk migration take?
Migrations land between two and four weeks for organizations under 50,000 Cases, 20,000 Contacts, and 5,000 Accounts with no custom objects, minimal custom fields, and standard Salesforce Flows that can be deactivated before migration. Migrations with Entitlement-to-SLA translation, large case history volumes, multi-object custom fields, or complex Flow audit requirements move to five to nine weeks because of Bulk API extraction time, picklist translation table development, and SLA configuration scope.
Do Salesforce Flows, Case Assignment Rules, and Omnichannel routing migrate to Freshdesk?
No. Salesforce Flows and Case Assignment Rules are automation models with no direct Freshdesk equivalent. We do not migrate them as code. We deliver a written inventory of every active Salesforce Flow and Case Assignment Rule with its trigger, conditions, and actions, plus a recommended Freshdesk Ticket Routing or Automation equivalent. The customer's Freshdesk admin rebuilds them post-migration. Omnichannel routing configurations similarly do not migrate; Freshdesk uses its own routing engine configured within the platform.
Can we preserve Salesforce SLA milestone data in Freshdesk?
Yes, with translation. Salesforce Entitlements and Case Milestones define SLA terms with response time, resolution time, and breach timestamps. We map these to Freshdesk Service Level Agreements with First Response Time and Resolution Time targets carried forward. The Salesforce milestone remaining time and breach timestamp transfer as custom ticket fields so that Freshdesk's SLA clock does not restart from zero on migration. Customers relying on SLA breach reporting in Salesforce should review Freshdesk's SLA analytics before cutover.
Do we lose Case Comments, Email Messages, and attachment history?
No. We migrate the full conversation history including Salesforce Case Comments (public and private) and EmailMessages as Freshdesk Conversations ordered by timestamp. Email attachments and Case Comment attachments are extracted separately via ContentVersion API and linked to the Freshdesk ticket conversation. Attachments exceeding Freshdesk's 25MB per-file limit are flagged for manual handoff. Private Case Comments migrate as Freshdesk internal notes with the visibility flag preserved.
What happens to Salesforce Entitlements and Entitlement Processes during migration?
Salesforce Entitlements define SLA terms per Contact or Account and are referenced by Case Milestones. We map each Entitlement to a Freshdesk Service Level Agreement with the same response and resolution time targets. Multiple Salesforce Entitlement Processes map to multiple Freshdesk SLAs by process name. If the Salesforce org uses different Entitlements for different customer tiers (Gold, Silver, Bronze), we configure equivalent Freshdesk SLA tiers and map by Entitlement name during Case migration.
How do we handle Salesforce picklist values that do not exist in Freshdesk?
We build a Salesforce-to-Freshdesk picklist translation table during field mapping before any records load. Every Salesforce picklist value gets mapped to a Freshdesk field option or flagged as a new option to add. Records with unmapped picklist values are held in a separate error queue and reported to the customer's admin for decision: add the missing value to Freshdesk, merge it with an existing value, or exclude it from migration. We run a pre-flight validation pass against the live Freshdesk instance to confirm all target field options exist before production load begins.
Does FlitStack AI also migrate from Freshdesk back to Salesforce Service Cloud?
Yes. We handle bidirectional helpdesk migrations including the reverse path from Freshdesk to Salesforce Service Cloud. The object mapping reverses (Freshdesk Ticket to Salesforce Case, Company to Account, Contact to Contact), but the schema translation complexity remains similar. Freshdesk custom ticket fields map to Salesforce Case custom fields, Freshdesk automations require inventory for Salesforce Flow rebuild, and Freshdesk SLA configurations translate to Salesforce Entitlements. The same rate-limit handling, attachment extraction passes, and picklist translation requirements apply.
Related migrations
Sources: official documentation
- Import to Freshdesk — Freshworks Marketplace
- Import and export customers and company information — Freshdesk
- Throughput and plan-tier limits — Freshdesk
- Associating different object types in Freshdesk
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Sandboxes — Staging Environments for Customizing and Testing
Get a quote
Moving from Salesforce Service Cloud to Freshdesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.
Get a quote