Freshservice to Intercom migration, customer support out of the service desk
Freshservice to Intercom is a migration our team plans and runs for you, with the mapping agreed in writing before anything moves.
Last updated
This page is about moving customer-facing support from Freshservice to Intercom while IT keeps its service desk. Freshservice tickets become Intercom conversations or tickets with their replies and notes, requesters become contacts and solution articles become Help Center articles. Links to assets, problems and changes have no Intercom counterpart and are agreed on the call. Our team plans and runs this route, with the mapping agreed in writing first.
What moves
How Freshservice records map to Intercom
| Freshservice | Intercom | How |
|---|---|---|
| Requesters | Contacts | Matched on a field agreed in the mapping, usually email. |
| Tickets | Conversations or tickets | Each customer-facing ticket becomes an Intercom conversation or a ticket of the type you choose. |
| Replies | Conversation replies | Freshservice's API lists every conversation on a ticket, so replies travel in order. |
| Notes | Internal notes | Private notes stay internal in Intercom. |
| Attachments | Attachments on the same message | Files travel with the message they belong to. |
| Ticket fields | Conversation or ticket attributes | Mapped field by field, agreed in writing. |
| Solution articles | Help Center articles | Freshservice solution articles become Intercom Help Center articles. |
Why teams make this move
Teams that ran customer-facing support inside Freshservice move it to Intercom for the Messenger and Fin AI Agent, while IT keeps its own service desk.
The tricky part on this route
Freshservice is built for IT service management, so a ticket can be linked to assets, problems and changes that have no counterpart in Intercom. Requester replies and private notes move as Intercom conversations or tickets, and the ITSM links are kept as attributes or left behind on a list agreed before the full run.
We agree how to handle it with you in the written mapping, before anything moves.
What doesn’t move
What stays behind in Freshservice, and why.
Some of what Freshservice holds has no place in Intercom. Here is what each vendor documents, and what we settle with you on the call.
| Freshservice | Outcome | Why |
|---|---|---|
| Assets, problems and changes | Check on the call | They have no Intercom counterpart; links to them are agreed on the call. |
| Workflow Automator, canned responses, agent groups and SLA policies | Rebuilt in Intercom | Configuration, not data: rebuilt in Intercom. |
Automations, macros and views are settings, not data, so they are set up again in Intercom.
Before you start: what to switch off and set up in Intercom
- Switch off customer email notifications in Intercom for the move: Intercom documents that customers get notifications on migrated email conversations unless they are suppressed.
- Add a ‘Created via API’ exception to live workflows, or turn them off, so they do not act on old conversations.
- Allow the attachment file types your history holds (Settings > Workspace > Security > Attachments), or Intercom refuses files outside its default list.
- Create teammates and teams in Intercom first: Intercom’s API cannot create them.
- Decide which Freshservice workspaces or groups hold customer-facing tickets.
Full checklist: Helpdesk migration checklist
How it runs
How our team runs a Freshservice to Intercom migration.
- 01
Scoping call
What moves, what stays, and your dates.
- 02
Written mapping
Every field and value agreed before anything moves.
- 03
The move
Our team runs it.
- 04
Hand-back
We walk you through what arrived and what you set up again in Intercom.
How a migration works · Security and data handling · Pricing · Talk to us about Freshservice to Intercom
Questions
Questions about moving from Freshservice to Intercom.
What happens to asset and change links?
Assets, problems and changes have no Intercom counterpart, so how links to them are kept is agreed on the scoping call.
Does Intercom import from Freshservice?
Intercom's content sync sources include Freshdesk, not Freshservice, and no Freshservice ticket importer is documented.
How fast can data come out of Freshservice?
Freshservice allows 100 API calls a minute on Starter, 200 on Growth, 400 on Pro and 500 on Enterprise, with lower caps on listing and viewing tickets.
What does not carry across from Freshservice?
Automations, macros and views are settings, not data, so they are set up again in Intercom. Anything with no place in Intercom is named in the written mapping before the move.
Who runs a Freshservice to Intercom migration?
Our migration team. Freshservice to Intercom is not a self-serve route on the DataGrine platform, so we plan it with you on a call, agree the mapping in writing, run the move and hand it back.
What does it cost?
It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.
Related reading