Migrate All Messaging Channels

Converge Converge Team

Part of the Chatwoot migration guide

Complete guide to migrating all your messaging channels (WhatsApp, Telegram, Messenger, etc.) from Chatwoot.

Migrating All Messaging Channels from Chatwoot

Chatwoot supports 12 channel types: website live chat, email, Facebook Messenger, Instagram DMs, WhatsApp, SMS, Telegram, TikTok, X (formerly Twitter), Line, Voice (Enterprise only), and a custom API channel. Here's how each maps to your migration.

Social Channels (Facebook, Instagram)

Both connect via Meta OAuth in Chatwoot. Go to Settings › Inboxes and delete the Facebook/Instagram inboxes. Then connect the same Facebook Pages and Instagram accounts to your new platform using OAuth. Your page followers, business verification, and message history on Meta's side are unaffected.

Telegram

Chatwoot connects Telegram via a bot token. In Chatwoot, delete the Telegram inbox from Settings › Inboxes. You can reuse the same bot token in your new platform, or create a new bot via @BotFather on Telegram. Connection is instant — just paste the token.

WhatsApp and Email

These have dedicated sub-guides. See the WhatsApp migration guide and email migration guide for detailed steps.

Channels Chatwoot Has That Converge Doesn't

Chatwoot supports TikTok DMs, X (Twitter) DMs, Line, SMS, and Voice — none of which are currently available in Converge. If these channels are critical to your support workflow, evaluate whether you can redirect those conversations to a supported channel (e.g., asking TikTok customers to message via Instagram or WhatsApp instead).

Channels Converge Has That Chatwoot Doesn't

Converge natively supports Discord and Zalo (both OA and personal accounts) — channels not available in Chatwoot. If your customers use Discord for community support or Zalo for Southeast Asian markets, switching opens up new engagement channels.

Live Chat Widget

Replace Chatwoot's live chat widget script tag with your new platform's widget code. In Chatwoot, the widget is embedded via a <script> tag with your websiteToken. Remove that script from your website and add the new widget code. If you used Chatwoot's pre-chat form to collect visitor info, configure equivalent fields in your new widget. Also recreate any live chat campaigns (proactive messages triggered by page rules) you had set up in Chatwoot.

Slack Integration

If you connected Chatwoot to Slack for agent notifications or reply-from-Slack functionality, disconnect it from Chatwoot's Settings › Integrations page. This integration is platform-specific and doesn't carry over. Check whether your new platform offers similar Slack integration capabilities.

Migration order recommendation: Start with your lowest-volume channel, verify it works, then proceed to higher-volume channels. Save WhatsApp (which requires exclusive BSP registration) for last to minimize any message gap.

If you used Chatwoot's API channel for custom integrations (chatbots, internal tools, or third-party platform connections), document the webhook URLs and API configurations. These custom integrations will need to be rebuilt against your new platform's API, which may have different endpoint structures and authentication methods.

Need the full migration guide?

This page covers migrate all messaging channels specifically. For the complete step-by-step migration process:

Read the complete Chatwoot migration guide →

Ready to try Converge?

$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.

Start Free Trial