Intercom → Fin / Intercom Fin

Catalog plan outline

General guidance from the Afterstack catalog for Intercom → Fin / Intercom Fin. Not Intercom or Fin / Intercom Fin vendor documentation.

Migration friendliness

Intercom 5/10 · Fin / Intercom Fin 5/10

Speed to live

Intercom 6/10 · Fin / Intercom Fin 6/10

Catalog migration difficulty

Intercom not set · Fin / Intercom Fin medium

Data to export from Intercom

• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: inbound

How the catalogs differ

• Neither product is flagged for custom objects. Keep the object list short.
• Intercom is flagged with an open API, which is the export path to test.
• Fin / Intercom Fin is flagged with an open API for the load.
• Intercom is cataloged as a fit for: SaaS products with in-app chat.
• Fin / Intercom Fin is cataloged as a fit for: Teams already on Intercom.

Phases

1. Export

   Take Intercom as the source of truth for this pair. Export synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: inbound. Messenger-first support. Fin — listed separately as Fin / Intercom Fin — is the AI agent layer.

2. Map

   Load into Fin / Intercom Fin only after the field map is written down. Intercom’s AI agent — listed on its own because teams shop Fin, not a new helpdesk. Neither product is flagged for custom objects. Keep the object list short.

3. Prove a sample

   Fin / Intercom Fin scores 6/10 on speed to live and 5/10 on migration friendliness. Run one sample load and one report the team already uses in Intercom before a full cutover.

4. Cut over

   Intercom scores 5/10 on migration friendliness. Keep Intercom readable until the team is working in Fin / Intercom Fin. Intercom started as an in-app messenger and is now a support platform. Fin is Intercom’s AI agent; Afterstack lists Fin / Intercom Fin as its own catalog entry because teams shop the agent, not a new desk. Intercom itself is still the incumbent workspace: strong when the customer is already in the product, heavier if you needed classic email ticketing and a BPO-friendly queue.

Intercom to Fin / Intercom Fin: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Intercom or Fin / Intercom Fin vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Intercom

Moving from Intercom to Fin is not a workspace export. Fin AI Agent is already the agent inside the Intercom workspace, and the Fin FAQ updated September 11, 2026 says your Intercom public articles are already imported and ready. Article edits show up immediately. External content syncs weekly unless you remove it and sync again, and the same FAQ caps external sources at 100. Channels named there are Messenger on web, iOS, and Android, plus email, WhatsApp, SMS, Facebook, and Instagram. API-created conversations are answered only when a Workflow triggers Fin. A test workspace marked [TEST] is not supported for Fin. You can train and test without starting the paid clock. The 14-day Fin trial starts when you set Fin live, and setup requires an active subscription or an Intercom trial. If that trial has ended and you have not subscribed, Fin, outbound messaging, and the Help Center pause. If you still want an archive, the conversation-export article separates metadata from transcripts. A saved Inbox View exports to CSV for teammates who have Can export conversation data and an Inbox seat. Up to 25,000 cells download at once. Above that, the file is emailed. More than 100,000 rows is refused. Two exports cannot run in the same workspace at once. System views such as Inbox cannot be exported. The file has the visible columns only, and it is a point-in-time snapshot, not a schedule. Dataset export under Reports needs Can access Chart drill-in and Can export CSV, covers 13 reporting datasets, downloads up to 10,000 rows immediately, and keeps data for up to two years. It does not include message content. The Conversations dataset can include Has user reply and First contacted by, and First contacted by can be Fin AI Agent. Bulk transcript downloads from the Inbox are PDF or text, about 200 to 300 conversations per operation, and internal notes are left out. The Export API window is at most 90 days per request. The same article says an Amazon S3 JSON export does not contain a transcript, and a later sentence says S3 JSON provides detailed message content and attachments. Both sentences are on the page. A transcript is not something to promise from that S3 paragraph alone. The pricing page shows Essential at $29 per seat per month, Advanced at $85, and Expert at $132, each plus from $0.99 per Fin outcome. A 14-day full trial needs no card. The catalog's $29 starting price and trial flag match Essential and that trial. There is no free plan on the page, which matches the catalog.

• Intercom export your conversations data — checked 2026-10-18
• Fin AI Agent FAQs — checked 2026-10-18
• Intercom pricing — checked 2026-10-18

How Fin / Intercom Fin imports

There is no Fin inbox to import into. The Fin FAQ says public Help Center articles are already available to the agent. Content you add besides articles is public articles, documents, snippets, and public URLs, managed from Knowledge. Audience rules can withhold articles. One personality is allowed per workspace. Two brands that need two personalities need two workspaces. EU-hosted workspaces process Fin in Europe. AU-hosted workspaces can use Fin while processing is still described as US-based. Languages listed include Arabic through Vietnamese, with a note that unlisted languages are unpredictable. Images in chat or email can be read for text, UI, and error codes. ALT text is not read. The pricing FAQ defines an outcome as a customer confirming the issue is resolved, or not asking for more help after Fin responds, or Fin completing a workflow including handoffs. You are charged once per conversation. Fin on the Intercom plans is $0.99 per outcome on top of the seat. Copilot, a separate add-on, is $29 per agent per month billed annually or $35 billed monthly, with 10 Copilot conversations and 10 AI auto-translation conversations included per agent each month. The Pro add-on is $100 per month. Proactive Support Plus is $99 per month and includes 500 messages. Rechecked 2026-10-19, Intercom's pricing page and fin.ai/pricing both print $0.99 per outcome, while the September 17, 2026 outcomes article prints a $49 monthly base that includes 50 resolutions. The Fin catalog starting price stays empty because those pages still disagree. That empty field was not replaced. The catalog trial flag matches the 14-day Fin trial that starts at go-live. Early Stage is described as up to 93% off plus one year of Fin, and those customers do not also get the standard 14-day Fin trial. None of this moves tickets. The inbox, seats, and Help Center stay where they are.

• Fin AI Agent FAQs — checked 2026-10-18
• Intercom pricing — checked 2026-10-18

Object and field mapping

• An Intercom public article is already a Fin source. There is no article-import step on this pair.
• A conversation CSV from Dataset export is reporting metadata. First contacted by can say Fin AI Agent. The file still has no message body.
• A View CSV is the current queue, capped at 100,000 rows and blocked if another workspace export is running. It is not a Fin training file.
• A PDF transcript includes chronology and participants and excludes internal notes. Fin's answers do not read that PDF back.
• An API conversation is not automatically handled. The FAQ requires a Workflow.
• A brand Help Center is selected in brand settings for chat and for email. The personality stays one per workspace.
• External URLs are a different sync from public articles. Articles update immediately. External content updates weekly, and you can attach at most 100 external sources.
• Seat price and outcome price are separate bills. Essential is $29 per seat. The outcome is $0.99. The catalog stores 29 on Intercom and nothing on Fin.

What will not carry over

• A second helpdesk. Fin in this pair is the agent on the Intercom inbox you already have.
• Internal notes, via the transcript export. They are omitted.
• Message bodies, via Dataset CSV or a saved View CSV.
• Anything older than the export windows. Dataset and the S3 section say up to two years. The Export API request is 90 days.
• A [TEST] workspace. The FAQ says Fin is not supported there.
• ALT text inside images.
• Two Fin personalities in one workspace.
• A single Fin starting price. The field stays empty because the $0.99 pricing pages and the $49 outcomes article still disagree.
• Customer quotations on the pricing page. They are not a migration result.

Cutover checklist

1. Treat this as turning Fin on, not as emptying Intercom.
2. Confirm public articles in Knowledge before go-live. The FAQ says they are already imported.
3. Add external sources only up to 100, and expect a weekly sync rather than the immediate article update.
4. If you need an archive, pick the method on purpose: View CSV for the queue, Dataset CSV for metrics, Inbox PDF for a short batch of transcripts, Export API for a 90-day content pull.
5. Do not schedule a View export. The article says each one is manual.
6. Set Fin live only when you mean to start the 14-day Fin trial. Training does not start it.
7. Keep an active subscription. An ended trial pauses Fin and the Help Center.
8. Use a Workflow if any conversations are created through the API.
9. Put a second brand personality in a second workspace if you need one.
10. Quote Essential at $29 per seat per month. Quote Fin as $0.99 per outcome on the pricing pages and as a $49 base on the outcomes article. Leave the catalog's empty Fin starting price, which records that disagreement.
11. Ignore homepage-style customer quotes. They are not in the procedure.

Common pitfalls

• Exporting a Dataset CSV and expecting Fin to learn from message text that the file does not contain.
• Starting the 14-day Fin trial during training. The FAQ says the clock starts at go-live.
• Assuming AU hosting means AU processing. The FAQ says AU processing is still US-based.
• Loading a [TEST] workspace as the pilot. It is called out as unsupported.
• Writing only $0.99, or only the $49 base, into Fin's starting price. The pricing pages and the September 17, 2026 outcomes article still disagree, so the starting price stays empty and the note records both.
• Treating S3 as a guaranteed transcript store. The export article says both that S3 has no transcript and that the JSON has message content.

Related catalog pages

• Best AI-native Intercom alternatives (2026) — Which tool, compared
• What should replace Intercom? — Switch narrative
• Fin / Intercom Fin product page — Intercom’s AI agent — listed on its own because teams shop Fin, not a new helpdesk.
• Customer support category — Catalog hub for this category