Freshdesk to Intercom migration
We migrate Tickets, Contacts, Companies, and Conversations from Freshdesk into Intercom with the Ticket-to-Conversation model shift resolved upfront, channel types normalized across multi-channel sources, and every Freshdesk custom field mapped to an Intercom custom attribute before cutover.
FlitStack AI migrates conversations, users, companies, team members and conversation parts from Freshdesk to Intercom, 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 Freshdesk to Intercom?
Moving from Freshdesk to Intercom is a paradigm shift from a ticket-queue model to a messaging-first conversation model.
Read the full summary
Freshdesk organizes work around Tickets with statuses, priorities, and SLA clocks; Intercom organizes around Conversations with a state machine (open, closed, snoozed) and a separate Tickets feature for structured cases. We resolve this structural difference during scoping by mapping Freshdesk ticket status and priority to Intercom Conversation state and priority, and we flag Freshdesk tickets that should be created as Intercom Tickets versus Conversations based on the customer's workflow intent. We migrate the full conversation thread history as Conversation Parts, preserve agent and requester attribution, and normalize non-standard Freshdesk channel types (phone, tweet, Facebook, survey) to Intercom custom channel labels. Knowledge Base articles migrate as Intercom Articles within Collections. We do not migrate Automations, Macros, SLA Policies, or Freddy AI configuration; we deliver a written inventory of these for the customer's admin to rebuild in Intercom's workflow builder.
Ticket → Conversation (or Ticket)
Freshdesk Tickets map to Intercom Conversations by default.
How it maps
Tickets originating from a structured request workflow or requiring formal SLA tracking are flagged for Intercom Ticket creation instead. We preserve the Freshdesk ticket_id as a custom attribute fd_ticket_id__c on every Intercom Conversation for audit and cross-reference. Freshdesk status (Open, Pending, Resolved, Closed) maps to Intercom state (open, closed) with Pending mapped to snoozed. Freshdesk priority (Low, Medium, High, Urgent) maps to Intercom priority (none, low, medium, high). We handle the channel source normalization during transform: non-standard Freshdesk channels (phone, Twitter, Facebook, survey, forwarded email) default to a custom channel label stored in fd_channel_source__c.
Contact (Requester) → User (or Lead)
Freshdesk Contacts map to Intercom Users.
How it maps
The email address is the dedupe key. We map Freshdesk contact fields (name, email, phone, job_title, language) to Intercom user attributes (name, email, phone, job_title, custom language attribute). Custom contact fields migrate to Intercom custom attributes, which must be created in Intercom before import. Contacts associated with Companies in Freshdesk map to Intercom Users linked to an Intercom Company. We flag any Freshdesk Contact that is also an Agent to prevent duplicate User creation.
Company → Company
Freshdesk Companies map directly to Intercom Companies.
How it maps
Company name is the dedupe key. We map description, website, industry, and custom company fields to Intercom company attributes. The contact-to-company relationship resolves at migration time so that Users are linked to their correct Company on import.
Agent → Team Member
Freshdesk Agents (full-license users with group and role assignments) map to Intercom Team Members.
How it maps
Agent groups map to Intercom Teams, which are used for routing in Intercom's inbox configuration. We flag any Agent who is also a ticket Requester to prevent circular reference during User creation.
Conversation (Ticket Reply and Note) → Conversation Part
Freshdesk Conversations (public replies, private notes, and incoming emails within a Ticket) map to Intercom Conversation Parts.
How it maps
Each Part preserves author attribution (agent vs customer), body content, timestamp, and attachments. We preserve whether a Freshdesk conversation was a public reply or a private internal note by setting the Part type and visibility accordingly in Intercom. Conversation Parts are the last component imported against a Conversation to ensure the parent record exists.
Product → Product (Intercom custom object)
Freshdesk Products associate items with tickets for asset tracking.
How it maps
Intercom does not have a native Product object; we migrate Products as a custom object in Intercom and create a link attribute fd_product__c on the Conversation or a custom ticket field, depending on the customer's data model. Products must be created in Intercom as a custom object before migration.
- TicketConversation1:1
- ContactUser1:1
- CompanyCompany1:1
- AgentTeam Member1:1
- ConversationConversation Part1:1
- ProductProduct1:1
+ 6 more in the mapping below
How Freshdesk and Intercom 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 | Intercom |
|---|---|---|
| Core object model | Ticket-centric queue with status, priority, type, and SLA | Conversation-centric inbox with state machine; separate Tickets object for structured cases |
| Channel normalization | Phone, email, chat, Twitter, Facebook, survey, and forwarded email as separate channels | Email, chat, and custom channel labels; phone routes differently via third-party telephony |
| Knowledge base | Articles in Categories and Folders with multilingual .yml support | Articles in Collections and Sections with no native multilingual upload format |
| AI feature billing | Freddy AI charged per session ($49/100 sessions) on top of base plan | Fin AI charged per resolution ($0.99/resolution) on top of base plan; Essential lacks SLA entirely |
| Free plan API access | No API access on free plan; minimum Growth plan required for export | Starter plan at $74/month; Essential at $29/seat lacks SLA and full automation |
| Pricing model | Per-agent from $15-$89/agent/month; add-ons stack costs | Per-seat from $29-$$134/seat/month; add-ons for Fin and analytics stack costs |
| Collaborator concept | View-only Collaborators included up to 5,000 on paid plans | No direct Collaborator equivalent; team members are assigned as Responders or Watchers |
What to watch for in a Freshdesk to Intercom migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Intercom Conversations and Tickets are separate models
Freshdesk Tickets do not map 1:1 to a single Intercom object.
How we handle it
Intercom distinguishes between Conversations (messaging threads from chat, email, and proactive messages) and Tickets (structured support cases with SLA tracking). We resolve this split during scoping by interviewing the customer's team about which Freshdesk ticket types or workflows should land as Intercom Conversations vs Tickets. Migrations that skip this step end up with all tickets as Conversations that lack SLA clocks, or Tickets that lack the conversational context agents expect.
Non-standard Freshdesk channels require normalization
Freshdesk tickets can originate from phone, forwarded email, tweet, Facebook, survey feedback, or vendor responses in addition to standard email and chat.
How we handle it
Intercom's import API accepts email, chat, and custom message types. We normalize non-standard source channels to a custom Intercom attribute fd_channel_source__c and set the Conversation source to 'custom' to prevent import rejection. The original channel name is preserved in the attribute for auditability.
Freshdesk free plan blocks any API export
Freshdesk's free plan enforces 0 API calls per minute.
How we handle it
We cannot extract any data programmatically from a free-plan account. We require customers to be on at least the Growth plan ($15/agent/month) before migration scoping begins. We flag this during the first discovery call and advise upgrading early to avoid timeline delays, because Freshdesk's per-minute rate limits also vary by plan tier (200 calls/min on Growth, 700 calls/min on Enterprise) and we must adjust batch sizing accordingly.
Intercom attachment file type restrictions can block import
Intercom blocks certain file types (.exe, .sys, .scr, .shb, .wsf, and others) as potential malware vectors.
How we handle it
If Freshdesk tickets contain attachments in blocked types, the import skips those files and logs a warning. We scan for blocked file types during the audit phase and advise the customer to either enable 'Allow more file types' in Intercom security settings before migration or accept that those specific files will be excluded from the transfer.
Knowledge Base multilingual content requires manual restructuring
Freshdesk supports multilingual Knowledge Base articles via .yml file upload, where translations are stored in a structured file rather than as separate article records.
How we handle it
Intercom does not support .yml import for translations. We extract translation content from the .yml and create separate Article records per language, which increases the article record count and requires the customer to map languages in Intercom's language settings before migration begins.
How the migration runs
Discovery and Freshdesk plan verification
We audit the source Freshdesk account across plan tier (Free/Growth/Pro/Enterprise), ticket volume, custom field definitions, SLA policy inventory, Knowledge Base article count and language count, product list, and agent count.
What this step covers
We verify the plan tier because Free-plan accounts have zero API access and we cannot begin extraction. We scan for non-standard channel sources (phone, Twitter, Facebook, survey) and identify Knowledge Base articles with .yml-based translations that require restructuring. The discovery output is a written migration scope, a Freshdesk API rate-limit map for the customer's plan tier, and a questionnaire about which ticket types should land as Intercom Conversations vs Tickets.
Schema design and Intercom configuration preparation
We design the destination schema in Intercom before any data import.
What this step covers
This includes creating all custom user attributes (matching Freshdesk custom contact fields), custom company attributes (matching Freshdesk custom company fields), custom conversation attributes (fd_ticket_id__c, fd_channel_source__c, fd_original_tags__c), and any custom objects for Products. We also configure Intercom Teams to match Freshdesk agent groups, and we enable conversation ratings if CSAT data is migrating. Knowledge Base Collections and Sections are created to mirror the Freshdesk category-folder structure. Schema preparation happens in the customer's live Intercom workspace or a sandbox, depending on their preference.
Custom field and tag mapping review
We extract the full Freshdesk custom field schema (ticket fields and contact fields) and map each to an equivalent Intercom attribute type.
What this step covers
Select and multi-select custom fields map to Intercom dropdown and multiple-choice attributes. Date fields map to Intercom date attributes. Boolean fields map to boolean attributes. We review the Freshdesk tag taxonomy and map it to Intercom conversation labels and tags, flagging any tags that may need consolidation. The mapping document is reviewed by the customer's admin before migration begins.
Bulk extraction with rate-limit throttling
We extract all migration objects from Freshdesk using the REST API with per-endpoint rate-limit handling.
What this step covers
For Growth-plan accounts the tightest sub-limit is 20 calls/min for the Tickets List endpoint; we batch ticket fetches and use exponential backoff on 429 responses. We extract in dependency order: Companies first (because Users link to them), then Users, then Conversations and their Parts, then Knowledge Base Articles, then Products, then Tags. Each extraction phase emits a record count report. Time entries and CSAT ratings extract as separate batches tied to their parent ticket records.
Transformation, channel normalization, and Conversation-Ticket split
We transform the extracted Freshdesk data into Intercom-compatible format.
What this step covers
The Ticket-to-Conversation split runs as the first transform step using the customer's routing rules defined during discovery. Non-standard Freshdesk channel types normalize to the fd_channel_source__c attribute. Freshdesk SLA policy definitions document to a separate output rather than being applied as data. Time entries aggregate as duration sums in fd_time_spent__c and as Part notes for audit. We resolve agent-to-Team-Member references by email match and flag any unmapped agents for the customer's admin to provision.
Production import and delta sync
We import data into Intercom in dependency order: Companies first (for the company lookup on Users), then Users with company_id resolved, then Conversations with fd_ticket_id__c and fd_channel_source__c set, then Conversation Parts with author attribution preserved, then Knowledge Base Articles with collection assignments, then Products as a custom object.
What this step covers
Each phase runs in batches against Intercom's API with chunking and retry logic. We run a delta migration for any tickets created in Freshdesk during the migration window, tagged with a migration checkpoint timestamp, and merge those records before cutover.
Cutover, validation, and configuration handoff
We freeze Freshdesk writes during cutover, run a final delta import, then enable Intercom as the system of record.
What this step covers
We validate by spot-checking record counts (Tickets in, Conversations in, Users in, Articles in), checking 25-50 record samples against the Freshdesk source, and verifying that fd_ticket_id__c is populated on every Conversation for cross-reference. We deliver the SLA Policy audit document, the Macro and Automation inventory (for the customer to rebuild in Intercom's workflow builder), and the Knowledge Base multilingual translation log. We support a one-week post-cutover window for reconciliation issues. We do not rebuild Freshdesk automations or macros as Intercom workflows inside the migration scope.
- 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, Knowledge Base article count, and whether SLA policies require reconstruction documentation. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Freshdesk to Intercom →Why teams move from Freshdesk to Intercom
- Teams report that Freshdesk's Freddy AI session-based pricing creates unpredictable monthly bills at volume, while Intercom's Fin AI resolution model is more transparent for support leaders budgeting quarterly. Reviewers on G2 and Capterra cite AI cost predictability as a reason to evaluate Intercom despite Intercom's higher per-seat base price. The shift from per-session to per-resolution shifts the cost conversation from tooling usage to outcome volume.
- Freshdesk customers cite poor notification reliability, limited filtering, and bulk action constraints (50 records at a time) as recurring frustrations. Capterra reviews describe Freshdesk as functional but limited for teams that need modern inbox UX, real-time collaboration, and proactive messaging. Intercom's Inbox provides a conversation-first workspace designed for teams that blend support, onboarding, and customer success.
- Product-led SaaS teams choose Intercom because support lives inside the product. Intercom's proactive messenger, product tours, and Fin AI are built for the in-app customer journey rather than inbound ticket deflection. Teams migrating from Freshdesk to Intercom typically cite wanting to unify support, onboarding, and customer messaging under one platform rather than managing a ticketing tool alongside a separate engagement layer.
- Intercom's Fin AI resolves tickets autonomously at scale, and the platform's workflow builder (Operator) integrates directly with the product context. Teams with complex routing requirements, multi-step resolution workflows, or customer success automation needs find Intercom's platform more flexible than Freshdesk's per-plan feature gating. The ability to configure Fin without a separate AI module reduces the feature-stack cost compared to Freshdesk's add-on model.
- Add-ons for Freshchat, Freshcaller, advanced routing, and custom reporting stack up, making the true per-agent cost significantly higher than the base tier. Intercom's pricing tiers bundle more functionality (inbox, live chat, help center) into the base seat cost, and while Intercom's per-seat price is higher, the bundled feature set reduces the number of add-on modules required for a complete support stack.
Questions, answered
Freshdesk to Intercom migration questions
How long does a Freshdesk to Intercom migration take?
Small teams with under 20,000 tickets, clean custom fields, and no Knowledge Base migration complete in two to four weeks. Mid-market setups with multiple agent groups, active SLA policies, and Knowledge Base content with multiple languages move to four to six weeks. Enterprise migrations with multi-brand Freshdesk accounts, large conversation histories (over 200,000 conversation parts), or complex product-to-ticket associations move to six to eight weeks. Timeline is driven by Freshdesk's endpoint-specific API rate limits, the volume of data requiring transformation, and how quickly the customer reviews and approves the mapping document.
What Freshdesk data does not migrate to Intercom?
Automations, Macros, SLA Policies, and Freddy AI configuration do not migrate as code or data. We audit every active Freshdesk automation and macro and deliver a written inventory with each rule's trigger, conditions, and actions documented, along with the recommended equivalent in Intercom's workflow builder. SLA Policy definitions are documented for manual configuration in Intercom's inbox settings. Freddy AI sessions, Copilot configuration, and bot flows do not migrate and must be rebuilt in Intercom's Fin and Operator configuration. Reports and dashboards do not migrate; we deliver a field-level map so the customer's admin can rebuild reports in Intercom Analytics.
Will our Freshdesk tickets become Intercom Conversations or Tickets?
It depends on the ticket's workflow intent, and we resolve this during discovery. Freshdesk tickets that represent ongoing customer conversations (email threads, chat sessions, support requests) map to Intercom Conversations. Tickets that represent structured, formal support cases requiring SLA tracking, approval workflows, or escalation routing map to Intercom Tickets. We interview the customer's team during scoping to define the split rule, and we apply it during transformation. The Freshdesk ticket ID is preserved as fd_ticket_id__c on every Intercom record so that historical reference is never lost.
Can we migrate our Freshdesk Knowledge Base to Intercom?
Yes, we migrate Freshdesk Knowledge Base articles to Intercom Articles within Collections and Sections. The Freshdesk category-folder structure maps to Intercom's collection-section hierarchy. Articles with .yml-based multilingual translations require manual restructuring: we extract each translation from the .yml and create separate Article records per language, then the customer maps the languages in Intercom's workspace settings. Inline images in articles migrate as file attachments. Forum content (Community Topics and Posts) migrates as Articles within a Community Collection.
Do we need to upgrade from Freshdesk's free plan before migration?
Yes. Freshdesk's free plan has zero API access and no programmatic export capability. We cannot extract any data from a free-plan account. We require customers to be on at least the Growth plan ($15/agent/month) before we begin scoping. We recommend upgrading early because Freshdesk's per-minute API rate limits also vary by plan tier, and we need to calibrate our extraction batch sizes and polling intervals to the customer's specific rate-limit profile before migration begins.
How do we handle Freshdesk agents and groups in Intercom?
Freshdesk Agents map to Intercom Team Members. We resolve agents by email match during import. Freshdesk Agent Groups map to Intercom Teams, which are used for inbox routing and SLA assignment in Intercom. We flag any Freshdesk Agent who is also a ticket Requester to prevent duplicate User creation. Agents without a matching Intercom User account are held in a reconciliation queue for the customer's admin to provision before record import resumes.
Will historical conversation threads and attachments transfer completely?
Yes. Freshdesk conversation history (public replies, private notes, and incoming emails within a ticket) migrates as Intercom Conversation Parts with author attribution, body content, timestamp, and attachments preserved. Inline images and PDFs attach to the specific Part. We scan for file types that Intercom blocks (.exe, .sys, .scr, .shb, .wsf, and others) during the audit phase and advise the customer to enable 'Allow more file types' in Intercom's security settings or accept those files as excluded from the transfer.
Related migrations
Sources: official documentation
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
- Events limits, troubleshooting and F.A.Q — Intercom Help
- Import to Freshdesk — Freshworks Marketplace
- Import and export customers and company information — Freshdesk
- Throughput and plan-tier limits — Freshdesk
Get a quote
Moving from Freshdesk to Intercom?
Tell us roughly how many records and objects you have. We scope the mapping and the Intercom setup with you, then send a quote.
Get a quote