---
title: "Freshdesk to Salesforce Service Cloud Migration"
description: "Migrate Freshdesk to Salesforce Service Cloud with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/freshdesk/to/salesforce-service-cloud"
---

# Freshdesk to Salesforce Service Cloud migration

We migrate Tickets, Contacts, Companies, and Conversation history from Freshdesk into Salesforce Service Cloud with Freshdesk's API rate limits pre-mapped per plan tier, case-to-account lookups resolved before insert, and every channel source normalized to Salesforce's Case Origin taxonomy.

Short answer

FlitStack AI migrates cases, emailmessages, contacts, accounts and users from Freshdesk to Salesforce Service Cloud, 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: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/freshdesk/to/salesforce-service-cloud#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Freshdesk ![](https://flitstack.ai/platforms-trim/freshdesk.webp)

Destination Salesforce Service Cloud ![](https://flitstack.ai/platforms-trim/salesforce-service-cloud.webp)

Case EmailMessage Contact Account User

Mapped field by field · sample run · one-click rollback

## What moves from Freshdesk to Salesforce Service Cloud?

Moving from Freshdesk to Salesforce Service Cloud is a schema redesign, not a record copy.

Read the full summary

Freshdesk models support around a ticket-first paradigm with agents, requesters, and companies; Salesforce Service Cloud models service around Cases attached to Accounts and Contacts in a CRM hierarchy. We resolve the ticket-to-case transformation, preserve conversation threads as EmailMessage records, and maintain the Freshdesk company-to-Account lookup chain throughout. SLA policies, products, satisfaction ratings, and time entries migrate as typed Salesforce fields. Freshdesk automations and macros do not migrate as code; we deliver a written inventory of every Freshdesk automation requiring rebuild in Salesforce Flow. Knowledge base articles transfer with folder structure intact, and we normalize non-standard channel sources (phone, Facebook, tweet, forwarded email) to Salesforce Case Origin values during transformation.

1:1

### Ticket → Case

Freshdesk Tickets map directly to Salesforce Cases.

How it maps

We transform Freshdesk status (Open, Pending, Resolved, Closed) to Salesforce Status (New, Working, Escalated, Closed), and priority maps to Case Priority with a custom field fd\_original\_priority\_\_c preserving the source value. The Freshdesk agent assignment resolves to Salesforce Case OwnerId via User email lookup. Non-standard channel sources (phone, Facebook, tweet, survey feedback) are normalized to Salesforce Case Origin values during transformation with the original channel name stored in a custom fd\_channel\_source\_\_c field.

1:1

### Conversation (Replies and Notes) → EmailMessage

Freshdesk ticket conversations (incoming emails, public replies, private notes) map to Salesforce EmailMessage records linked to the Case.

How it maps

We separate public conversations from private notes: public threads become EmailMessage with IsIncoming=false for agent replies and IsIncoming=true for customer messages; private notes map to a custom fd\_private\_note\_\_c field on the Case to preserve audit context without creating a separate EmailMessage record. Attachments migrate as ContentDocument records linked via ContentDocumentLink.

1:1

### Contact (Requester) → Contact

Freshdesk Contacts (requesters) map to Salesforce Contact.

How it maps

We resolve the parent Account via Freshdesk company\_id and link Contact.AccountId before insert. Custom contact fields from Freshdesk Admin > Support Operations > Customer Fields create matching Salesforce custom fields on Contact. Email uniqueness is enforced as the dedupe key; contacts with duplicate emails receive a fd\_original\_id\_\_c suffix for manual reconciliation.

1:1

### Company → Account

Freshdesk Companies map to Salesforce Account.

How it maps

The company domain becomes the Account Website field and is used as the dedupe key during import. Freshdesk company custom fields map to Salesforce Account custom fields. We create Account records before Contact import so that Contact.AccountId references are satisfied at insert time.

lookup

### Agent → User

Freshdesk Agents map to Salesforce User records by email match.

How it maps

We extract every distinct agent referenced on Tickets and Conversations and match against the destination Salesforce org's User table. Agents without a matching User go to a reconciliation queue for the customer admin to provision before migration resumes. Agents who are also ticket requesters are flagged to prevent circular ownership references.

1:1

### Product → Product2

Freshdesk Products associated with tickets migrate as Salesforce Product2 records with a custom fd\_product\_id\_\_c field preserving the Freshdesk product reference.

How it maps

Product-to-ticket associations transfer as a custom multi-select picklist fd\_associated\_products\_\_c on the Case. Standard Pricebook entries are created during migration if the customer uses Opportunity-based selling in Salesforce.

******What moves 12 objects

Freshdesk Salesforce Service Cloud

- Ticket Case 1:1
- Conversation EmailMessage 1:1
- Contact Contact 1:1
- Company Account 1:1
- Agent User transformed
- Product Product2 1:1

\+ 6 more in the mapping below

## How Freshdesk and Salesforce Service Cloud 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                     | Freshdesk                                                                                                          | Salesforce Service Cloud                                                                                                 |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Ticket model                  | Ticket is the primary object with agent, requester, and company links                                              | Case attaches to Account and Contact in a CRM hierarchy with separate Lead object for prospects                          |
| Channel source normalization  | Phone, email, chat, Facebook, tweet, survey feedback, and forwarded email as separate channel types                | Case Origin covers Email, Phone, Web, and custom values; social and survey sources require custom field or normalization |
| API rate limits               | Account-wide per-minute limits that scale from 0 (free) to 700/min (Enterprise) with tight sub-limits per endpoint | Bulk API 2.0 with 150,000 batch size; Composite API for parent-record resolution; REST API with per-user rate limits     |
| Custom object access          | In-product custom objects are isolated and inaccessible to programmatic export                                     | Custom objects available from Professional tier via standard \_\_c schema with full API access                           |
| Knowledge base structure      | Articles in folders with multi-language support via .yml file upload                                               | Knowledge Articles with Data Category Groups for navigation; multi-language via Translation Workbench                    |
| SLA policies                  | Available on Pro and Enterprise plans as named policies with response and resolution hours                         | Entitlement Processes and Milestones tied to Case Record Type and Entitlement on Account                                 |
| Per-agent vs per-user pricing | Per-agent pricing from $15 to $89/month; API access requires paid plan                                             | Per-user pricing from $25 to $550/month depending on edition; API access included from Professional                      |

## What to watch for in a Freshdesk to Salesforce Service Cloud migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Freshdesk API access is disabled on the free plan

Freshdesk's free plan explicitly has 0 API calls per minute and no API access.

How we handle it

Any migration tooling that relies on the Freshdesk REST API fails immediately for free-plan accounts. We require customers to upgrade to at least the Growth plan before we can begin any programmatic export. We flag this during scoping and advise customers to upgrade early because Freshdesk plan upgrades require billing cycle alignment that can add days to the project timeline if not anticipated.

high

### Freshdesk rate limits are account-wide and endpoint-specific

Freshdesk enforces rate limits per account rather than per agent, and each endpoint has its own sub-limit.

How we handle it

Growth allows 200 calls/min total but only 20 calls/min for the Tickets List endpoint. We throttle export queries to the tightest sub-limit per plan tier and implement exponential backoff on 429 responses. We pre-map each migration to the customer's plan tier rate limits before starting any data pull. Skipping this step results in truncated exports and missing records in Salesforce.

medium

### Non-standard channel sources require normalization

Freshdesk tickets can originate from phone, forwarded email, tweet, survey feedback, or Facebook in addition to standard email and portal.

How we handle it

Salesforce Case Origin only supports Email, Phone, Web, and custom values by default. We normalize non-standard source channels to a custom fd\_channel\_source\_\_c field on Case and set Case Origin to the closest Salesforce equivalent. The original Freshdesk channel name is preserved in the custom field for audit and reporting.

medium

### In-product Freshdesk custom objects are inaccessible

Custom objects created via the in-product experience in Freshdesk are isolated and cannot be accessed programmatically.

How we handle it

Only custom objects created via the Freshdesk Custom Objects API are accessible to our extraction tooling. We confirm during scoping whether custom objects were created via API or in-product. In-product-only custom objects may require manual CSV export by the customer, which we coordinate as a pre-migration deliverable.

medium

### Salesforce triggers and validation rules can block case import

Salesforce orgs commonly enforce validation rules, required field formats, conditional required fields, and before-insert triggers that reject migrating records.

How we handle it

We coordinate with the customer's Salesforce admin to grant the migration user the API Enabled and Bulk API permissions and to either temporarily disable blocking validation rules or add a migration-context bypass flag. Skipping this step typically results in 10-25 percent case rejection on the first import attempt, requiring a second pass.

## How the migration runs

1. ### Discovery and plan tier audit

   We audit the source Freshdesk account across plan tier (Free/Growth/Pro/Enterprise), API rate limits, object inventory (tickets, contacts, companies, agents, products, SLA policies, knowledge base, forums), active automations, and custom field definitions.

   What this step covers

   We confirm whether any Freshdesk custom objects were created via API or in-product. The discovery output is a written migration scope document with object counts, a mapping plan, and a Freshdesk plan upgrade recommendation if the customer is on the free tier.

2. ### Destination schema design in Salesforce Sandbox

   We design the Salesforce Service Cloud destination schema in a Sandbox org.

   What this step covers

   This includes provisioning custom fields on Case, Contact, and Account (with fd\_ prefix to preserve Freshdesk origin), configuring Case Origin picklist values, setting up Entitlement Processes and Milestones from Freshdesk SLA policies, creating Knowledge data category groups from Freshdesk article folders, and designing the Topic or tag strategy. Page Layouts and Record Types are configured per the customer's case routing requirements. All schema is deployed via metadata API into Sandbox first for validation.

3. ### Sandbox migration and reconciliation

   We run a full migration into the Salesforce Sandbox using production-like data volume.

   What this step covers

   The customer reconciles record counts (Cases in, Contacts in, Accounts in, EmailMessages in, Knowledge Articles in), spot-checks 25-50 random cases against the Freshdesk source for field accuracy and conversation completeness, and signs off the schema and mapping before production migration begins. Any field mapping corrections, validation rule gaps, or rate-limit adjustments happen in Sandbox, not in production.

4. ### Owner reconciliation and User provisioning

   We extract every distinct Freshdesk agent referenced on Tickets and Conversations and match by email against the destination Salesforce org's User table.

   What this step covers

   Agents without a matching User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users before record import resumes. This step gates the production migration because Case OwnerId references are required at insert time.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Accounts (from Freshdesk Companies), Contacts (with AccountId resolved), Cases (with ContactId and OwnerId resolved, channel source normalized), Products, EmailMessage conversation history (via Bulk API 2.0 with parent-record resolution), Time Entries, Satisfaction Ratings, Tags (as Topics or custom field), Knowledge Base Articles with folder structure, and Forum data last.

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, delta migration, and automation handoff

   We freeze Freshdesk writes during cutover, run a final delta migration of any records created or updated during the migration window, then enable Salesforce as the system of record.

   What this step covers

   We deliver the Freshdesk automation and macro inventory document to the customer's admin team for rebuild in Salesforce Flow. We support a one-week hypercare window where we resolve reconciliation issues raised by the support team. We do not rebuild Freshdesk automations, macros, or SLA policies as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.

![](https://flitstack.ai/platforms/freshdesk.svg) Freshdesk ![](https://flitstack.ai/platforms/salesforce-service-cloud.svg) Salesforce Service Cloud

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Salesforce Service Cloud Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with record volume, custom object count, and whether the destination org requires a full CRM schema or Service Cloud standalone. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Freshdesk to Salesforce Service Cloud →](https://flitstack.ai/contact)

## Why teams move from Freshdesk to Salesforce Service Cloud

- Freshdesk's pricing add-ons accumulate silently. Teams on Pro or Enterprise find that Freddy AI sessions, Freshchat, Freshcaller, and advanced reporting are billed separately, pushing effective cost significantly above the per-agent headline rate. Salesforce Service Cloud bundles omnichannel routing, case management, and basic AI at the Professional tier without per-session or per-feature billing, providing more predictable cost at scale.
- Freshdesk lacks deep integration with sales and marketing data. Teams running both a support desk and a CRM find themselves duplicating customer records across systems. Salesforce Service Cloud shares the same data model as Sales Cloud and Marketing Cloud, giving support agents a 360-degree view of the customer without re-entering data or maintaining a separate integration layer.
- Customization limits frustrate teams with complex routing logic. Reviewers on Reddit and G2 note that Freshdesk's automation builder cannot handle multi-condition branching with mixed AND/OR logic across 240+ distinct rules without significant workaround. Salesforce Flow supports record-triggered, scheduled, screen, and autolaunched flows with the complexity required for enterprise routing, even if rebuilding that logic from scratch is non-trivial.
- Freshdesk performance degrades under high-volume periods with ticket loading delays and occasional dropped channels, per customer reports on Capterra and G2. Salesforce Service Cloud is architected for enterprise-scale throughput with dedicated infrastructure per org and no noisy-neighbor constraints from shared multi-tenant resources.

Questions, answered

## Freshdesk to Salesforce Service Cloud migration questions

How long does a Freshdesk to Salesforce Service Cloud migration take?

Most migrations land between three and five weeks for accounts under 20,000 tickets and 10,000 contacts with no custom objects or knowledge base migration. Migrations with custom objects, large conversation histories (over 200,000 messages), SLA policy transfer, or Knowledge Base migration with folder structure preservation move to eight to twelve weeks because of Bulk API time, entitlement process configuration, and knowledge article versioning.

Do Freshdesk automations, macros, and SLA policies migrate to Salesforce?

No. Freshdesk automations, macros, and SLA policies are structurally different from Salesforce Flow, Assignment Rules, and Entitlement Processes. We do not migrate them as code. We deliver a written inventory of every Freshdesk automation and macro with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration. SLA policies are the exception: we audit and map them to Salesforce Entitlement Processes and Milestones as a configuration step during migration.

Can we migrate Freshdesk Knowledge Base articles with folder structure?

Yes. Freshdesk Articles migrate to Salesforce Knowledge Articles with folder hierarchy preserved as Data Category Groups. Multi-language articles migrate as separate Salesforce Knowledge Article Versions linked to the master record. Attachments migrate as ContentDocument records. We scope the Knowledge Base migration during discovery because it adds complexity to the timeline and requires the Salesforce admin to configure Knowledge settings and article types in the destination org before import.

Do we lose conversation history and private notes?

No. We migrate the full conversation thread including public replies, incoming customer messages, and private notes. Public conversations migrate as Salesforce EmailMessage records linked to the Case. Private notes migrate to a custom fd\_private\_note\_\_c field on the Case to preserve audit context. Attachments migrate as ContentDocument records linked via ContentDocumentLink. We use the Salesforce Bulk API 2.0 with parent-record resolution to handle large conversation volumes without timeouts.

What happens to Freshdesk's multi-channel ticket sources in Salesforce?

Freshdesk tickets can originate from email, phone, chat, Facebook, tweet, survey feedback, or forwarded email. Salesforce Case Origin supports Email, Phone, Web, and custom values by default. We normalize non-standard sources (Facebook, tweet, survey, forwarded email) to a custom fd\_channel\_source\_\_c field on Case and set Case Origin to the closest Salesforce-supported value. The original channel name is preserved in the custom field for auditability and reporting.

We are on the Freshdesk free plan. Can FlitStack AI still migrate our data?

No. Freshdesk's free plan has 0 API calls per minute and no API access. Our extraction tooling uses the Freshdesk REST API, which is unavailable on the free tier. We require customers to upgrade to at least the Growth plan ($15/agent/month) before we can begin any programmatic export. We flag this during scoping so that the upgrade happens early in the project timeline rather than causing delays after discovery is complete.

## Related migrations

[![](https://flitstack.ai/platforms-trim/salesforce-service-cloud.webp) Migrate to **Salesforce Service Cloud** Every source we move into Salesforce Service Cloud, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud)

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

[Set up Salesforce Service Cloud and migrate into it as one engagement.](https://flitstack.ai/services/salesforce-implementation)

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Salesforce Service Cloud to Freshdesk** The same pair in reverse](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/freshdesk) [**Zendesk to Salesforce Service Cloud** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/salesforce-service-cloud) [**Freshdesk to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/zendesk) [**Freshdesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/intercom) [**Freshdesk to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/hubspot-service-hub)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Sandboxes — Staging Environments for Customizing and Testing](https://help.salesforce.com/s/articleView?id=platform.deploy_sandboxes_parent.htm)
4. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
5. [Import to Freshdesk — Freshworks Marketplace](https://www.freshworks.com/apps/import_to_freshdesk/)
6. [Import and export customers and company information — Freshdesk](https://support.freshdesk.com/support/solutions/articles/196491-importing-and-exporting-customer-data)
7. [Throughput and plan-tier limits — Freshdesk](https://support.freshdesk.com/support/solutions/articles/225439)

Get a quote

## Moving from Freshdesk to Salesforce Service Cloud?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce Service Cloud setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
