FreshdeskIntercom
Freshdesk to Intercom migration
Migration specialists move your tickets, replies and private notes into Intercom, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 11 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Freshdesk to Intercom at a glance
A Freshdesk to Intercom migration turns tickets into Intercom conversations or tickets, contacts into users or leads, and agents into admins. The hard part is the history: Freshdesk's ticket list returns only 30 days by default. Freshdesk stays live until the final delta sync.
- Objects mapped
- 11
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- Support teams moving from Freshdesk's ticket queues to Intercom's conversational inbox.
- What does not move
- Freshdesk canned responses, scenario automations, dispatch and supervisor rules, SLA policies and portal themes stay behind, listed for your admin to rebuild in Intercom.
- What sets the scope
- The age of your history, ticket and reply volume, how many tickets agents opened themselves, custom field count, and the size of the solution article base.
What moves
What moves from Freshdesk to Intercom
Tickets become Intercom conversations or tickets, contacts become users or leads, agents become admins, and replies and private notes become conversation parts, with solution articles loading as Help Center articles.
- 11 included
| Freshdesk | maps to | Intercom | Status |
|---|---|---|---|
| Contacts | Contacts (user or lead)The role comes from a rule agreed at mapping: customers with an account as users, the rest as leads. | Included | |
| Companies | CompaniesCreated through the API by company_id, since Intercom's CSV import cannot create companies. | Included | |
| Tickets | Conversations, or Intercom ticketsAgreed per group of tickets. The Freshdesk ticket id goes to a data attribute, because Intercom issues its own ids. | Included | |
| Replies | Conversation parts (comments)Customer replies load as contact replies and agent replies as admin replies, each with its original time. | Included | |
| Private notes | Conversation parts (notes)Internal notes for admins, so they never reach the customer. | Included | |
| Status and priority | Conversation or ticket state, and an attributeStatus maps to a state one by one. Priority has no state of its own and becomes an attribute. | Included | |
| Ticket custom fields | Conversation or ticket data attributesCreated first from the approved mapping. | Included | |
| Contact and company custom fields | Contact and company data attributesEach attribute exists in the workspace before a value is sent. | Included | |
| Tags | TagsCreated, then attached to the conversation or contact. | Included | |
| Agents and groups | Admins and teamsAgent replies are written as an admin, so agents are matched first. | Included | |
| Solution categories, folders and articles | Collections, sections and articlesCollections and sections are created first. The author of each article must be a teammate. | Included |
- ContactsContacts (user or lead)
The role comes from a rule agreed at mapping: customers with an account as users, the rest as leads.
- CompaniesCompanies
Created through the API by company_id, since Intercom's CSV import cannot create companies.
- TicketsConversations, or Intercom tickets
Agreed per group of tickets. The Freshdesk ticket id goes to a data attribute, because Intercom issues its own ids.
- RepliesConversation parts (comments)
Customer replies load as contact replies and agent replies as admin replies, each with its original time.
- Private notesConversation parts (notes)
Internal notes for admins, so they never reach the customer.
- Status and priorityConversation or ticket state, and an attribute
Status maps to a state one by one. Priority has no state of its own and becomes an attribute.
- Ticket custom fieldsConversation or ticket data attributes
Created first from the approved mapping.
- Contact and company custom fieldsContact and company data attributes
Each attribute exists in the workspace before a value is sent.
- TagsTags
Created, then attached to the conversation or contact.
- Agents and groupsAdmins and teams
Agent replies are written as an admin, so agents are matched first.
- Solution categories, folders and articlesCollections, sections and articles
Collections and sections are created first. The author of each article must be a teammate.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Freshdesk to Intercom as-is
Canned responses, scenario automations, dispatch and supervisor rules and SLA policies are configuration that Intercom cannot import, so each is documented and rebuilt as macros and Workflows.
- Agent-opened ticketsOn request
- In Intercom: Intercom ticketsIntercom starts a conversation only from a contact, so tickets created by an agent load as Intercom tickets, or follow a convention agreed at mapping.
- On request
- Canned responsesNot migrated
- In Intercom: MacrosRebuilt by hand in Intercom from the text we hand over.
- Not migrated
- Scenario automations, dispatch and supervisor rulesNot migrated
- In Intercom: WorkflowsEach rule is documented with what it does, for your team to rebuild as a Workflow.
- Not migrated
- SLA policies and business hoursNot migrated
- Rebuilt in Intercom by your team. The original ticket dates stay on the records.
- Not migrated
- Portal themes and article URLsNot migrated
- The theme is not moved. Redirects from the old article addresses can be set.
- Not migrated
- Apps and marketplace integrationsNot migrated
- Installed again in Intercom. We hand over the list in use.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Freshdesk to Intercom migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree the date range, how contacts are split into users and leads, which tickets become conversations and which become Intercom tickets, and how agent-opened tickets are handled.
Connect Freshdesk and Intercom
You0.5 dayYou give us a Freshdesk API key and an Intercom access token that can write. We note your Freshdesk plan, since its listing limit sets the speed of the read.
Fields, states and structure
Both1 dayCustom fields to data attributes, statuses to states, categories and folders to collections. The attributes and collections are created before anything else.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, taken from the oldest and newest windows and including the longest threads, loaded into Intercom through a test contact.
You review the sample
You1 dayYour team opens the result in the Intercom inbox and checks reply order, notes, dates, contact roles and that nothing was emailed.
Full load
MigrateX2-3 daysCompanies and contacts first, then conversations and tickets with their replies, then articles, window by window as the Freshdesk history is read.
Delta sync
MigrateX0.5 dayTickets updated in Freshdesk since the full load are brought across and matched on the ticket id kept in a data attribute.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayTicket counts per date window against Freshdesk, tickets against conversations and Intercom tickets, replies against parts, and attachments against files.
Spot checks and sign-off
You1-2 daysYour leads check a random sample, live outbound messages are switched back on, and Freshdesk stays read-only until you agree.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 2 solved
- 4 handled
- 01SolvedMost critical
A plain Freshdesk export quietly drops older history
The problem
Freshdesk returns the last 30 days by default and stops at 30,000 tickets, so an unfiltered pull looks complete while years of tickets are missing.
How we handle it
We pull history in date windows with updated_since, count the tickets in each window against the Freshdesk account, and only load once the counts reconcile. A window that comes back short is read again.
Source: Freshdesk API documentation, checked 13 Nov 2026
- 02Handled
Freshdesk is the slow side of this route
The problem
Freshdesk's lower listing limit and a separate conversations call for every ticket dominate the run, while Intercom accepts far more calls.
How we handle it
Reads run within your Freshdesk plan's limits, and each date window loads as soon as it is read. The scoping call confirms your plan and what it does to the schedule.
Source: Freshdesk support documentation, checked 13 Nov 2026
- 03Handled
Every Freshdesk contact needs a role in Intercom
The problem
Intercom contacts are either users, who have signed up, or leads, who have not. Freshdesk has one kind of contact, so the platform gives no hint which role a requester should get.
How we handle it
A rule decides it with you at mapping: customers with an account load as users and everyone else as leads. The Freshdesk contact id is kept as external_id so the rule can be changed later.
Source: Intercom developer documentation, checked 15 Nov 2026
- 04Solved
Freshdesk ticket numbers do not survive the move
The problem
Intercom issues its own ids for conversations and tickets. Agents and customers who quote an old Freshdesk ticket number would not be able to find the history.
How we handle it
The original Freshdesk ticket id is written to a searchable data attribute, created before the first record loads.
Source: Intercom Help Center, checked 15 Nov 2026
- 05Handled
Loaded contacts can trigger live messages to customers
The problem
Contacts who match the audience of a live outbound message receive it straight away after an import. A requester from three years ago could receive a current campaign the moment the contact is created.
How we handle it
Live outbound messages are paused for the loading window and switched on again after sign-off. Tickets are created with notifications off, and the sample goes through a test contact first.
Source: Intercom Help Center, checked 15 Nov 2026
- 06Handled
Solution articles can only load into collections that already exist
The problem
An Intercom article points at its collection through parent_id, so a collection must exist before its first article. Freshdesk keeps a category, folder and article hierarchy that has to be flattened or rebuilt first.
How we handle it
We map Freshdesk categories and folders onto collections and sections and create them first. Articles then load with a teammate as author, as published or draft to match the source.
Source: Intercom developer documentation, checked 15 Nov 2026
Technical profile
What makes this route technical
Freshdesk hides everything older than 30 days from its default ticket list and paces the read through a lower listing limit, while Intercom needs every attribute, company and collection to exist before its records.
- Exporting from Freshdesk: the ticket list starts 30 days back
- Without a filter, the Freshdesk ticket list returns only tickets created in the past 30 days, and it stops after 300 pages, which is 30,000 tickets. History beyond that is reached with the updated_since filter.
Source: Freshdesk API documentation, checked 13 Nov 2026
- Exporting from Freshdesk: listing has its own budget
- Listing tickets is limited to 40 calls a minute on Growth, 100 on Pro and 200 on Enterprise, below the 100, 400 and 700 that apply to the account as a whole.
Source: Freshdesk support documentation, checked 13 Nov 2026
- Why the Freshdesk list-view export is not a source
- The ticket export from the list view leaves out full conversations and archived tickets. The conversations are read through the API.
Source: Freshdesk support documentation, checked 13 Nov 2026
- Exporting from Freshdesk: replies and notes per ticket
- The replies and notes of a ticket are read from that ticket's conversations endpoint, so a long thread costs several calls on top of the ticket list.
Source: Freshdesk API documentation, checked 13 Nov 2026
- Importing into Intercom: replies accept a time and files
- A reply on behalf of a contact takes created_at, so later customer messages keep their original time. Files go in as up to 10 image URLs, or as base64 attachment_files with a content type, data and name.
Source: Intercom developer documentation, checked 15 Nov 2026
- Importing into Intercom: five ticket states to map onto
- Intercom ticket states are submitted, in progress, waiting on customer, on hold and resolved. A status from another platform must be mapped onto one of them, and tickets can be created with notifications switched off.
Source: Intercom developer documentation, checked 15 Nov 2026
- Importing into Intercom: contacts by CSV
- A contact CSV is limited to 20 MB a file. Rows are matched on the Intercom ID, then user_id, then email, and mixing email and user_id in one file can create duplicates.
Source: Intercom Help Center, checked 15 Nov 2026
- Importing into Intercom: attributes exist before values
- Every custom attribute sent with a company or contact must already exist in the workspace, or the call returns a 400 error. A company is keyed on company_id, which cannot be changed afterwards.
Source: Intercom developer documentation, checked 15 Nov 2026
- Importing into Intercom: an article needs its parent first
- An article is created with an author_id that must be a teammate, a state that defaults to draft, and a parent_id pointing at its collection. The tags on an article are attached with a separate call.
Source: Intercom developer documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Freshdesk and Intercom documentation. Each fact links its source.
Freshdesk to Intercom questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Why does my Freshdesk export only show the last 30 days of tickets?
Because Freshdesk's ticket list returns only tickets created in the past 30 days unless filtered, and stops after 300 pages. We read your full history in date windows and load only when each window's count matches your account.
How do Freshdesk tickets map to Intercom conversations?
Each ticket becomes either an Intercom conversation or an Intercom ticket, chosen per group of tickets at mapping. Conversations suit threads that began as a customer message. Intercom tickets suit tracked work, but they require a ticket type and take a single contact.
Do notes and replies keep their original times in Intercom?
Yes. Each Freshdesk reply and note is written to Intercom with its original created_at. Agent replies are written as an admin, so agents are matched to admins before the load.
What happens to Freshdesk companies and contacts?
Companies are created through the API, since Intercom's CSV import cannot create them, and contacts load next, each linked to its company as a user or a lead by the rule agreed at mapping.
Do Freshdesk solution articles move to the Intercom Help Center?
Yes. Freshdesk categories and folders become Intercom collections and sections, created first, and articles keep their published or draft state with a teammate as author. Article URLs change, and redirects from the old ones can be set.
Can we pick a date range or only open tickets?
Yes. History is read in date windows anyway, so a date range, status or tag can limit what moves, for example open tickets and the last two years first. You choose the filter on the scoping call.
What happens to canned responses and scenario automations?
Not as data. Canned responses are handed over as text to rebuild as Intercom macros, and scenario automations, dispatch and supervisor rules are documented for your admin to recreate as Workflows.
How long does a Freshdesk to Intercom migration take?
About 10 business days end to end, with Freshdesk's ticket listing limit and per-ticket conversation calls setting the pace. Your 100-record sample shows the real rate.
What does a Freshdesk to Intercom migration cost?
The price is set by what moves: tickets with their replies and notes, attachments, contacts, companies, custom fields and the solution article base. After the free sample of 100 of your records, a fixed quote follows within 24 hours.
How it compares
Four ways to run Freshdesk to Intercom
The same data, moved four different ways. This is what changes between them.
Object coverage (cases, emails, comments, files, Knowledge)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Linked records, files and knowledge often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Public replies vs internal notes
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the Intercom cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your Intercom move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
