Intercom's pricing has a peculiar sting: it charges per resolution on top of per-seat fees, so the better its automation gets at closing conversations, the more each closed conversation can cost, a support bill that climbs with your own success and resists forecasting. Intercom also bundles several jobs into one surface: an in-app messenger, bots, a help center, outbound lifecycle messages, and a shared inbox. The open source alternatives below unbundle that and run on a server you control, so support is priced by the hardware you provision rather than by conversations resolved, and the full record of every customer chat lives in a database you own and can query.
Chatwoot is an open-source, self-hosted customer support platform that centralizes conversations in one inbox. It is built for businesses that want to handle live chat, email, and social messaging while keeping full control over their customer data.
Frappe Helpdesk is an open-source ticket management tool for customer support teams. It helps you organize issue handling and resolve customer queries through a clean interface with a straightforward setup.
EspoCRM is a free, open-source CRM for managing customer relationships. It organizes leads, contacts, sales opportunities, marketing campaigns, support cases, and related business records in one web application that organizations can run on premise.
Dittofeed is an open-source omni-channel customer engagement platform for transactional and marketing messages. Teams send broadcasts or build automated journeys across email, mobile push, SMS, WhatsApp, Slack, and more. It targets self-hosted use as an alternative to OneSignal, Customer.io, and Segment Engage.
Sort these by which slice of Intercom you are replacing: the inbox, tickets, outbound messaging, or customer records.
Closest messenger and shared inbox: Chatwoot Chatwoot is the nearest single replacement for Intercom's core, centralizing live chat, email, and social channels like WhatsApp and Instagram in one shared inbox. Agents get private notes, mentions, labels, canned responses, and auto-assignment, plus a help center portal. Its Captain AI agent drafts replies and resolves routine questions, and it self-hosts so data stays yours.
Ticketing with SLAs: Frappe Helpdesk Frappe Helpdesk fits when your Intercom is really ticket-driven support. Separate agent and customer portals let customers track issues while agents work tickets, with customizable SLAs and assignment rules that route by priority, type, or workload. A built-in knowledge base publishes articles with search, and saved replies keep responses consistent. It self-hosts or runs on Frappe Cloud.
Lifecycle and outbound messaging: Dittofeed Dittofeed covers the outbound side of Intercom: onboarding sequences, lifecycle campaigns, and broadcasts across email, SMS, push, WhatsApp, and Slack. User data connects through Segment, Reverse ETL, or its API, and templates use HTML and MJML or a low-code editor. Branch-based Git workflows and a CI testing SDK give campaigns version control.
Customer records and CRM: EspoCRM EspoCRM handles the customer-record side, organizing leads, contacts, opportunities, and support cases in one self-hosted web app. Teams add custom entities, fields, and relationships, automate tasks, and connect other systems through a PHP REST API. It runs on MySQL, MariaDB, or PostgreSQL, a natural owner for customer identity after Intercom.
The reason leaving Intercom feels daunting is that its pieces share one identity graph and conversation history, so pulling out the messenger seems to threaten everything attached to it. In practice the switch is about deciding which tool owns what. The nearest single replacement is Chatwoot, an omnichannel inbox that gathers live chat, email, WhatsApp, Instagram, and more into one shared queue, with private notes, labels, canned responses, auto-assignment, a help center portal, and a built-in AI agent. If your Intercom is mostly ticket-driven support, Frappe Helpdesk leans into agent and customer portals, SLAs, and a knowledge base instead.
Where the bundle really splits is the parts of Intercom that are not the inbox. Outbound onboarding and lifecycle campaigns map to Dittofeed, which builds automated journeys and broadcasts across email, SMS, push, WhatsApp, and Slack, while customer records, companies, and support cases may belong in a CRM like EspoCRM. Deciding that ownership up front, who holds contacts, events, and consent after the move, matters more than any feature checklist, because the split changes which team maintains each workflow.
Migration is an export-and-rebuild project. Use Intercom's exports and API to pull contacts, companies, conversations, tags, custom attributes, and help center articles; transcripts survive better than bot logic, and article HTML usually needs formatting fixes, image re-linking, and redirects. Preserve original Intercom IDs as reference fields so agents can trace old cases, run both systems briefly, and keep a read-only archive until support and finance agree the data has landed.
It removes the meter. Instead of paying per seat and per resolution, a self-hosted tool like Chatwoot is priced by the hardware you provision, so automation that closes more conversations does not raise your bill. The cost does not vanish, though: it shifts to hosting, databases, email delivery, backups, and admin time. The savings are clearest when your team can run the stack competently.
Chatwoot. It centralizes live chat, email, and social channels in one shared inbox, with private notes, mentions, labels, canned responses, and auto-assignment, plus a help center portal and its Captain AI agent for routine replies. Expect more variance around visitor qualification and polished end-user UI, so test your highest-volume workflows rather than comparing feature grids.
Often several, because Intercom bundles jobs that open source keeps separate. Chatwoot or Frappe Helpdesk covers the inbox and support side; Dittofeed handles outbound onboarding and lifecycle messaging; a CRM such as EspoCRM can own customer records. That split is not necessarily worse, but it changes ownership, so map which team maintains each piece before you commit.
Mostly, with cleanup. Article text, titles, and collections usually survive, but formatting, embedded media, broken image links, and category structure rarely land perfectly. Chatwoot and Frappe Helpdesk both include a knowledge base to receive them. If your articles rank in search or are linked from the product, plan URL mapping and redirects carefully, and recheck public versus private visibility rules.
The website widget, yes; the deep mobile SDK experience, not always. Chatwoot provides a live-chat widget and shared inbox that cover most in-app messaging. Intercom's mobile SDKs also handle push, user identity, and in-app help, and open source replacements may offer fewer mobile-native features. If mobile matters, prototype login handoff, push, unread counts, and attachments before committing.
Usually not. Conversation transcripts export, but bot paths, qualification rules, and AI answer configuration are normally rebuilt, so treat this as a workflow redesign. Chatwoot's Captain AI agent can draft replies and resolve routine questions, but you configure it fresh. Start with the automations that deflect the most tickets, rebuild them, and compare results against your historical Intercom volumes.
Decide who owns identity first: the support tool or a CRM. Intercom contacts, companies, custom attributes, and events often carry years of operational shortcuts, so clean duplicates and stale attributes before importing. EspoCRM can hold that record with custom entities and relationships. Keep important Intercom IDs as reference fields, and document which attributes still drive routing, segmentation, or compliance.
