Intercom Alternatives After the Salesforce Deal: 6 Options Compared
Six Intercom alternatives after the Salesforce deal, compared on how conversations, notes, contacts and articles land in each, from vendor docs.
Published 11 min read

On this page
- What changed at Intercom in 2026?
- How do the six Intercom alternatives compare?
- 1. Zendesk
- 2. Freshdesk
- 3. HubSpot Service Hub
- 4. Gorgias
- 5. Salesforce Service Cloud
- 6. Stay on Intercom
- How do you choose between them?
- Intercom alternatives FAQ
- See your Intercom conversations in the platform you are considering
Teams looking at Intercom alternatives after the Salesforce deal have six realistic options: Zendesk, Freshdesk, HubSpot Service Hub, Gorgias, Salesforce Service Cloud, or staying on Intercom. Zendesk, Freshdesk and Gorgias keep each conversation as one ticket. HubSpot keeps it as a ticket with timeline activities, and Service Cloud splits it into a Case, emails and feed posts.
This comparison is for support leaders deciding where their Intercom history should live. Every option gets the same fact card, built from the vendor's own documentation as of November 2026. It does not rank them.
What changed at Intercom in 2026?
The company changed its name and its owner. The platform kept its name. Three dated announcements are the whole story.
- 12 May 2026: the company behind Intercom renamed itself Fin. Its announcement says "Intercom will live on as our customer service software platform, but Fin is our future".
- 15 June 2026: Salesforce announced it had signed a definitive agreement to acquire Fin, formerly Intercom, for approximately $3.6 billion.
- 10 September 2026: Salesforce announced it had completed the acquisition. The press release says "as part of Salesforce's AI Labs, Fin will continue to serve its customers".
Nothing in those announcements tells a customer to move, and this post makes no prediction beyond them.
How do the six Intercom alternatives compare?
The table shows where each part of an Intercom workspace lands, as of November 2026. The cards below give the vendor documentation behind every cell.
| Option | Suits | An Intercom conversation becomes | Internal notes become | Companies become | Help Center articles | Original dates |
|---|---|---|---|---|---|---|
| Zendesk | Support teams that want a ticket per conversation | A ticket with public comments | Internal notes | Organizations | Help Center articles, with new dates | Set on tickets and comments by the Ticket Import API |
| Freshdesk | Support teams that want tickets and a solutions knowledge base | A ticket with incoming and outgoing replies | Private notes | Companies | Solution articles | Checked on your sample |
| HubSpot Service Hub | Teams whose sales already run on HubSpot | A ticket with email and note activities, not an inbox thread | Notes | Companies | Knowledge base articles, 400 per import | Activity times kept; ticket Create date checked on your sample |
| Gorgias | Ecommerce brands | A ticket with its messages | Internal-note messages | No company object | Help Center articles, imported directly from Intercom | Set on messages through the API |
| Salesforce Service Cloud | Teams already running Salesforce | A Case with email messages and feed posts | Internal feed posts | Accounts | Knowledge articles, through the article importer | Set at insert, with a permission |
| Stay on Intercom | Teams built around the Messenger and Fin AI Agent | Stays a conversation | Stay notes | Stay companies | Stay where they are | Unchanged |
Three things are true of every move, from Intercom's own help centre and developer documentation:
- There is no bulk export of conversation text. Intercom's help article on exporting conversations says to "use a GET request on each conversation ID to pull detailed content". Its CSV exports hold reporting metadata only, and its Amazon S3 export "will not contain a transcript".
- Long threads need extra calls. Retrieving a conversation returns the 500 most recent parts unless the request pages back through older ones.
- Automation is rebuilt. Writing about moves between its own workspaces, Intercom says "workflows cannot be transferred. You must manually recreate them". The same goes for Series, bots, Fin AI Agent configuration and macros. Macro text can be exported to CSV.
How to read the cards. Each card follows six Intercom items. "Native" means the target has the same kind of record. "Kept as" means the item survives in a different form. "Does not carry over" means the target has nowhere to put it. "We map it as…" marks our design choice, not a vendor rule, and every one is agreed on your free sample.
1. Zendesk
Who it suits. A general support team that wants every conversation to be a ticket with a status, an owner and a place in a queue.
- Conversation: native, as a ticket. Zendesk's Ticket Import API sets a ticket's created, updated and solved dates. Zendesk says triggers won't run on an imported ticket that is not closed, until it is next updated.
- Messages: native, as public comments. Each imported comment carries its own author and created time. Zendesk comments are public or internal with no bot type, so we map Fin AI Agent and bot parts as comments from a bot user, or drop them.
- Internal notes: native. Zendesk's comments API marks a comment that is not public as "an internal note".
- Intercom tickets: native, as tickets. We map each ticket type as a Zendesk ticket form or a tag.
- Contacts and companies: native, as end users and organizations. Zendesk's Users and Organizations APIs both have an
external_idfor a record elsewhere, which holds the Intercom ID. - Articles: kept as Help Center articles, with new dates. Zendesk's Articles API lets the author be set but makes
created_atread-only.
What Zendesk cannot hold. Zendesk says metrics and SLAs are not supported on imported tickets, and one ticket holds at most 5,000 comments.
Choose it when ticket discipline matters more to you than a chat-first inbox. Full mapping: Intercom to Zendesk migration.
2. Freshdesk
Who it suits. A general support team that wants tickets, canned responses and a knowledge base of categories, folders and articles.
- Conversation: native, as a ticket. One Freshdesk ticket per Intercom conversation.
- Messages: native, as replies. Customer parts become incoming replies and teammate parts outgoing replies. We hold no Freshdesk documentation on setting original reply times, so they are checked on your sample.
- Internal notes: native, as private notes.
- Intercom tickets: native, as tickets. We map each ticket type as a Freshdesk ticket type or a tag.
- Contacts and companies: native, with one condition. Freshdesk contact email is unique, and a ticket with an unknown email creates a contact on the fly, so Intercom leads without an email need a rule before the load.
- Articles: native. Collections and sections become solution categories and folders.
What Freshdesk cannot hold. All attachments on one ticket together cannot exceed 20 MB, while Intercom allows Messenger files up to 100 MB. Ticket creation is capped at 50 a minute on Growth, 160 on Pro and 280 on Enterprise.
Choose it when you want a straightforward ticket desk and most Intercom contacts have an email address. Full mapping: Intercom to Freshdesk migration.
3. HubSpot Service Hub
Who it suits. A team whose sales or marketing already runs on HubSpot. HubSpot's help desk workspace is available on Service Hub Professional and Enterprise.
- Conversation: kept as a ticket, not an inbox thread. HubSpot's Conversations API guide documents no way to create a thread, and messages posted to an existing thread "are sent from the channel". We map each conversation as a ticket in a pipeline.
- Messages: kept as email activities or notes. HubSpot email activities take
hs_timestampfor their place on the timeline,hubspot_owner_idfor the sender andhs_email_directionfor the direction. We map chat messages as notes in time order. - Internal notes: native, as notes. A HubSpot note body holds up to 65,536 characters, and files attach through
hs_attachment_ids. - Intercom tickets: native, as tickets. States map to pipeline stages, each marked OPEN or CLOSED. HubSpot's pages disagree on ticket Create date: one calls it read-only except on deals, the ticket property page says users can edit it. We check it on your sample.
- Contacts and companies: native. HubSpot's import guide uses Email for contacts and Company domain name for companies to update a record instead of duplicating it.
- Articles: native, with limits. HubSpot's Smart copy imports from an Intercom-hosted Help Center, up to 400 articles per import, without tables, and all into the primary language.
What HubSpot cannot hold. Past conversations as inbox threads, and tables inside imported articles.
Choose it when one customer record for sales and support is the goal. Start at the HubSpot platform page.
4. Gorgias
Who it suits. Ecommerce brands. Gorgias integrates with Shopify, BigCommerce, Magento and WooCommerce.
- Conversation: native, as a ticket. Gorgias creates a ticket with its messages in one call, up to 500 of them, and its
importedflag marks the ticket and its messages as a historical import. - Messages: native. Each message takes created and sent times, and
from_agentmarks teammate messages. Gorgias warns that without a sent time "the message will be sent by Gorgias". Itsvialist has no Intercom value, so we map each part's original channel to chat or email. - Internal notes: native, as internal-note messages. Gorgias's guide says a note from a sender who is not a Gorgias user shows as sent by "Gorgias Bot", so teammates are created as users first.
- Intercom tickets: kept as tickets with two statuses. The Gorgias API has only
openandclosed. We map Intercom's five states to those two and keep the original state as a tag. - Contacts: native, as customers. Companies: do not carry over. Gorgias customers take an email and an
external_id, and the API has no company object. We keep the company name on each customer. - Articles: native. Gorgias imports Help Center articles directly from Intercom, or from a CSV file.
What Gorgias cannot hold. Companies as records, and ticket states beyond open and closed. Gorgias charges for tickets with at least one message sent from its helpdesk, and its billing page does not say how imported tickets count, so confirm that with Gorgias before a large load.
Choose it when support is mostly about orders on one of those four store platforms. Order data arrives when you connect the store, not through a migration. Start at the Gorgias platform page.
5. Salesforce Service Cloud
Who it suits. Teams already on Salesforce, with an admin to own the setup.
- Conversation: native, as a Case. An original created date can be set only when the record is inserted, by a user holding Set Audit Fields upon Record Creation and Update Records with Inactive Owners.
- Messages: email native, chat kept as feed posts. Email parts become EmailMessage records on the Case, with their body, date and an Incoming flag. Salesforce's chat objects do not suit history: LiveChatTranscript is "automatically created for each Live Agent chat session", and Salesforce says the ConversationEntry schema serves legacy chat, which is "in maintenance-only mode". We map chat parts as Case feed posts with their original author and time.
- Internal notes: native, as internal feed posts. A FeedItem can be visible to internal users only. Case comments, up to 4,000 bytes, are the alternative.
- Intercom tickets: native, as Cases. States map to Case Status, and Salesforce derives IsClosed from Status.
- Contacts and companies: native, as Contacts and Accounts.
- Articles: native, through the Knowledge article importer. Salesforce's importer takes a .csv that points to one .html file per rich text field, with images up to 1 MB and files up to 5 MB each.
What Service Cloud cannot hold. Field-by-field Case history, because history objects are read-only, and SLA processes, which are built in Setup. Your org's validation and duplicate rules also apply to the load.
Choose it when Salesforce is already your system of record. Start at the Salesforce Service Cloud platform page.
6. Stay on Intercom
Who it suits. Teams whose support is built around the Messenger and Fin AI Agent, and who have no problem to solve today.
- Conversations, notes, tickets, contacts, companies and articles: native, and unchanged. No migration, no retraining, no rebuilt workflows. The announcements say the platform keeps the Intercom name and that Fin will continue to serve its customers.
What to know now. Your exit path. Conversation text leaves only through the API. Intercom's attachment links expire, after 30 minutes or around six months for email attachments, so files are copied during the read. The companies list stops at 10,000 records, after which Intercom's Scroll API is needed.
Choose it when the platform fits your team and your own review turns up no reason to leave. The Intercom platform page lists what can be moved later.
How do you choose between them?
Start from where your customers and other systems already are, not from features. Four questions:
- Is anything wrong today? If not, staying is sound. Confirm your exit path and review again at renewal.
- Do you sell through an online store? If support is mostly order questions, look at Gorgias first, and decide where company data will live.
- Is your CRM HubSpot or Salesforce? Its service product keeps support on the same customer record, at the cost of splitting each conversation across records.
- Otherwise, Zendesk or Freshdesk. Both keep a conversation as one ticket. Check attachment sizes and how many contacts have no email before choosing Freshdesk.
Whichever you pick, ask to see your own conversations in it before you sign. A demo account shows the product. A sample of 100 of your records shows what your history will look like in it.
Facts checked November 17, 2026 from Intercom blog: Today Intercom becomes Fin, Salesforce press release, 15 June 2026, Salesforce press release, 10 September 2026, Intercom help: Export your conversations data, Intercom help: Additional details on Regional Data Hosting, Intercom API: Retrieve a conversation, Zendesk Ticket Import API, Freshdesk API, HubSpot: Edit a property value for a record, HubSpot: Import knowledge base articles, HubSpot Conversations API guide, Gorgias pricing, Gorgias: Import and export Help Center articles, Gorgias API: Create a ticket, Gorgias API: Create a message, Salesforce help: Set Audit Fields upon Record Creation, Zendesk API: Ticket comments, Zendesk API: Users, Zendesk API: Organizations, Zendesk API: Help Center articles, Freshdesk: API rate limits, Intercom help: Control how attachments are uploaded and used, Intercom API: List all companies, HubSpot developer docs: Notes, HubSpot developer docs: Email, HubSpot: HubSpot's default ticket properties, HubSpot: Format import files, Gorgias developer docs: Create a ticket using API, Gorgias: How you're billed for using Gorgias, Gorgias API: The Customer object, Salesforce object reference: EmailMessage, Salesforce object reference: FeedItem, Salesforce object reference: CaseComment, Salesforce object reference: LiveChatTranscript, Salesforce object reference: ConversationEntry and Salesforce help: Create a .csv File for Article Import. No vendor paid for this article. How we research
Intercom alternatives FAQ
Is Intercom shutting down after the Salesforce acquisition?
Nothing in the announcements says so. The company's rename post says Intercom "will live on as our customer service software platform", and Salesforce's press release of 10 September 2026 says Fin will continue to serve its customers as part of Salesforce's AI Labs.
Can Intercom chats become HubSpot inbox conversations?
Not as history. HubSpot's Conversations API guide documents no endpoint that creates a thread, and a message posted to an existing thread is sent from the channel like a live reply. Past chats therefore land on a HubSpot ticket as timeline activities, each with its original time set through hs_timestamp.
Do Intercom Help Center articles move to every option?
Yes, by different routes. Our Zendesk and Freshdesk mappings include them, HubSpot takes them through Smart copy on Service Hub Professional or Enterprise, Gorgias through its direct Intercom import, and Service Cloud through the Knowledge article importer. Zendesk sets new article dates, and HubSpot imports no tables.
Can I export all my Intercom conversations myself?
Not with their text, in one file. Intercom's help centre says CSV exports hold reporting metadata, not message content. Full conversations come from the API, one request per conversation, with extra requests for threads longer than 500 parts. A script has to list every conversation ID first, then read each one.
Which Intercom alternative keeps original conversation dates?
Zendesk, Gorgias and Salesforce Service Cloud each document one way: Zendesk through its Ticket Import API, Gorgias through created and sent times on every message, Salesforce through audit fields set at insert. HubSpot keeps each activity's time, but its own pages disagree on whether a ticket's Create date can change.
Do imported Intercom conversations count towards Gorgias billing?
Gorgias does not say. Its billing article charges a fee for "any ticket with at least one message sent from your Gorgias helpdesk", by an agent, AI Agent or rule, and does not mention imports. Ask Gorgias in writing before loading years of history, and plan the load with the answer.
How long should we keep Intercom after moving?
Until you have signed off the migration. No Intercom feature re-imports its exports, and the CSV exports hold no message text, so the live workspace is the only complete copy of your conversations. Keep it active until counts are reconciled and your team has checked real conversations in the new platform.
See your Intercom conversations in the platform you are considering
MigrateX is an AI migration platform, SOC 2 Type II, GDPR and HIPAA compliant. Send us one option from the list and your conversation count. You get 100 of your Intercom records in that platform, free, and a fixed quote within 24 hours. Book a scoping call. What a complete thread should contain after any move is covered in our guide to migrating ticket history.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


