Migrating from Intercom to Chatwoot is one of the most effective ways for growing businesses to slash their software overhead without sacrificing customer communication quality. While Intercom remains a powerful platform for customer messaging, its per-seat pricing and escalating add-on costs for bots and help centers can quickly push monthly bills past $139 per user. For bootstrapped startups, mid-sized support teams, and privacy-conscious organizations, Chatwoot emerges as the ideal alternative. As an open-source customer engagement suite, Chatwoot provides core capabilities that mirror Intercom—including omnichannel inboxes, shared team notes, automated chatbots, and live chat widgets—while offering complete data sovereignty through self-hosting or a predictable managed cloud tier.
Organizations typically initiate this transition when Intercom invoices begin outpacing team growth, or when internal compliance requires moving customer conversation data onto private infrastructure. Moving away from Intercom does require careful planning because proprietary ecosystems do not always map cleanly onto open-source architecture. However, by systematically auditing your canned responses, exporting historical customer data, and reconfiguring your webhooks, you can execute a seamless transition to Chatwoot. This guide walks you through every phase of the migration process, helping you preserve agent productivity, maintain continuity for your customers, and successfully cut ties with Intercom's restrictive pricing model.
For a 50-person team that's a significant annual saving.
🗺️ Migration Steps
Before exporting data, document all active Intercom features including custom attributes, team assignment rules, assignment tags, and automated workflows. Review your current widget placements across your websites and mobile apps so you know exactly where the Intercom script needs replacement. Identifying your essential configurations early prevents workflow disruptions after the switch to Chatwoot.
Choose between Chatwoot's managed cloud service or self-hosting the open-source edition via Docker or Kubernetes. Provisioning your own server gives you total control over database storage and security compliance, matching strict enterprise requirements. Once running, configure your domain, brand logos, and system settings within the Chatwoot dashboard.
Use Intercom's export tools to download your customer contact lists, user attributes, and historical conversation logs in CSV format. While Intercom does not provide a direct one-click importer for Chatwoot, these exported files serve as the primary dataset for migration scripts. Ensure you capture contact identifiers like email addresses and user IDs to maintain continuity.
Import your cleaned CSV contact lists into Chatwoot using its contact management tools or API endpoints. Next, configure your communication channels—such as website live chat widgets, email channels, and social media integrations like WhatsApp or Facebook—inside Chatwoot's inbox settings. Recreate your team structure by inviting agents, assigning roles, and setting up appropriate team inboxes.
Translate Intercom's Business Messenger rules and automated assignment macros into Chatwoot's automation rules and labels. If you relied on Intercom Articles, migrate your help center content by exporting your articles and publishing them natively to Chatwoot's Portal feature. Test your custom chatbots and routing rules thoroughly before pushing live.
Remove the Intercom JavaScript snippet from your website's header and replace it with the Chatwoot website widget code. Perform end-to-end testing by sending test messages through your live chat, email, and social channels to verify that agents receive notifications instantly. Once verified, cancel your Intercom subscription to finalize the migration.
⚠️ Common Challenges & How to Avoid Them
Write a custom Python migration script utilizing the Chatwoot REST API to programmatically ingest historical contacts and past conversation transcripts, or archive the Intercom export as a searchable reference database.
Map out your branching decision trees and use Chatwoot's integration capabilities with webhook tools like n8n or Make to replicate advanced automated routing and FAQ deflection.
Run a one-week parallel testing phase where agents handle inbound queries in Chatwoot while keeping Intercom open as a fallback, utilizing Chatwoot's intuitive keyboard shortcuts guide for quick onboarding.
🔗 Get Started
❓ Frequently Asked Questions
Direct automated migration of full chat transcripts is not built into out-of-the-box settings because of differing data schemas. However, you can use Chatwoot's REST API to programmatically import past conversations and customer profiles, or keep your Intercom data exported as a static archive.
Intercom charges steep monthly fees starting around $39 to $139 plus extra per-seat and usage fees that scale aggressively. Chatwoot offers a free open-source version that you can self-host indefinitely, and a managed cloud plan starting at a fraction of Intercom's cost with no hidden user seat penalties.
Downtime is minimal if you execute the cutover correctly. By deploying your Chatwoot instance, importing contacts, and swapping out the JavaScript tracking snippet on your website during low-traffic hours, your chat widget will transition smoothly with zero lost customer inquiries.
Want a full feature and pricing comparison before you switch?
Read the Full Intercom vs Chatwoot Comparison →