Intercom to Freshdesk migration
We migrate Contacts, Conversations, Tickets, and Help Center Articles from Intercom into Freshdesk with knowledge base hierarchy flattened to Freshdesk's three-level structure, conversation threads merged into ticket records, and every Agent mapped to the corresponding Freshdesk agent account before cutover.
FlitStack AI migrates contacts, organizations, tickets, ticket replies and ticket notes from Intercom 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: 3-5 weeks.

What moves from Intercom to Freshdesk?
Moving from Intercom to Freshdesk is a conversation-to-ticket migration with several structural adjustments required.
Read the full summary
Intercom organizes around a conversation-centric model where every customer touchpoint threads into a single Conversation, while Freshdesk uses a traditional ticket object with SLA policies, collision detection, and parent-child nesting for complex issues. We map Intercom Conversations to Freshdesk Tickets, Intercom Contacts to Freshdesk Contacts, Intercom Companies to Freshdesk Organizations, and Intercom Admins to Freshdesk Agents. The knowledge base requires flattening because Intercom permits Collections without Sections while Freshdesk enforces a three-level hierarchy (Category, Folder, Article). Freshdesk's API rate limits (200-700 calls per minute depending on plan) require chunking and backoff logic that we implement during migration. Workflows, Bots, Outbound automation, and Fin AI configuration do not migrate; we deliver a written inventory of every automation for the customer's admin to rebuild in Freshdesk's Rules engine.
Contact → Contact
Intercom Contacts (Users and Leads) map directly to Freshdesk Contacts.
How it maps
Email, name, phone, custom attributes, and owner assignment transfer. We resolve the Freshdesk agent corresponding to the Intercom owner and populate Freshdesk's agent_id on the Contact record. Custom attributes on Contact require field-level mapping because Intercom's workspace-specific attribute names and types must be typed correctly against Freshdesk's custom field definitions.
Company → Organization
Intercom Companies map to Freshdesk Organizations.
How it maps
Company name, domain, plan, monthly_spend, and custom attributes transfer. The Organization becomes the parent for all related Contacts, preserving the company-contact association. We resolve Freshdesk Groups or Agents by matching the Intercom team or admin owner assigned to the company record.
Conversation → Ticket
Intercom Conversations with nested Parts (messages, notes, assignments, ratings) merge into a single Freshdesk Ticket.
How it maps
The conversation subject becomes the Ticket subject, the first customer message becomes the Ticket description, and subsequent Parts append as Ticket Replies or internal Notes based on Part type. Conversation state (open, closed, snoozed) maps to Freshdesk Ticket status (open, pending, resolved, closed). We pull full conversation content via Intercom's REST API because the S3 JSON export excludes transcripts.
Conversation Part (message type) → Ticket Reply
Intercom Parts with part_type = comment (customer or agent messages) become Freshdesk Ticket Replies.
How it maps
We preserve message body, attachments, and delivery timestamp. Agent vs customer authorship determines the Freshdesk 'from_email' address on the reply. Outbound messages from Intercom (operator, campaign) that are not replies become Notes on the Freshdesk Ticket for internal context.
Conversation Part (note type) → Ticket Note (internal)
Intercom Parts with part_type = note (internal notes) map to Freshdesk internal Notes on the Ticket.
How it maps
Note body, author (agent), and created_at timestamp transfer. This preserves the internal collaboration history that agents used while working the conversation.
Admin → Agent
Intercom Admins map to Freshdesk Agents.
How it maps
Agent identity (name, email, role) transfers, and conversation assignments in Intercom resolve to agent assignments in Freshdesk via email matching. Inactive or deleted Intercom Admins are reconciled against the Freshdesk agent list during scoping; missing agents are provisioned or reassigned before migration begins.
- ContactContact1:1
- CompanyOrganization1:1
- ConversationTicketmerged
- Conversation PartTicket Reply1:1
- Conversation PartTicket Note1:1
- AdminAgent1:1
+ 6 more in the mapping below
How Intercom 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 | Intercom | Freshdesk |
|---|---|---|
| Core data model | Conversation-first threading with Parts nested inside | Ticket-first with threaded Replies and Notes separated |
| Knowledge base hierarchy | Collection > Section > Article or Collection > Article (two-level allowed) | Category > Folder > Article (three-level enforced) |
| AI pricing | $0.99 per Fin AI resolution on top of seat cost | Freddy AI Agent sessions included in Pro plan (first 500 free), then per-session pricing significantly lower than Intercom |
| API rate limit model | 10,000 calls/minute workspace limit shared across all private apps | 200-700 calls/minute per account by plan, with per-endpoint sub-limits |
| SLA tooling | No native SLA object; workflows approximate escalation | Native SLA policies with business hours, escalation rules, and fulfillment tracking |
| Pricing structure | Seat + per-resolution AI + channel add-ons; compounding cost | Per-agent flat tiers (Growth $19, Pro $55, Enterprise $89); predictable monthly billing |
| Multi-channel routing | Live chat, email, SMS, WhatsApp, Phone consolidated in one inbox | Omnichannel through separate products (Freshdesk + Freshchat for chat); unified in higher tiers |
What to watch for in a Intercom to Freshdesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Knowledge base hierarchy flattening required
Intercom permits a two-level help center structure (Collection > Article) without requiring a Section, but Freshdesk enforces a three-level hierarchy (Category > Folder > Article).
How we handle it
Articles without a parent Section in Intercom adopt a default Folder and Category during migration, which disrupts navigation and search. We flag articles that will be affected, and the customer may choose to pre-create a Section structure in the Intercom workspace before migration or accept the default Folder assignment and reorganize post-migration. We do not restructure the source knowledge base on the customer's behalf.
Freshdesk API per-endpoint sub-limits constrain write throughput
Freshdesk's v2 API enforces per-endpoint sub-limits within the overall plan rate limit.
How we handle it
On the Growth plan (200 calls/min), Ticket Create is limited to 80/min and Ticket Update to 80/min, while on Enterprise (700 calls/min), the sub-limits are 280/min each. We chunk ticket imports to stay within these sub-limits and implement exponential backoff when the X-RateLimit-Remaining header drops below a threshold. Migrations exceeding the plan's rate limit require either upselling the customer to a higher Freshdesk tier or scheduling migration windows during off-peak hours.
Intercom S3 JSON export omits conversation transcripts
Intercom's native Data Export to Amazon S3 stores conversation metadata and message bodies but explicitly excludes full conversation transcripts.
How we handle it
This means teams relying on the S3 export for migration will have incomplete message history. We address this by pulling full conversation content via the Intercom REST API retrieve-conversation endpoint for each conversation during migration, which includes the complete transcript at the cost of additional API calls per conversation. We scope and document the API call volume required so the customer can plan for any Intercom API quota impact during the migration window.
Intercom workspace automation does not migrate
Intercom workspaces operate in isolation — workflows, automation rules, custom bots, Outbound campaigns, and Fin AI configuration cannot be moved or duplicated between workspaces or to Freshdesk.
How we handle it
We do not migrate automation logic. We deliver a written inventory of every active Intercom automation rule, bot configuration, and Outbound campaign with its trigger, conditions, and actions for the customer's admin to rebuild in Freshdesk's Rules engine, Freddy Self Service, or Freshdesk Magic. The rebuild scope is a separate engagement or internal admin task.
Intercom two-year conversation history limit applies to API exports
Intercom's API enforces a two-year historical window when retrieving conversations.
How we handle it
Teams with support histories extending beyond two years cannot export older conversations through the REST API. We use date-range filtering to retrieve whatever historical data is accessible and explicitly scope and document how much historical volume falls outside the two-year window so the customer can decide whether to accept the gap or pursue a separate archival approach. This is distinct from Freshdesk's retention policy and is a limitation of the Intercom source API.
How the migration runs
Discovery and scoping
We audit the Intercom workspace across objects: Contact count, Company count, Conversation volume (with date-range analysis to quantify the two-year history gap), Article count with section structure, active Tags, Custom Attribute definitions, and active Admins and Teams.
What this step covers
We audit the Freshdesk destination account for existing Contacts, Organizations, Agents, and Groups to identify conflicts. We document all Intercom automation rules, bots, and Outbound campaigns requiring rebuild inventory. The discovery output is a written migration scope and object inventory.
Schema design and knowledge base restructuring
We design the Freshdesk schema to receive the Intercom data.
What this step covers
This includes creating Freshdesk Custom Fields for each Intercom Custom Attribute (typed correctly as string, number, boolean, date, or picklist), pre-creating Freshdesk Groups to match Intercom Teams, provisioning Freshdesk Agents to match Intercom Admins, and designing the three-level knowledge base structure (Category, Folder, Article) to accommodate Intercom's potentially two-level Collections and Articles. We flag knowledge base articles without parent Sections for customer decision on pre-migration restructuring.
Agent and Group reconciliation
We extract every distinct Intercom Admin and map by email to Freshdesk Agents.
What this step covers
We extract every Intercom Team and map to Freshdesk Groups. Any Freshdesk Agent or Group that does not exist is added to a reconciliation queue for the customer's Freshdesk admin to provision before record migration begins. Migration cannot proceed past this step because ticket assignments and routing rules depend on valid agent and group references.
Contact and Organization migration
We migrate Intercom Contacts to Freshdesk Contacts first, resolving the owner agent_id for each Contact.
What this step covers
We migrate Intercom Companies to Freshdesk Organizations second, preserving the company-contact association. Custom attributes on both objects apply the field-level mapping defined during schema design. Each phase emits a row-count reconciliation report before the next phase begins.
Ticket and conversation migration with API transcript pull
We migrate Intercom Conversations to Freshdesk Tickets using the 1:N merge strategy: conversation subject as ticket subject, first customer message as ticket description, subsequent Parts as Replies or internal Notes.
What this step covers
We pull full transcript content via the Intercom REST API retrieve-conversation endpoint because the S3 export omits transcripts. Freshdesk API per-endpoint sub-limits (Ticket Create and Ticket Update) are enforced with chunking and backoff. Tags apply to the resulting Tickets. We flag any conversations outside the two-year history window that cannot be retrieved via API.
Knowledge base migration with hierarchy flattening
We migrate Intercom Articles into Freshdesk's three-level structure.
What this step covers
Collections map to Freshdesk Categories, Sections map to Folders, and Articles map to Freshdesk Articles. Articles without a parent Section in Intercom are assigned to a default Folder. Article content, title, author, publication state, and translations transfer. We flag article-specific URLs for manual redirect configuration in Freshdesk. The customer reviews the article hierarchy in a staging environment before production migration.
Cutover, delta sync, and automation rebuild handoff
We freeze Intercom writes during cutover, run a final delta migration of any tickets, contacts, or articles modified during the migration window, then enable Freshdesk as the system of record.
What this step covers
We deliver the automation rebuild inventory document listing every Intercom workflow, bot, and Outbound campaign with recommended Freshdesk Rules equivalents. We support a one-week hypercare window for reconciliation issues. We do not rebuild Intercom automations as Freshdesk Rules inside the migration scope; that is a separate engagement or internal admin task.
- 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, knowledge base complexity, and custom field count. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Intercom to Freshdesk →Why teams move from Intercom to Freshdesk
- Intercom's pricing compounds unpredictably with seat additions, Fin AI resolution fees at $0.99 each, and add-ons (Pro at $99/month, Copilot at $29 per agent) that reviewers on Reddit and G2 report as separate charges they did not anticipate until month six. Freshdesk's per-agent flat tiers are more predictable; a team of ten on Pro pays $550/month with Freddy AI included versus the same team on Intercom Advanced at $850/month before a single Fin resolution is counted.
- Freshdesk's ticketing model is more structured and mature for high-volume support operations. SLA policies with escalation rules, collision detection (preventing two agents from responding to the same ticket), round-robin assignment, canned responses, and parent-child ticketing for complex issues are native features. Intercom's conversation-first model lacks these structured ticket management primitives, which reviewers cite as a gap for teams managing formal support SLAs.
- Freshdesk's knowledge base and reporting are built around tickets and response targets rather than conversation metrics. Custom dashboards, SLA tracking by agent and team, resolution time trends, CSAT scores, and slicing by channel, priority, or time period are available without add-ons. Intercom's reporting is built around conversation engagement rather than support KPIs, which teams managing formal SLAs find insufficient for operational visibility.
- Freshdesk's free plan is generous for small teams evaluating a switch, and the Growth plan at $19 per agent is significantly lower entry cost than Intercom's Essential at $29 per seat with no AI features. Teams on Intercom's entry tier report feeling locked into upgrades for basic automation, while Freshdesk includes more features at lower tiers.
- Intercom's Fin AI at $0.99 per resolution creates a billing model where teams are charged more as their automation improves. At 2,000 Fin resolutions per month, that adds $1,980 to the monthly bill. Freshdesk's Freddy AI Agent pricing is included in Pro and significantly lower per-session at comparable volumes, making AI-augmented support more cost-effective at scale.
Questions, answered
Intercom to Freshdesk migration questions
How long does an Intercom to Freshdesk migration take?
Most migrations land between three and five weeks for accounts under 10,000 Contacts and 50,000 Tickets with a simple knowledge base and no custom attributes. Migrations with large conversation histories requiring per-conversation API transcript pulls, multi-section knowledge bases requiring hierarchy restructuring, or Freshdesk plan upgrades for API rate limit headroom move to eight to twelve weeks. Timeline is driven primarily by conversation volume, knowledge base article count, and the customer's availability for schema sign-off and reconciliation.
Do Intercom workflows, bots, and Fin AI configuration migrate to Freshdesk?
No. Intercom workflows, automation rules, custom bots, Outbound campaigns, and Fin AI configuration are workspace-specific and cannot be transferred to Freshdesk or any other platform. We do not migrate them as code. We deliver a written inventory of every active Intercom automation with its trigger, conditions, and actions, and a recommended Freshdesk Rules equivalent or Freddy Self Service configuration. The customer's Freshdesk admin rebuilds the automations post-migration. That rebuild work is outside the migration scope.
Will our Intercom conversation history transfer completely to Freshdesk?
Intercom Conversations transfer as Freshdesk Tickets with full message history. However, Intercom's REST API enforces a two-year conversation history window. Tickets older than two years cannot be retrieved via API and will not appear in Freshdesk. We scope and document the volume of conversations outside the two-year window during discovery so the customer can decide whether to accept the gap or archive older records separately. We pull full transcript content via the per-conversation REST API because Intercom's S3 JSON export deliberately excludes transcripts.
How does the knowledge base migrate when Intercom and Freshdesk have different hierarchy structures?
Intercom allows a two-level structure (Collection > Article) without requiring a Section, but Freshdesk enforces three levels (Category > Folder > Article). We migrate Articles into the three-level structure, assigning Articles without a parent Section to a default Folder we create during migration. This can disrupt navigation and searchability in Freshdesk. We flag which articles will be affected and recommend that customers pre-create a Section structure in Intercom before migration or reorganize articles in Freshdesk post-migration. Article content, translations, author, and publication state transfer regardless of hierarchy mapping.
Can Freshdesk's API rate limits handle a large migration?
Freshdesk's v2 API rate limits are 200 calls per minute on Growth, 400 on Pro, and 700 on Enterprise, with per-endpoint sub-limits (for example, Ticket Create is capped at 80/min on Growth and 280/min on Enterprise). We implement chunking and backoff to stay within these limits. Migrations exceeding the destination plan's rate limit require either upgrading the Freshdesk plan or scheduling migration windows. We assess the rate limit headroom during discovery and flag if a plan upgrade is needed before migration begins.
What happens to Intercom Tags and Segments during migration?
Intercom Tags applied to Contacts and Conversations transfer as Freshdesk Tags on the corresponding Contact or Ticket. Tags transfer as a snapshot at migration time. Intercom Segments (dynamic Contact lists based on attribute rules) do not migrate as active dynamic lists because Freshdesk Smart Groups recompute on query rather than storing membership. We take a snapshot of each segment's Contact membership and create a Freshdesk Static Group with those contacts. The customer documents the filter logic for each segment to rebuild as a Freshdesk Smart Group post-migration.
How do we handle custom attributes and custom fields during migration?
Intercom Custom Attributes on Contacts, Companies, and Tickets are workspace-specific with varying field types. We audit all attribute definitions via Intercom's Data Attributes API during discovery, map each attribute by data type (string, number, boolean, date, select, multi-select) to the equivalent Freshdesk Custom Field type, and create the corresponding Freshdesk field definition before migration begins. Select and multi-select attributes require Freshdesk agent picklist values to be populated. We do not restructure Intercom's attribute schema; we map what exists. Custom Objects (Intercom's user-defined data structures) migrate to Freshdesk via the API if the destination uses Freshdesk Omni (Enterprise tier) with custom object support.
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
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
Get a quote
Moving from Intercom 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