
Intercom Alternatives After the Salesforce Deal: 6 Options Compared
11 min read
IntercomFreshdesk
Migration specialists move your conversations, messages and internal notes into Freshdesk, 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
An Intercom to Freshdesk migration turns conversations into tickets, admins into agents and teams into groups. The hard part is the pace, set by Freshdesk's per-minute cap on ticket creation. Intercom stays live until the final delta sync.
What moves
Conversations become Freshdesk tickets, contacts and companies move across, customer messages arrive as incoming replies and internal notes as private notes, and Help Center articles become solution articles.
| Intercom | maps to | Freshdesk | Status |
|---|---|---|---|
| Contacts (users and leads) | ContactsMatched on email before any ticket loads. Contacts without an email follow the rule agreed at mapping. | Included | |
| Companies | CompaniesLoaded before contacts, so each contact is linked to its company. | Included | |
| Conversations | TicketsOne ticket per conversation. Whether short chats from the same contact are grouped is scoped during the free sample. | Included | |
| Messages | RepliesCustomer messages arrive as incoming replies and teammate messages as outgoing replies, in order. | Included | |
| Internal notes | Private notesNotes between teammates stay private. | Included | |
| Tickets (Customer category) | TicketsThe ticket type becomes a Freshdesk ticket type or a tag. | Included | |
| Ticket states | Ticket statusesMapped one by one onto your Freshdesk statuses. | Included | |
| Tags | TagsApplied to the ticket. | Included | |
| Data attributes | Contact, company and ticket custom fieldsFields are created first, then values load. | Included | |
| Admins and teams | Agents and groupsAdmins are matched to agents by email. | Included | |
| Articles and collections | Solution articles, folders and categoriesThe hierarchy is mapped to category, folder and article, and the structure is created before the articles. | Included |
Matched on email before any ticket loads. Contacts without an email follow the rule agreed at mapping.
Loaded before contacts, so each contact is linked to its company.
One ticket per conversation. Whether short chats from the same contact are grouped is scoped during the free sample.
Customer messages arrive as incoming replies and teammate messages as outgoing replies, in order.
Notes between teammates stay private.
The ticket type becomes a Freshdesk ticket type or a tag.
Mapped one by one onto your Freshdesk statuses.
Applied to the ticket.
Fields are created first, then values load.
Admins are matched to agents by email.
The hierarchy is mapped to category, folder and article, and the structure is created before the articles.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
Workflows, Series, bots, macros and Inbox views are configuration that Freshdesk cannot import, so each is documented and rebuilt as automation rules and canned responses.
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Estimated total
About 10 business days
end to end
Day 1-2
Scoping call
We look at conversations per contact, agree the rule for contacts without an email and for short chats, and decide which ticket types and date range move.
Connect and read your Freshdesk plan
You give us an Intercom access token with read access and a Freshdesk API key. We note the plan, because its caps decide how long the load runs.
Field and status review
Data attributes to contact, company and ticket fields, Intercom ticket states to Freshdesk statuses, and teams to groups. Your admin approves the mapping.
Day 3-7
Free sample
100 of your records, picked for the busiest contacts, the biggest attachments and the most internal notes, loaded into Freshdesk end to end.
You review the sample
Your agents open the tickets, check reply order, private notes, requesters and dates, and confirm no automation emailed a customer.
Full load
Companies and contacts first, then tickets with their replies and notes, then the solution articles, held to the ticket creation cap of your plan.
Delta sync
Conversations updated in Intercom since the full load are brought across and matched on the conversation id, so nothing is created twice.
Day 8-10
Reconciliation report
Conversations against tickets by state and year, parts against replies and notes, files against attachments, and every file moved to your own storage.
Spot checks and sign-off
Your leads check a random sample, the paused automation rules go back on, and Intercom stays active and 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
The problem
On Growth, Freshdesk creates 50 tickets a minute, so 10,000 conversations need at least 200 minutes before a single reply or note is counted. Each reply is another call against the same account allowance.
How we handle it
We read your Freshdesk plan at scoping and schedule the load against its caps. The free sample confirms the real rate.
Source: Freshdesk support documentation, checked 13 Nov 2026
The problem
A Messenger upload can be as large as 100 MB, and one Intercom conversation can hold several. Freshdesk stops at 20 MB of attachments for the whole ticket.
How we handle it
Every file is sized during the read. Files that would push a ticket past 20 MB go to storage you own and are linked in a private note on the ticket.
Source: Intercom Help Center, checked 15 Nov 2026
The problem
Freshdesk identifies a contact by email. Intercom leads and visitors who never gave one could be folded into a single Freshdesk contact.
How we handle it
At mapping you decide whether those conversations load under a placeholder contact or are left out, and the free sample tests the choice. Contacts with an email are matched before any ticket is created.
Source: Freshdesk API documentation, checked 13 Nov 2026
The problem
One conversation request returns only the 500 most recent parts. Without a second read, a long thread would reach Freshdesk with its first messages missing.
How we handle it
A conversation that returns a full 500 parts is requested again with page and per_page, oldest part first, so the Freshdesk ticket opens with the original message.
Source: Intercom developer documentation, checked 15 Nov 2026
The problem
Intercom's S3 export holds no transcript and its CSV files hold metadata, so closing the workspace too early leaves no other copy of the old messages.
How we handle it
The Intercom workspace stays active until you sign off the reconciliation report. You decide when to close it after that.
Source: Intercom Help Center, checked 15 Nov 2026
The problem
Intercom ticket types come in three categories. Tracker tickets are internal only and never shared with customers, and Back-office tickets are not customer tickets either, so a plain copy would mix them into the support queue.
How we handle it
Customer tickets move by default. Back-office and Tracker tickets are scoped per account during the free sample.
Source: Intercom Help Center, checked 15 Nov 2026
Technical profile
Freshdesk caps ticket creation per minute and attachments at 20 MB a ticket, while Intercom's own exports carry metadata and no message text.
Source: Intercom Help Center, checked 15 Nov 2026
Source: Intercom developer documentation, checked 15 Nov 2026
Source: Intercom Help Center, checked 15 Nov 2026
Source: Intercom developer documentation, checked 15 Nov 2026
Source: Intercom Help Center, checked 15 Nov 2026
Source: Freshdesk support documentation, checked 13 Nov 2026
Source: Freshdesk support documentation, checked 13 Nov 2026
Source: Freshdesk API documentation, checked 13 Nov 2026
Source: Freshdesk API documentation, checked 13 Nov 2026
Facts checked 15 Nov 2026 against Intercom and Freshdesk documentation. Each fact links its source.
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Companies and contacts load first, then each Intercom conversation is read through the API and created as a Freshdesk ticket with its replies and private notes, because Intercom's CSV exports hold no message text. A delta sync and a reconciliation report close the move.
Yes. Each Intercom conversation becomes one Freshdesk ticket, with customer messages as incoming replies, teammate messages as outgoing replies and internal notes as private notes, in the original order. Bot and Fin AI Agent messages follow the rule you set at mapping.
They follow a rule you choose at mapping, a placeholder contact or leaving those conversations out, because Freshdesk identifies each contact by a unique email.
Yes. Intercom collections and sections become Freshdesk solution categories and folders, created first, and the articles load into them. Old article addresses will not resolve in Freshdesk, and redirects are scoped with you during the free sample.
Yes. Tags go onto the Freshdesk tickets, and data attributes become contact, company and ticket custom fields, created before the first value loads.
Yes. Freshdesk caps ticket creation at 50 a minute on Growth, 160 on Pro and 280 on Enterprise, for the whole account, below its general call limit. That cap sets the length of the load.
Freshdesk allows 20 MB of attachments per ticket in total, and one Intercom Messenger file can be 100 MB. Files that would push a ticket over the cap go to storage you own, linked in a private note.
About 10 business days end to end. The load is paced by Freshdesk's ticket creation cap for your plan, and the free sample measures the real pace.
The price is set by what moves: conversations and the messages and files in each, tickets, contacts, companies and the size of your Help Center. We send a fixed quote within 24 hours of the scoping call, once 100 of your records have been migrated free as a sample.
How it compares
The same data, moved four different ways. This is what changes between them.
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.
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.
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the Freshdesk 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.
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.
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.
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.
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.
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.
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.
Guides
Related routes
Independently audited controls over how we handle your data.
Data processing agreement available.
Business associate agreement available.

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.