A Freshdesk-to-Salesforce migration takes 10–16 weeks and requires designing the Salesforce org before loading data. The hardest decision: CaseComment (plain text, no timestamps) vs. EmailMessage (HTML, full fidelity).
Migrating from Freshdesk to Salesforce Service Cloud is not a simple helpdesk swap but a full enterprise platform adoption that typically spans 10–16 weeks. No native migration path exists between the two systems; data must be extracted via Freshdesk's REST API and loaded into Salesforce using Bulk API 2.0, but only after the Salesforce org is fully configured. The fundamental data model difference is that Freshdesk is ticket-centric and permits orphaned contacts, while Salesforce enforces a strict Account → Contact → Case relational hierarchy. Significant custom work is required for conversation fidelity (mapping Freshdesk threaded replies to CaseComment or EmailMessage), automation redesign (translating Dispatch'r/Supervisor/Observer rules into governor-limit-safe Flows), and extensive Salesforce org configuration including Record Types, Queues, picklist values, and custom fields—all before any data loading can begin.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Timestamp preservation
CaseComment.CreatedDate is system-set and cannot be overridden via standard API by default. Salesforce's Create Audit Fields feature allows CreatedDate and CreatedById to be set on insert (not upsert), but this must be enabled per org and is not available in all editions — specifically, it is available in Enterprise, Unlimited, and Performance editions but not Professional (help.salesforce.com). If you need original timestamps without this feature, use EmailMessage where MessageDate is settable. Make the conversation fidelity decision in week 1 with a sample test load of 50–100 tickets. Teams that start with CaseComment and pivot to EmailMessage mid-project lose 2–3 weeks.
Governor limits during data load
Salesforce enforces per-transaction limits — 100 SOQL queries, 150 DML statements, 6 MB heap size, 10,000ms CPU time. If Record-Triggered Flows are active during migration, they fire on every inserted record. A non-bulkified Flow will fail when processing the standard trigger batch of 200 records. Temporarily deactivate non-critical Flows during data load or implement a "Bypass Automation" Custom Setting that each Flow checks before executing — set it to true during migration loads.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Freshdesk
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Salesforce Service Cloud can hold your support model
Walk your current workflow through Salesforce Service Cloud: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Freshdesk → Salesforce Service Cloud timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Freshdesk → Salesforce Service Cloud specifics
- Platform consolidation
- The organization is standardizing on Salesforce across sales, marketing, and service. One Account record connecting pipeline deals, support Cases, and marketing engagement eliminates the data silo between Freshdesk and the CRM.
- Enterprise service features
- Salesforce offers Entitlements and Milestones for complex multi-tier SLA management, Omni-Channel for real-time presence-based routing with agent capacity management, and Einstein AI for predictive case classification and routing.
- Regulatory requirements
- Salesforce's security model — Shield Platform Encryption, Event Monitoring, Field Audit Trail — satisfies compliance mandates (HIPAA, FedRAMP, SOX) that Freshdesk's security layer cannot.
- Programmability
- The team needs Apex, Lightning Web Components, custom APIs, or governor-limit-aware automation that Freshdesk's configuration model cannot accommodate.
- Platform vs. Product
- Freshdesk is a self-contained helpdesk. Salesforce is a fully programmable platform with its own database, automation engine (Flows), and deployment infrastructure (sandboxes, change sets, Salesforce CLI).
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Freshdesk export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Freshdesk export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Freshdesk where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Freshdesk → Salesforce Service Cloud field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Freshdesk → Salesforce Service Cloud field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Salesforce Service Cloud has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Freshdesk → Salesforce Service Cloud specifics
- Freshdesk Tickets → Salesforce Cases
- Each ticket becomes one Case. Freshdesk statuses (Open, Pending, Resolved, Closed + custom) map to Salesforce Case Status picklist values. Freshdesk priority (1 Low, 2 Medium, 3 High, 4 Urgent) maps to Case Priority. Freshdesk ticket types (Question, Incident, Problem, Feature Request) map to Case Type or Record Type. Freshdesk ticket source (Email, Portal, Phone, Chat) maps to Case Origin — add any missing picklist values before data load. Be careful with status design: Salesforce distinguishes between "Closed" (IsClosed = true) and other statuses, and closed values in Lightning depend on Sup
- Freshdesk Companies → Salesforce Accounts
- Accounts sit at the top of the data hierarchy. Map core fields (Name, Domain, Description). Load these first.
- Freshdesk Contacts → Salesforce Contacts
- Every Salesforce Contact must have an AccountId. Freshdesk contacts without a company association will fail to load. Audit for orphaned contacts and assign a default "Individual" Account or associate by email domain before migration.
- Freshdesk Agents → Salesforce Users
- Not a data import — a configuration task. Each agent needs a Salesforce license, a Profile (defining object access), and Permission Sets.
- Freshdesk Groups → Salesforce Queues
- Create Queues in Setup, assign agent members, and integrate with Omni-Channel for real-time routing. Queue-based Omni-Channel is the normal first implementation; skills-based routing is a second layer, not a default shortcut.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Salesforce Service Cloud sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Salesforce Service Cloud sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Salesforce Service Cloud's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Freshdesk → Salesforce Service Cloud specifics
- Sandbox allocation
- Professional edition includes 1 developer sandbox only. Enterprise includes 1 partial copy + 25 developer sandboxes. Unlimited includes 1 full copy sandbox. Full copy sandboxes are required for realistic data-volume testing.
- Closed-status behavior
- Verify that migrated closed Cases display correctly in the Lightning Service Console with the expected Support Process lifecycle. Open a closed Case to confirm the status picklist shows the correct available transitions.
- Email-to-Case threading
- Send test replies to migrated Cases from external email accounts to verify threading behavior. Test with both recent and old migrated Cases.
- Omni-Channel routing
- Create test Cases assigned to Queues and verify they route to available agents based on presence status and capacity configuration.
- UAT with agents
- Have 3–5 agents work in the Lightning Service Console for 2–3 days handling real or simulated cases. Collect feedback on macro functionality, Omni-Channel routing, Quick Text, Knowledge search, and layout usability.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Salesforce Service Cloud, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Freshdesk stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Salesforce Service Cloud's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Freshdesk and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Freshdesk read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Freshdesk → Salesforce Service Cloud specifics
- Immediate (Day 1–3)
- Revert Email-to-Case routing back to Freshdesk by changing MX records or email forwarding rules. Agents return to Freshdesk for new tickets. Salesforce retains the migrated data but is not the active system.
- Short-term (Week 1–2)
- Fix the identified issues in the Salesforce sandbox, redeploy, and reload any data that was corrupted. Because external IDs enable idempotent upserts on parent records, re-running the load is safe.
- Abandon (rare)
- If the Salesforce org design is fundamentally wrong, the team continues using Freshdesk while the SI redesigns. Migrated data in Salesforce can be deleted via Bulk API hard-delete.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Freshdesk and Salesforce Service Cloud record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Salesforce Service Cloud, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Freshdesk read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
-
Record-count reconciliation
Compare Freshdesk export counts against Salesforce SOQL COUNT() queries for Cases, Contacts, Accounts, CaseComments/EmailMessages, ContentVersions, and Knowledge Articles. Accept ≤0.1% variance; investigate any variance above that.
Freshdesk → Salesforce Service Cloud specifics
- Referential integrity verification
- Run Salesforce reports or SOQL queries to identify orphaned records: SELECT Id FROM Case WHERE ContactId = null, SELECT Id FROM CaseComment WHERE ParentId NOT IN (SELECT Id FROM Case).
- Conversation fidelity verification
- Sample 50+ Cases across different channels (email, portal, phone, chat) and date ranges. Verify that HTML is preserved (if using EmailMessage), author attribution is correct, and timestamps match Freshdesk source data within 1 second.
- Flow validation
- Create 200+ Cases in a single batch to confirm that Record-Triggered Flows execute successfully without hitting governor limits. Check debug logs for any flow errors.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets (Cases) | medium | Core ticket fields map cleanly to Case, but status, priority, and source values require picklist pre-configuration and integer-to-label translation, and the Freshdesk ticket ID must be stored as an External ID for relational linking. |
| Contacts | high | Freshdesk allows orphaned contacts without company associations, but Salesforce mandates an AccountId on every Contact, requiring pre-migration auditing and domain-based or default Account assignment. |
| Companies (Accounts) | low | Freshdesk Companies map directly to Salesforce Accounts with straightforward field mappings and must be loaded first to establish the parent hierarchy. |
| Ticket Conversations | high | Freshdesk's threaded replies with rich HTML, sender metadata, and public/private distinction have no exact Salesforce equivalent, requiring a complex architectural choice between CaseComment and EmailMessage with potential loss of fidelity. |
| Attachments (Files) | medium | Attachments must be migrated as ContentVersion and ContentDocumentLink records in Lightning Experience, and large volumes can exceed Salesforce's base storage allocation, triggering significant overage costs. |
| Custom Fields | medium | Freshdesk custom ticket fields require strict type matching to Salesforce custom fields on Case (e.g., dropdowns to Picklists with pre-defined values), and all fields must exist in Salesforce metadata before data loading. |
| Tags | medium | Salesforce's native Tag feature is limited and rarely used, so Freshdesk tags must be migrated to a custom multi-select picklist (max 500 values) or text field, requiring value enumeration and metadata setup. |
| Knowledge Base Articles | medium | Freshdesk Solutions must be restructured into Salesforce Knowledge articles with Data Category Groups and Data Categories, subject to default limits of 3 active groups and 100 categories per group. |
| Agents (Users) | low | Agent migration is a configuration task rather than a data import, but each agent requires a Salesforce license, Profile, and Permission Sets to be provisioned before case ownership can be assigned. |
| Groups (Queues) | low | Freshdesk Groups map to Salesforce Queues which must be created in Setup with member assignments and optionally integrated with Omni-Channel for presence-based routing. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Enforced Account-Contact Hierarchy
Salesforce requires every Contact to have an AccountId, so Freshdesk contacts without a company association must be audited and assigned to a default Account or matched by email domain before migration.
Conversation and Thread Fidelity
Freshdesk's rich threaded ticket replies have no direct equivalent in Salesforce, requiring a deliberate architectural choice between CaseComment (plain text, no sender metadata) and EmailMessage (preserves headers and threading but is more complex to load).
Automation Redesign Under Governor Limits
Freshdesk's three simple automation engines (Dispatch'r, Supervisor, Observer) must be rebuilt as Salesforce Flows that comply with strict per-transaction governor limits including 100 SOQL queries, 150 DML statements, and 10,000ms CPU time.
Salesforce Org Configuration Prerequisite
All custom fields, picklist values, Record Types, Support Processes, Queues, and page layouts must be fully defined in Salesforce metadata before any data loading can begin, creating a large sequential dependency.
File Storage Cost and Limits
Salesforce base storage is 10 GB plus 2 GB per user with expensive overage pricing, so migrating Freshdesk attachment volumes requires careful storage auditing and budget planning before loading ContentVersion records.
Knowledge Base Structure Mapping
Freshdesk's Solutions hierarchy of Categories and Folders must be mapped to Salesforce Data Category Groups and Data Categories, which have default limits of 3 active groups and 100 categories per group that can constrain deeply nested knowledge bases.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
CaseComment timestamp loss
By default, CaseComment.CreatedDate cannot be set via standard API — all migrated comments show the migration date. Salesforce's Create Audit Fields feature can override this on insert (available in Enterprise, Unlimited, and Performance editions) (help.salesforce.com), but it must be enabled per org and does not work with upsert — only insert. If unavailable, use EmailMessage where MessageDate is settable without any special feature enablement.
Account-Contact hierarchy enforcement
Freshdesk contacts without a company association fail Salesforce Contact insert. Options: create a default "Individual" Account, or pre-process contacts by email domain matching against existing Accounts during transformation.
Rich HTML stripping
CaseComment.CommentBody is plain text only. Inline images, links, tables, and text formatting from Freshdesk replies will be stripped. Use EmailMessage.HtmlBody to preserve formatting.
Picklist value mismatches
Salesforce rejects records with picklist values not defined in metadata. Every Freshdesk dropdown value must exist as a Salesforce picklist value before data load. Missing values cause silent batch failures (records appear in failedResults but the job itself may show as "Completed").
Attachment storage limits
Check current Salesforce storage allocation via Setup → Storage Usage. A Freshdesk instance with 50 GB of attachments against a Salesforce org with 70 GB allocated may appear safe until you account for existing Salesforce data consumption.
Duplicate contacts
Freshdesk may have duplicate contacts (same email, different records). Salesforce Duplicate Management rules can block inserts. Dedup in the transformation layer or temporarily set Duplicate Rules to "Allow" with an alert during migration, then re-enable blocking rules post-cutover.
Closed status mapping
Closed values need Support Process alignment and the IsClosed flag in the Status picklist metadata. Without this configuration, agents will not see the expected status lifecycle in the Lightning Console — even if the data loaded successfully.
Email threading on old threads
Once you switch from Freshdesk to Salesforce, customer replies only attach to the correct Case if Salesforce can match the inbound message using its Thread-Id header format. Otherwise a new Case is created. There is no way to retroactively inject Freshdesk email thread IDs into Salesforce's threading mechanism.
Freshdesk Mint vs. Classic
If your Freshdesk instance is still on Classic (pre-2019), some API endpoints and export formats may differ. Verify API responses against current documentation before building extraction scripts.
Telephony is a separate project
Freshcaller configuration does not transfer. Salesforce documents Open CTI as maintenance-mode with retirement scheduled for February 28, 2028; Service Cloud Voice with Amazon Connect is the native direction (help.salesforce.com).
Customer portal is a separate project
The Freshdesk portal does not migrate. The Salesforce equivalent is Experience Cloud — a distinct build with separate licensing (Customer Community or Customer Community Plus) and configuration that typically adds 4–8 weeks to the project.
Omni-Channel requires upfront configuration
Freshdesk assigns tickets via Dispatch'r or round-robin. Salesforce Omni-Channel provides real-time, capacity-based routing but requires Service Channels, Presence Statuses, Routing Configurations, and Presence Status assignments to Profiles before agents can receive work.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How long does a Freshdesk to Salesforce Service Cloud migration take?
A typical migration takes 10–12 weeks: 3–8 weeks for Salesforce org design and configuration, 2–4 weeks for data migration, and 2–4 weeks for testing, training, and go-live. Complex enterprise orgs with multiple Record Types, Entitlements, and Omni-Channel routing should plan for 14–16 weeks.
Can I keep my full Freshdesk ticket history in Salesforce?
Yes. Ticket metadata (subject, status, priority, custom fields) migrates cleanly to Cases. Conversation history requires choosing between CaseComment (plain text, no original timestamps by default) or EmailMessage (HTML, settable timestamps, full fidelity). Attachments migrate as Salesforce Files (ContentVersion + ContentDocumentLink).
What is the difference between CaseComment and EmailMessage in Salesforce?
CaseComment stores flat plain text with a 4,000-character practical limit and a system-set CreatedDate that cannot be overridden via standard API without the Create Audit Fields feature enabled. EmailMessage supports HtmlBody for rich formatting, a settable MessageDate for timestamp preservation, From/To/CC addresses, and file attachments. Use EmailMessage when conversation fidelity matters.
Why does migrating to Salesforce take longer than switching to Zendesk?
Salesforce requires an org design phase — custom fields, record types, page layouts, profiles, Entitlements, Omni-Channel configuration — that takes 3–8 weeks and does not exist in helpdesk-to-helpdesk migrations. This is the primary driver of the 3–10x timeline multiplier compared to a Freshdesk-to-Zendesk move.
Can Freshdesk automations be migrated to Salesforce?
Not directly. Freshdesk's Dispatch'r maps to Case Assignment Rules and Record-Triggered Flows. Supervisor maps to Entitlements/Milestones or Scheduled Flows. Observer maps to Record-Triggered Flows. This is a redesign, not a data migration — and it requires understanding Salesforce governor limits (100 SOQL queries, 150 DML statements per transaction).