Migrating from Intercom to an AI-First Platform: A 2026 Checklist
Plan an Intercom exit: inventory each export format, rebuild workflows by hand, test AI handoff in parallel and keep a read-only archive before you cancel.
- Updated
- Reading time
- 16 min read
12 sections
- Do you need to leave Intercom, or only replace Fin?
- Step 1: Inventory what Intercom can export
- Step 2: Clean the content and build a test set
Moving off Intercom is mostly inventory and rebuild work. Intercom lets you export article HTML, conversation transcripts, reporting CSVs and contact lists, but its Workflows, bots, Series and routing rules have no portable export, so you document them and rebuild them by hand. The AI agent is usually the easiest part to replace. The hard parts are cleaning the help center, rebuilding automation, testing human handoff and keeping access to old conversations after you cancel.
This checklist separates three things that migration guides often blur: what Intercom's own documentation says you can export, what Chatsy can actually take in today, and what nothing will move for you. Chatsy has no Intercom importer, so every Chatsy step below is a manual or crawl-based path.
How this was researched: desk research of Intercom's and Fin's official pricing pages and Intercom's help-center export articles, checked November 12, 2026, plus Chatsy's own product documentation. We did not run a live migration for this article. Chatsy publishes this blog, so weigh what we say about Chatsy accordingly.
Do you need to leave Intercom, or only replace Fin?
Decide this first, because the answers lead to very different projects. Fin is now sold on its own: the Fin pricing page lists $0.99 per outcome with a 50-outcome monthly minimum when you use your current help desk, and fin.ai says Fin "works excellently with Salesforce, Zendesk, Hubspot, Freshdesk, and many other helpdesks". So "leaving Intercom" and "leaving Fin" are now separate decisions.
| Your situation | Likely project | Size of the job |
|---|---|---|
| Happy with Intercom's inbox, unhappy with Fin cost or answers | Swap or trial a different AI front line; keep the Intercom inbox | Small: content and handoff only |
| Moving to another help desk, happy with Fin | Move the inbox and keep Fin on the new help desk (if it is on Fin's supported list) | Large: inbox, history, automation |
| Leaving both | Full migration: new inbox, new AI agent, new help center | Largest: everything in this checklist |
| Mainly unhappy with seat cost | Check seat types and plan tier first; Advanced includes 20 free Lite seats per Intercom pricing | Often no migration needed |
To size the cost side, use one stated workload rather than a vendor's best case. The table below uses 5 agents, 2,000 customer conversations a month, AI answering first on all of them, and 40% of conversations ending as a billable Fin outcome (800 outcomes). For Chatsy, which bills per AI reply rather than per outcome, it assumes 3 AI replies per conversation (6,000 replies). Intercom prices are from intercom.com/pricing, checked November 12, 2026. That page has a monthly/annual toggle but does not label which cadence the per-seat prices use, and Essential shows $19 with $29 struck through ("New customers save 35%").
| Option | Seats | Seat cost | AI billing unit | AI usage in this workload | AI cost | Monthly total |
|---|---|---|---|---|---|---|
| Intercom Essential | 5 | 5 x $19 = $95 (5 x $29 = $145 at list) | Fin outcomes | 800 outcomes | 800 x $0.99 = $792 | $887 ($937 at list) |
| Intercom Advanced | 5 | 5 x $85 = $425 | Fin outcomes | 800 outcomes | $792 | $1,217 |
| Intercom Expert | 5 | 5 x $132 = $660 | Fin outcomes | 800 outcomes | $792 | $1,452 |
| Fin on another help desk | Your help desk's seats | Your help desk's price | Fin outcomes | 800 outcomes | $792 (50-outcome minimum) | $792 + help desk |
| Chatsy Pro | 5 | Included in plan | AI replies (credits) | 6,000 replies = 6,000 credits at 1 credit each, 12,000 at 2 | Included up to the cap | $500 ($5,000 a year) |
Read the last row carefully. A Fin outcome and a Chatsy AI reply are different units, so the totals are not a like-for-like price per answer. Chatsy Pro has 15,000 monthly credits and blocks a reply that would bring usage to the allowance, so it covers at most 14,999 one-credit replies. At 3 or more credits per reply this workload needs 18,000 credits or more, which is above Pro and means an Enterprise quote. Chatsy's inbox is also much lighter than Intercom's (no SLAs, routing rules or round robin). For a fuller cost model, see the Intercom pricing breakdown, the message credits guide or the chatbot cost calculator.
Step 1: Inventory what Intercom can export
Build a spreadsheet of everything your support operation depends on before you touch the new tool. The table below lists the export paths Intercom documents in Export your conversations data, Formatting and exporting your public articles with the Articles API and How to export users, leads, or company data, checked November 12, 2026. Check Intercom's current export documentation before you rely on any limit.
| Asset | Intercom export path | Format and limits (per Intercom docs) | Into Chatsy? |
|---|---|---|---|
| Public help-center articles | Articles API, one article at a time by ID; no UI export | HTML body, title, metadata, localization data | Not imported directly. Crawl the public URLs or re-create articles (Step 3) |
| Article images | Inside the article HTML | Must be complete, publicly accessible URLs | Download and re-host before Intercom access ends |
| Conversation transcripts | Inbox: export one or a bulk selection as text or PDF; or the Conversations API | Bulk is about 200 to 300 conversations per operation; internal notes are excluded | No import. Keep as an archive |
| Reporting data | Reports > Dataset export | CSV with reporting metadata only, no message content; browser download limit 10,000 rows; large exports emailed | No import |
| Saved views | Download icon on the view, "Export as CSV" | CSV snapshot; over 100,000 rows refused | No import |
| Bulk data to storage | Settings > Data > Imports & exports > Export data to Amazon S3 | JSON; Intercom says it contains no transcripts | No import |
| Export API | API | Maximum 90-day window per request | No import |
| Contacts (users, leads) | Contacts > select > More > Export users | CSV sent by email; link expires after one hour; company data limited | No contact import |
| Workflows, custom bots, Series, Product Tours | No portable export documented in the articles above | Screenshot and document every trigger and branch | Rebuild by hand where an equivalent exists |
| Macros (saved replies), tags, teams, assignment rules | No export documented in the articles above | Copy text and settings manually | Saved replies and tags can be recreated manually |
Two practical notes. First, exports contain personal data, so decide where the files live and who can open them before you run them. Second, the conversation exports serve your records and your agents, not the AI: old transcripts are a poor training source because they contain customer details and outdated answers.
Step 2: Clean the content and build a test set
Fix the content before it reaches any new AI agent. An AI agent answers from whatever you give it, so stale articles become stale answers.
- Audit articles. Mark each one keep, update or retire. Retire anything that describes a pricing plan, UI or policy you no longer have.
- Collect a test set. Pull 30 to 50 real customer questions from the last 90 days of transcripts, including ones Fin or your team answered badly. Strip names, emails and order numbers. Write the correct answer next to each.
- List the handoff cases. Note which questions must always reach a person: billing disputes, account access, legal, anything that needs account data.
The test set is the most useful artifact of the whole migration. You will use it in Step 6 to compare the old and new setups on identical questions.
Step 3: What Chatsy can take in today
Chatsy has no Intercom importer, no conversation import and no contact import. These are the verified ways content gets in, with the plan that unlocks each (see Train your AI agent):
| Source | How it works | Plan |
|---|---|---|
| Whole-site crawl | Point it at your public help center; set a page limit (up to 10,000) and include/exclude paths | Hobby and above |
| Single page | Reads one URL only | All plans |
| List of links | Up to 500 URLs, one per line, each added as its own page | All plans |
| File upload | TXT, HTML, PDF, DOC, DOCX, MD or CSV, up to 25 MB per file | All plans (storage cap applies) |
| Written answer | A question and answer saved as a text source | All plans |
| Chatsy help-center articles | Import one article, a category or all articles from a Chatsy knowledge base | Hobby and above |
The simplest path for an Intercom help center is to crawl it while it is still public, test answers, and only later decide whether to rebuild the articles inside Chatsy's own help center. If you do rebuild, the Chatsy article editor parses Markdown, articles have draft, published and archived states, and a knowledge base can use a custom domain (Publish a knowledge base). Two limits to plan for: Chatsy's public help-center search is keyword search, and website sources do not re-crawl on a schedule, so you re-read a source manually after you change the pages.
Step 4: Rebuild what does not move
Nothing moves Intercom Workflows, bots, Series or routing rules into another product. Document each one, then decide whether to rebuild, replace or drop it.
| Intercom feature | Closest Chatsy option today | Gap to plan for |
|---|---|---|
| Fin AI Agent | AI agent trained on your sources, with a model you choose | Different billing unit (credits per reply); no Fin Procedures |
| Workflows and custom bots | Agent instructions, written answers, and custom API tools (REST or OpenAPI import, HTTPS only, 15-second timeout) | No visual workflow builder; test each custom tool end to end before going live |
| Inbox and ticketing | Live chat queue plus a forwarding-based email mailbox with numbered tickets, statuses, priorities, assignees and tags | No SLAs, routing rules, round robin, CSAT surveys or phone |
| Round robin and assignment rules | Teammates claim live chats manually; tickets get a manual assignee | No round robin or skills routing |
| Macros | Saved replies with customer-name and ticket-number placeholders | Recreate by hand |
| Help center | Public knowledge base with categories, images, custom domain | Keyword search only |
| Series, Product Tours, Surveys, banners | None | Needs a separate tool, or keep Intercom for these |
| WhatsApp, SMS, phone | None | Chatsy is website chat and email only |
| CRM and app integrations | Dashboard connections exist for some services, but agents cannot run those actions yet; HubSpot, Salesforce and Shopify connectors are planned, not available | Do not plan a cutover that depends on them |
If a Workflow looks up account data, it only survives the move if you can rebuild it as a custom API tool against your own endpoint, and that tool has passed end-to-end testing. Otherwise route that question to a person.
Step 5: Set data and consent boundaries
Agree on these rules before anyone uploads a file:
- Only load content you want quoted. Anything in a source can appear in an answer. Do not upload raw transcripts, contact CSVs or internal notes as knowledge.
- Decide retention for exports. Intercom exports sit in your storage, not Intercom's. Set an owner and a delete date for them.
- Check your requirements against what Chatsy offers. Chatsy does not offer SOC 2 Type II, a signed HIPAA BAA or SSO today, does not publish a named subprocessor list, and has no self-serve account export or deletion control (requests go through support). Intercom's Expert plan lists SSO and HIPAA support. If those are hard requirements, stop here. See Security.
- Languages. Chatsy's widget interface is available in English and Spanish only. Test answers in any other language your customers use before you rely on them.
Step 6: Run both in parallel and test handoff
Keep Intercom live while you test the new setup on a staging page or a low-traffic page. Run the Step 2 test set through both and score each answer as correct, partly correct, wrong or correctly handed off.
Handoff needs its own checks, because this is where migrations quietly break:
| Check | What to confirm in Chatsy |
|---|---|
| Live chat is on | The Live chat module (Hobby and above) adds the "Escalate to Human" tool to agents (Human handoff) |
| A person sees the escalation | Escalations land in the live-chat queue. Chatsy has no staff online status and sends no email alert to staff on escalation; connect Slack, Discord or Telegram alerts, or staff the queue |
| Nobody online | Visitors can leave an email for follow-up when email capture is on; the request is emailed to the owner of the agent |
| Email still arrives | Forward your support address to the mailbox after verifying it (Connect support email) and send a test message |
| Seats match the team | Seats include the owner: Hobby 1, Standard 3, Pro 5, Enterprise 10. Free and Hobby cannot invite teammates |
| Credits last the month | Watch usage against the plan's credits; there are no top-ups or overages, so a reply that would reach the allowance is blocked until the monthly reset or an upgrade |
Chatsy's analytics show conversations, first reply time, top questions, helpful ratings, handoff rate and knowledge gaps. It has no CSAT or resolution-rate dashboard, so compare the two setups on your test set and a manual transcript review rather than on a single headline metric.
Step 7: Cut over, keep a rollback, and keep history
Cut over only when the test set and a week or two of parallel traffic look acceptable to the people who will handle escalations.
- Swap the widget. Chatsy installs with one script tag before
</body>(Install the widget). Keep the Intercom Messenger snippet in version control so rollback is a single revert. - Write the rollback trigger. Agree in advance what sends you back: for example, wrong answers on a billing question, or escalations sitting unanswered.
- Re-point integrations. Find every webhook, email forward and app still sending to Intercom before you downgrade.
- Keep read access to history. Run the final transcript exports on cutover day. If agents still need to look up old conversations, keep a minimal Intercom workspace for a while: Intercom requires a minimum of one full seat, which is $19 to $29 a month at the Essential prices shown on the pricing page.
- Then cancel. Cancel only after the archive is complete and nothing still routes through Intercom.
When you should not migrate from Intercom
Staying is the right call in some cases, and a cheaper bill alone does not justify the move:
- You use Product Tours, Series, banners or in-app surveys heavily. Chatsy has nothing equivalent, so you would add another vendor.
- You run many mission-critical Workflows with branching logic. Each needs a manual rebuild, and some will have no equivalent.
- You need SLAs, round robin, skills routing, phone, SMS or WhatsApp in one inbox.
- You need SSO, HIPAA support or a SOC 2 report from your support vendor.
- Fin is working well and the only issue is the inbox: keep Fin and move the inbox, or stay put.
When Chatsy is not the right destination
Chatsy fits teams that want a website AI agent, live chat handoff, a forwarding-based email inbox and a help center on a fixed monthly plan, and that can live without heavy automation. It is a poor fit if you need any of the gaps listed in Steps 4 and 5, more than 10 seats, an importer that carries over conversation history or contacts, or agent actions through HubSpot, Salesforce, Shopify or another connected service today. Hobby also keeps the "Powered by Chatsy" line; removing it needs Standard or above.
FAQ
Can I keep Fin if I leave Intercom's inbox?
Yes, according to Fin's own pages. fin.ai/pricing lists Fin at $0.99 per outcome on your current help desk with a 50-outcome monthly minimum and no seat, setup or platform fees, and names help desks including Salesforce, HubSpot, Freshworks, Front and Gorgias. Check that your destination help desk is supported before you plan around it.
How long does an Intercom migration take?
It depends on the number of Workflows to rebuild, the size of the help center and how much history you need to keep accessible, so we do not publish a standard timeline. Size it from your Step 1 inventory: count the Workflows, the articles to keep and the integrations to re-point, then add a parallel-run period.
Will I lose my data when I cancel Intercom?
You lose access through Intercom's interface. Export transcripts, contacts and article HTML yourself before you downgrade, using the paths in Step 1, rather than relying on a request after cancellation.
Does Chatsy import Intercom conversations, contacts or Workflows?
No. Chatsy takes in knowledge through crawling, links, files, written answers and its own help-center articles. Conversation history, contacts, tags, Workflows, bots and Series do not import.
Which Chatsy plan does a five-person team need?
Pro is the smallest plan with 5 seats: $500 a month or $5,000 a year, with 15,000 monthly credits. Standard has 3 seats and Hobby has 1, and seats include the owner. See pricing.
Next step
Start with the inventory and the test set; they are useful whichever platform you choose. If you want to test Chatsy as the destination, create a free account, crawl a copy of your public help center, and run your test set against it in parallel with Intercom. For the Intercom side of the decision, read the Intercom review and Intercom vs Zendesk.