IntercomFreshdesk

Intercom to Freshdesk migration

Migration specialists move your conversations, messages and internal notes into Freshdesk, check a sample with you first, and count every record on both sides.

Scope my migration

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
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Intercom to Freshdesk at a glance

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.

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 Intercom's chat-first inbox to Freshdesk's ticket queues, groups and automation rules.
What does not move
Intercom Workflows, Series, bots, Fin AI Agent configuration, macros and reports stay behind, listed for your admin to rebuild in Freshdesk.
What sets the scope
Conversations per contact, your Freshdesk plan and its ticket creation cap, attachment volume, contacts without an email, and Help Center size.

What moves

What moves from Intercom to Freshdesk

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.

  • 11 included
IntercomFreshdesk
  • Contacts (users and leads)Contacts

    Matched on email before any ticket loads. Contacts without an email follow the rule agreed at mapping.

  • CompaniesCompanies

    Loaded before contacts, so each contact is linked to its company.

  • ConversationsTickets

    One ticket per conversation. Whether short chats from the same contact are grouped is scoped during the free sample.

  • MessagesReplies

    Customer messages arrive as incoming replies and teammate messages as outgoing replies, in order.

  • Internal notesPrivate notes

    Notes between teammates stay private.

  • Tickets (Customer category)Tickets

    The ticket type becomes a Freshdesk ticket type or a tag.

  • Ticket statesTicket statuses

    Mapped one by one onto your Freshdesk statuses.

  • TagsTags

    Applied to the ticket.

  • Data attributesContact, company and ticket custom fields

    Fields are created first, then values load.

  • Admins and teamsAgents and groups

    Admins are matched to agents by email.

  • Articles and collectionsSolution articles, folders and categories

    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

What does not move from Intercom to Freshdesk as-is

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.

Back-office and Tracker ticketsOn request
In Freshdesk: TicketsInternal-only tickets, agreed per account.
Messages from bots, Fin AI Agent and assignmentsOn request
In Freshdesk: Private notesKept as text in a private note on request. Otherwise they are left out of the ticket.
MacrosNot migrated
In Freshdesk: Canned responsesExported from Intercom as text and rebuilt by hand as canned responses.
Workflows, Series and botsNot migrated
In Freshdesk: Automation rulesIntercom says workflows cannot be transferred. They are listed and rebuilt as Freshdesk automation rules.
Assignment rules, Inbox views and reportsNot migrated
Configuration, rebuilt in Freshdesk from the list we hand over.
Fin AI Agent configuration, apps and Messenger settingsNot migrated
Set up again by your team. SLA definitions in Intercom are rebuilt as Freshdesk SLA policies.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Intercom to Freshdesk migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      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

      You0.5 day

      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

      Both1 day

      Data attributes to contact, company and ticket fields, Intercom ticket states to Freshdesk statuses, and teams to groups. Your admin approves the mapping.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      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

      You1 day

      Your agents open the tickets, check reply order, private notes, requesters and dates, and confirm no automation emailed a customer.

    • Full load

      MigrateX2-3 days

      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

      MigrateX0.5 day

      Conversations updated in Intercom since the full load are brought across and matched on the conversation id, so nothing is created twice.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      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

      You1-2 days

      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

Every known risk on this route, with how we handle it

  • 2 solved
  • 4 handled
  1. 01HandledMost critical

    Freshdesk's ticket creation cap sets the length of the run

    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

  2. 02Handled

    A busy Intercom thread can carry more files than one ticket holds

    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

  3. 03Solved

    Leads without an email can merge into one Freshdesk contact

    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

  4. 04Handled

    A long Intercom thread arrives without its oldest messages

    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

  5. 05Solved

    The Intercom workspace is the only copy of the message text

    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

  6. 06Handled

    Back-office and Tracker tickets have no customer-facing meaning in Freshdesk

    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

What makes this route technical

Freshdesk caps ticket creation per minute and attachments at 20 MB a ticket, while Intercom's own exports carry metadata and no message text.

Exporting from Intercom: CSV exports hold metadata only
Intercom's CSV exports carry reporting metadata, such as conversation ids, timestamps, attributes and metrics, but no message content.

Source: Intercom Help Center, checked 15 Nov 2026

Exporting from Intercom: cursor paging, 150 a page
Conversation, contact and ticket lists use cursor pagination with starting_after and return at most 150 records a page. The defaults are 20 for conversations and 10 for the contacts list.

Source: Intercom developer documentation, checked 15 Nov 2026

Exporting from Intercom: tickets by ticket type
Tickets are read through the Tickets API: first list the ticket types, then request each ticket type or ticket id. The tickets CSV from Dataset export is capped at 10,000 rows in the browser.

Source: Intercom Help Center, checked 15 Nov 2026

Exporting from Intercom: far more headroom than Freshdesk
Intercom allows private apps 10,000 calls a minute per workspace, far above Freshdesk's ticket creation cap, so Freshdesk sets the pace.

Source: Intercom developer documentation, checked 15 Nov 2026

Exporting from Intercom: file sizes
Intercom accepts attachments up to 100 MB each on Messenger uploads, while incoming email is capped at 20 MB including its attachments. A single Intercom file can therefore be larger than a whole Freshdesk ticket allows.

Source: Intercom Help Center, checked 15 Nov 2026

Importing into Freshdesk: calls a minute by plan
Freshdesk allows 100 API calls a minute on Growth, 400 on Pro and 700 on Enterprise. The allowance covers the whole account, so every integration in it draws from the same budget.

Source: Freshdesk support documentation, checked 13 Nov 2026

Importing into Freshdesk: ticket creation is capped lower
Creating tickets is limited to 50 a minute on Growth, 160 on Pro and 280 on Enterprise. Replies and notes are further calls on top of the ticket itself.

Source: Freshdesk support documentation, checked 13 Nov 2026

Importing into Freshdesk: 20 MB of attachments a ticket
The attachments on one Freshdesk ticket together cannot exceed 20 MB.

Source: Freshdesk API documentation, checked 13 Nov 2026

Importing into Freshdesk: contact email is unique
Each Freshdesk contact has a unique email address. Creating a ticket for an email Freshdesk does not know creates a new contact on the spot.

Source: Freshdesk API documentation, checked 13 Nov 2026

Facts checked 15 Nov 2026 against Intercom and Freshdesk documentation. Each fact links its source.

Intercom to Freshdesk questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do I migrate from Intercom to Freshdesk?

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.

Do Intercom conversations become Freshdesk tickets with all replies?

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.

What happens to Intercom contacts with no email?

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.

Does the Intercom Help Center move into Freshdesk solution articles?

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.

Will Intercom tags and custom attributes carry over?

Yes. Tags go onto the Freshdesk tickets, and data attributes become contact, company and ticket custom fields, created before the first value loads.

Is there a limit on tickets per minute in Freshdesk?

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.

What about large attachments?

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.

How long does an Intercom to Freshdesk migration take?

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.

What does an Intercom to Freshdesk migration cost?

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

Four ways to run Intercom to Freshdesk

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 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.

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.

Guides

Guides for an Intercom to Freshdesk migration

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    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 Freshdesk move with 100 of your records.

Scope my migration

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