Freshservice to Intercom migration
We migrate Tickets, Agents, Requesters, and Knowledge Base content from Freshservice into Intercom's Conversational Support model, handling the structural shift from ITSM ticket queues to customer-facing conversation threads and resolving attachment re-upload dependencies before any records move.
FlitStack AI migrates conversations, admin or teammates, contacts, custom attributes on contacts and contact note or external documents from Freshservice 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: 3-5 weeks.

What moves from Freshservice to Intercom?
Moving from Freshservice to Intercom is not a like-for-like platform swap — it is a migration from an ITSM model (IT teams managing internal employee tickets) to a Conversational Support model (customer-facing support teams managing buyer and user conversations).
Read the full summary
Freshservice Tickets map to Intercom Conversations, but the routing, SLA, and change-management semantics of ITSM have no Intercom equivalents. We migrate Tickets with their full reply threads, Agents as Intercom Admins and Teammates, Requesters as Contacts, and Knowledge Base Solutions as Help Center Articles. Freshservice Assets and Changes — ITIL-native objects — do not have structural counterparts in Intercom and are documented as manual inventory items post-migration. Workflows, SLA Policies, and Automation Rules do not migrate; we deliver a written inventory of these for your team to rebuild in Intercom's workflow builder. Attachment handling requires a multi-step process: Freshservice attachment URLs expire and require re-authentication, so we download each binary to memory, upload to Intercom via multipart/form-data, and reference the returned upload ID in the conversation record. Parent-child ticket relationships in Freshservice can cause migration errors when the dependency chain is incomplete, which we resolve by ordering parent records before child records and validating the hierarchy before cutover.
Ticket → Conversation
Freshservice Tickets map to Intercom Conversations.
How it maps
The ticket subject maps to the conversation title; description maps to the first message part. Replies, notes (internal notes map to Intercom admin notes), and attachments map as conversation parts in chronological order. Ticket status (Open, Pending, Resolved, Closed) maps to Intercom state (open, resolved, closed). Agent and group assignments map to conversation assignee and team inbox. Priority and ticket type are stored as custom attributes on the conversation.
Agent → Admin or Teammate
Freshservice Agents map to Intercom Admins (full workspace access) or Teammates (conversation handling access).
How it maps
We resolve by matching email addresses. Role (Agent, Topic Manager, Admin) in Freshservice maps to Intercom permission levels. Group memberships in Freshservice map to Intercom team membership, which controls inbox routing. If the destination Intercom workspace has fewer seats than the agent count, we flag the discrepancy during scoping so the customer can provision additional seats before migration.
Requester → Contact
Freshservice Requesters map to Intercom Contacts.
How it maps
Contact name, email, phone, and organization associations migrate directly. Custom fields on the requester record migrate as custom attributes on the Intercom Contact. Requesters who are also Agents in Freshservice create both a Contact and an Admin record in Intercom; we use email as the dedupe key to avoid duplicate records.
Asset → Custom Attributes on Contact
Freshservice Assets (hardware, software, network items tracked in the CMDB) have no native Intercom equivalent.
How it maps
We handle this as a configuration decision during scoping: assets can be stored as custom attributes on the related Contact record (linked by the ticket's requester), or preserved as a separate CSV inventory in the migration report. For organizations that need to retain full asset context, we recommend a separate asset management tool post-migration.
Change → Contact Note or External Document
Freshservice Changes (planned modifications with risk level, approvers, and associated CIs) have no structural counterpart in Intercom.
How it maps
We flag Changes during pre-migration discovery and migrate them as Contact Notes or as a structured CSV in the migration report. The linkage to related Tickets is preserved as a text field containing the Freshservice change ID for manual cross-reference.
Problem → Contact Note or External Document
Freshservice Problems track root-cause analysis behind one or more incidents.
How it maps
Intercom has no native problem management object. We migrate Problem records as notes on the primary affected Contact, with a link back to the related conversation IDs. This preserves the relationship for audit purposes without forcing an unnatural schema fit.
- TicketConversation1:1
- AgentAdmin or Teammate1:1
- RequesterContact1:1
- AssetCustom Attributes on Contacttransformed
- ChangeContact Note or External Documenttransformed
- ProblemContact Note or External Documenttransformed
+ 5 more in the mapping below
How Freshservice 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 | Freshservice | Intercom |
|---|---|---|
| Primary use case | ITSM for internal IT teams managing employee requests | Customer-facing conversational support for buyers and product users |
| Ticket model | Ticket with status, priority, type, group, agent, and optional child tickets | Conversation with message parts, state, assignee, and topic |
| Agent model | Licensed IT agents (agent-based pricing) plus free requesters | Seats (admins and teammates) who handle conversations |
| Routing | Group-based routing, escalation rules, and change workflows | Inbox assignment rules, saved replies, and Fin AI automation |
| Asset management | Full CMDB with asset discovery, lifecycle tracking, and CI relationships | No native asset management; assets as custom attributes or external tool |
| Change management | Changes, Releases, and Problems with risk levels and approval chains | No change or release management objects; support-focused only |
| Knowledge base | Solutions organized by Category, Folder, and Article | Help Center with Collections, Sections, and Articles with translations |
What to watch for in a Freshservice to Intercom migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Freshservice attachment URLs expire and require re-upload
Freshservice attachment URLs require authentication and expire after a configurable period.
How we handle it
We cannot reference the original URL from within Intercom. We download each binary to memory during migration, upload it to Intercom via multipart/form-data POST, and reference the returned upload ID in the conversation part. Inline images in HTML ticket bodies are parsed, downloaded, and replaced with Intercom-hosted URLs. This multi-step handling adds latency for migrations with high attachment-per-ticket ratios, and we flag the attachment volume during scoping so the customer can decide whether to migrate attachments or defer them to a separate pass.
Parent-child ticket relationships require ordered migration
Freshservice parent-child ticket hierarchies can cause migration failures when the child ticket references a parent ticket that has not yet been created in Intercom.
How we handle it
The Freshservice API returns ticket dependencies we resolve during the transform phase, ordering parent records before child records and validating that the parent conversation_id is present before inserting the child. We run a hierarchy validation pass before cutover to catch any orphaned child tickets and resolve them by creating parent placeholder conversations first.
Help Center migration requires manual URL rewrites
Freshservice Solutions and Intercom Help Center use different URL structures.
How we handle it
Article URLs in Freshservice follow a category/folder/article path; Intercom uses a collection/section/article path. We rewrite URLs during migration but Intercom does not support automated redirects, so any links embedded in migrated emails, macros, or external documentation will break. We deliver a URL map document alongside the migration report so the customer's team can set up redirects or update links post-migration.
Freshservice API rate limits vary by plan and must be requested upfront
Freshservice applies per-minute API rate limits that scale by plan tier: Growth around 200 calls per minute, Pro around 400, and Enterprise around 700.
How we handle it
During large migrations, these limits constrain throughput and extend timelines. We request elevated limits through Freshservice's migration partner process before migration begins. If the API returns 429 responses, we back off with exponential delay. Not requesting the limit increase upfront is a common cause of migration timeline overruns, and we flag this as a pre-migration action in our discovery call.
Workflows, SLA Policies, and Automation Rules do not migrate
Freshservice workflows, escalation rules, SLA Policies, and automation rules are ITSM-process configurations that do not map to Intercom's conversational automation model.
How we handle it
Intercom uses different primitives (Inbox Rules, Fin AI workflows, saved replies, macros) that require manual redesign rather than direct migration. We deliver a written inventory of every active Freshservice automation with its trigger, conditions, and a recommended Intercom equivalent, and the customer's team rebuilds them post-migration.
How the migration runs
Discovery and object mapping design
We audit the Freshservice portal across plan tier, agent count, ticket volume, attachment ratio, parent-child ticket prevalence, custom fields, and Knowledge Base article count.
What this step covers
We pair this with an Intercom workspace audit: seat count, existing collections, custom attributes already defined, and workflow configuration. The discovery output is a written migration scope document with the object mapping table, a list of Freshservice objects that have no Intercom equivalent (documented for manual handling), and the attachment handling strategy. We also confirm the Intercom API rate limit of 1,000 requests per minute (distributed as 166 per 10-second window) and reconcile it against the Freshservice export rate.
Attachment strategy and Help Center parent mapping
We establish the attachment handling approach: either full attachment migration (with the download-reupload process), or attachment metadata only (leaving binaries for a separate migration pass).
What this step covers
We also map Freshservice Solution categories to Intercom Help Center collections during this phase, as the parent-child structure differs between platforms. We validate that any custom fields in Freshservice have corresponding custom attribute definitions in Intercom before migration begins; Intercom requires custom attributes to be pre-defined via the dashboard or API before data can be written to them.
Test migration and hierarchy validation
We run a test migration using a representative sample (typically 50-100 tickets, 20-50 contacts, 10-20 articles) into a staging environment or shadow workspace.
What this step covers
We validate that parent-child ticket hierarchies resolve correctly, that attachment upload IDs attach to the correct conversation parts, and that Help Center article URLs map to the correct collection structure. The customer reviews the sample records against the source Freshservice data and signs off before production migration begins. Any mapping corrections happen at this stage.
Production migration in dependency order
We run production migration in record-dependency order: Admins and Teammates first (Intercom requires admins to exist before conversations can be assigned), Contacts next (Intercom requires contacts to exist before conversation parts can reference them), Conversations and conversation parts in chronological order, custom attributes populated after their parent records are confirmed, and Help Center Collections, Sections, and Articles last.
What this step covers
We batch conversations by month to manage the Intercom API rate limit and maintain thread integrity. Parent-child ticket pairs are inserted as a unit with the parent conversation created first.
Cutover, validation, and inventory handoff
We freeze Freshservice writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Intercom as the system of record.
What this step covers
We deliver the full migration report including the URL map for Help Center articles, the CSV inventory of Changes, Problems, and Releases with no Intercom equivalent, the automation inventory with Intercom equivalents, and a row-count reconciliation showing record counts by object type. We do not rebuild Freshservice workflows, SLA Policies, or escalation rules in Intercom; those are documented for your team to rebuild in Intercom's workflow builder.
- 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, attachment count, and the complexity of the Knowledge Base migration. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Freshservice to Intercom →Why teams move from Freshservice to Intercom
- Freshservice built Freddy AI as a paid add-on rather than a platform-included feature, which triggered churn among teams that purchased expecting AI triage to be included at their tier. Intercom's Fin AI Agent is built into Pro and Premium tiers and handles conversation resolution with no per-resolution surcharge at higher conversation volumes.
- Freshservice's child ticket reporting and dashboard performance degrade under large ticket volumes, forcing teams to export to BI tools for cross-ticket views. Intercom's conversation timeline and reporting provide real-time visibility into resolution times, first-response metrics, and conversation volume without requiring external tooling.
- Intercom's in-app messenger and proactive outbound messaging support product-led growth models that Freshservice's internal ITSM framing cannot serve. Customer support teams running product-led SaaS companies migrate to Intercom because the messenger lives inside the product, enabling contextual support without forcing users into a separate portal.
- Custom Objects in Freshservice are gated behind Forest and Enterprise plans and cannot define associations to native objects like Tickets or Assets, limiting their practical utility for complex ITSM data models. Intercom's custom attributes on Contacts and Conversations are available at all paid tiers and support flexible data capture without plan-tier restrictions.
Questions, answered
Freshservice to Intercom migration questions
How long does a Freshservice to Intercom migration take?
Straightforward migrations under 20,000 Tickets, 5,000 Contacts, and 500 Help Center articles with manageable attachment volumes land in three to five weeks. Migrations with high attachment-per-ticket ratios, multi-language Help Centers, parent-child ticket hierarchies, or large asset inventories requiring manual documentation move to seven to eleven weeks because of the attachment re-upload process, the Help Center parent mapping work, and the hierarchy validation pass.
Do Freshservice workflows, SLA Policies, and escalation rules migrate to Intercom?
No. Freshservice workflows, escalation rules, SLA Policies, and automation rules are ITSM-process configurations that do not have structural equivalents in Intercom's conversational model. We do not migrate them as code. We deliver a written inventory of every active Freshservice automation with its trigger conditions, targets, and a recommended Intercom equivalent (Inbox Rules, Fin AI workflows, or saved replies). Your team rebuilds them in Intercom's workflow builder post-migration. Service Catalog approval chains also do not migrate; these require redesign in Intercom Forms or an external intake tool.
What happens to Freshservice Assets, Changes, and Problems?
Freshservice Assets, Changes, and Problems are ITSM-native objects with no Intercom equivalents. Assets can be stored as custom attributes on Contact records (linked by ticket requester) or preserved as a structured CSV in the migration report for import into a dedicated asset management tool. Changes and Problems migrate as structured CSVs in the migration report, preserving title, status, linked ticket IDs, risk level, and approval information. The customer references these post-migration for audit and compliance documentation.
Do historical conversation attachments migrate?
Yes, with a multi-step process. Freshservice attachment URLs expire and require authentication, so we download each binary to memory, upload it to Intercom via multipart/form-data POST, and reference the returned upload ID in the conversation part. Inline images in HTML ticket bodies are parsed, downloaded, and replaced with Intercom-hosted URLs. This process adds latency for migrations with high attachment-per-ticket ratios. During scoping, we report the attachment volume and attachment ratio so you can decide whether to migrate all attachments or handle them in a separate pass.
How do we handle the Freshservice Knowledge Base migration?
Freshservice Solutions (Knowledge Base articles organized by Category and Folder) map to Intercom Help Center Articles within Collections and Sections. Article titles, body content with formatting, attachments, and tags migrate. The Freshservice category structure maps to Intercom collection structure during scoping, but the parent-child organization differs and requires a manual parent mapping. Article URLs are rewritten during migration but Intercom does not support automated redirects, so we deliver a URL map document so your team can set up redirects or update embedded links post-migration.
Can FlitStack AI migrate Freshservice Custom Objects to Intercom?
Freshservice Custom Objects (available on Forest and Enterprise plans) store structured data beyond standard fields, but Freshservice does not support creating relationships between Custom Object records and native objects like Tickets. Intercom stores custom data as attributes on Contacts and Conversations rather than as separate custom objects. We can migrate Custom Object records as custom attributes on the relevant Contact or Conversation, or preserve them as a structured CSV in the migration report for import into a dedicated database or custom object tool. The mapping strategy is decided during scoping based on how the customer uses Custom Objects.
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
- Historical data migration to Intercom — Intercom Help
- Data hosting and residency — Intercom Help
- Setting up a Custom Object — Intercom Help
Get a quote
Moving from Freshservice 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