Migrate All Messaging Channels
Converge Team
Part of the Respond.io migration guide
Complete guide to migrating all your messaging channels (WhatsApp, Telegram, Messenger, etc.) from Respond.io.
Migrating All Channels from Respond.io
Respond.io supports WhatsApp, Facebook Messenger, Instagram, Telegram, LINE, Viber, WeChat, TikTok (Beta), SMS (via Twilio, MessageBird, or Vonage), email (IMAP/SMTP), VoIP calls, and Custom Channels (Advanced plan only). It does not support Discord or Zalo. Each channel type has a different disconnection and reconnection process.
WhatsApp Business API
Respond.io is a WhatsApp BSP, so your number is registered to their infrastructure. Disconnect from Settings > Channels, wait for release, then reconnect via your new platform's OAuth flow. Disable 2FA before migration. Your verified business status and approved templates carry over through Meta. See the WhatsApp migration guide for full steps.
Facebook Messenger and Instagram
Both connect via Meta OAuth through your Facebook Business Page and Instagram Business Account. Disconnect them from Respond.io's channel settings. Then connect the same pages/accounts to your new platform using Meta's OAuth flow. Your page followers, business verification, and ad accounts remain unchanged. Takes 2-3 minutes per channel.
Telegram
Telegram uses a Bot Token from BotFather. Remove the Telegram channel from Respond.io, then use the same bot token to connect to your new platform. Alternatively, you can revoke the old token and generate a new one via BotFather. Telegram bot connections are instant — no waiting period between disconnect and reconnect.
LINE, Viber, and WeChat
LINE uses your LINE Official Account credentials. Viber connects via a Viber Bot token (note: Viber is only available on Respond.io's Growth plan and above). WeChat uses your WeChat Official Account. Disconnect each from Respond.io's channel settings, then reconnect to your new platform if it supports these channels. Verify your new platform supports these specific channels before disconnecting.
SMS (Twilio, MessageBird, Vonage)
Respond.io doesn't own your SMS numbers — they connect through your third-party SMS provider account. Update the webhook URL in your Twilio, MessageBird, or Vonage dashboard to point to your new platform instead of Respond.io. Your SMS numbers, sender IDs, and provider accounts stay intact. No disconnection from Respond.io is strictly needed — just redirect the webhooks.
Custom Channels (Advanced Plan Only)
If you built Custom Channel integrations via API webhooks (available on Advanced plan at $279+/mo), these are Respond.io-specific configurations that won't transfer to any other platform. Document the webhook URLs, API endpoints, and message formats you configured so you can rebuild equivalent integrations in your new platform.
Channels Not Available in Respond.io
Respond.io does not support Discord or Zalo. If your customers use these platforms, switching to a platform with native support for these channels gives you additional coverage you didn't have before. This is a net gain in your migration — no disconnection needed for channels that weren't connected.
Migration order recommendation: Start with your lowest-traffic channel to verify the connection process. Then migrate Telegram and social channels (quick, no registration transfer needed). Save WhatsApp for last since it involves BSP migration and a brief routing gap.
Need the full migration guide?
This page covers migrate all messaging channels specifically. For the complete step-by-step migration process:
Read the complete Respond.io migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial