Switch Guide: Moving from Intercom to Chatwoot
Intercom is one of the most expensive per-seat SaaS products in the customer support category — plans for growing teams can exceed $500–$1,000 USD/month, and pricing is notoriously opaque. Chatwoot is the open-source alternative: a full-featured customer support platform (live chat, shared inbox, email, social channels) that you can self-host on Canadian infrastructure for under $50/month in server costs. For Canadian SaaS companies and e-commerce businesses, the economics are compelling.
What Is Chatwoot?
Chatwoot is an open-source customer engagement platform built by a team based in India, released under the MIT licence. It provides live chat, email inbox, social media channels (Twitter, Facebook, Instagram, WhatsApp), a help centre/knowledge base, team collaboration features, and automation workflows. It's a genuine Intercom alternative — not a stripped-down toy. When self-hosted on a Canadian VPS, all your customer conversation data stays in Canada.
What You'll Gain
- Dramatic cost reduction: Intercom charges $39–$99 USD/seat/month. Chatwoot self-hosted costs the price of a VPS ($20–$50/month total, unlimited seats).
- Canadian data residency: All customer conversations, contact data, and support history stored on your Canadian server.
- Full feature set: Live chat widget, team inbox, email channel, social channels, help centre, automation rules, canned responses, CSAT surveys, and reporting.
- No per-seat pricing: Add your entire support team without watching the bill climb.
- Data portability: Your data is in a PostgreSQL database you control. Export it any time.
- Active development: Chatwoot has a large, active open-source community and frequent releases.
What You Might Miss
- Intercom's AI features: Intercom has invested heavily in AI-powered support automation (Fin AI agent). Chatwoot's AI features are newer and less mature.
- Product tours and outbound messaging: Intercom is a full customer lifecycle platform — it does in-app onboarding tours, targeted outbound messages, and NPS surveys. Chatwoot focuses on inbound support and doesn't replicate Intercom's outbound/marketing features.
- Native mobile SDK: Intercom's mobile SDK for in-app support is polished. Chatwoot has a mobile SDK but it's less mature.
- Self-hosting overhead: You're responsible for updates, backups, and uptime. Budget approximately 2 hours/month for maintenance.
Migration Checklist
- Export your Intercom data — In Intercom, go to Settings → Data → Export. Export contacts, conversations, and knowledge base articles. Intercom exports as CSV and JSON.
- Export help centre content — Download all your help articles. You'll rebuild the knowledge base in Chatwoot's Help Centre.
- Provision your Canadian VPS — Minimum 4GB RAM, 2 vCPU, 50GB SSD. Chatwoot recommends at least 4GB RAM for smooth operation.
- Install Chatwoot — Use the official Linux installation script or Docker Compose deployment. Installation takes 30–60 minutes.
- Configure your domain and HTTPS — Point your support subdomain (e.g., support.yourcompany.ca) at your VPS. Use Certbot for SSL.
- Set up inboxes — Configure your channels: website live chat widget, email inbox (connect via SMTP/IMAP), and any social channels you use.
- Import contacts — Chatwoot supports CSV contact import. Map your Intercom contact fields to Chatwoot fields.
- Rebuild automation rules — Recreate your Intercom assignment rules, auto-replies, and SLA policies in Chatwoot's automation section.
- Add your team — Invite all support agents. Configure teams and agent roles.
- Rebuild knowledge base — Recreate your help articles in Chatwoot's Help Centre. Prioritize your highest-traffic articles first.
- Update your website chat widget — Replace the Intercom JavaScript snippet with the Chatwoot widget code. Test thoroughly before going live.
- Set up backups — Configure automated daily PostgreSQL backups to Canadian object storage.
Timeline Estimate
Server setup and configuration: 1–2 days. Knowledge base migration: 1–3 days depending on article count. Full cutover including team training: 1–2 weeks. Plan the widget swap for a low-traffic period (e.g., Sunday night) to minimize disruption.