- Migration Guides
- Trengo
- Migrate All Messaging Channels
Migrate All Messaging Channels
Part of the Trengo migration guide
Complete guide to migrating all your messaging channels (WhatsApp, Telegram, Messenger, etc.) from Trengo.
Migrating All Channels from Trengo
Trengo natively supports WhatsApp Business API, email, live chat widget, Facebook Messenger, Instagram DMs, SMS, and voice (as a paid add-on). It also offers Telegram integration and custom channels via API on the Pro plan. Trengo does not support Discord or Zalo.
WhatsApp Business API
Trengo is an official WhatsApp BSP, so your number is registered through their system. See the dedicated WhatsApp migration guide for the full BSP release and reconnection process. This is typically the most complex channel to migrate because of the BSP handoff.
Live Chat Widget
Trengo's widget is embedded via a JavaScript snippet in your website HTML. To migrate, remove the Trengo widget code from your site's header or footer (or uninstall the Trengo Shopify/WooCommerce app if you used a plugin). Replace it with your new platform's widget code. If you configured widget automations in Trengo — greetings, Flowbot triggers, targeted messages — you'll need to recreate those in your new platform's widget settings.
Social Channels (Messenger, Instagram)
Facebook Messenger and Instagram DMs connect via Meta OAuth through your Facebook Business page. Disconnect these channels in Trengo, then reconnect the same Facebook pages and Instagram accounts to your new platform. Your page followers, verification status, and business information remain intact — they belong to your Meta accounts. The process takes 2-3 minutes per channel.
Telegram
If you added Telegram to Trengo, it connects via a Telegram Bot token. Disconnect the bot from Trengo, then use the same bot token (or create a new one via @BotFather) to connect to your new platform. Telegram bot connections are instant and don't require waiting periods.
SMS and Voice
SMS in Trengo is typically provided through a third-party carrier. Check whether your SMS number can be ported to a new provider. Voice is a paid add-on — if you use it, check whether your voice number is Trengo-provisioned or your own. Trengo-provisioned numbers may not be portable. If voice is critical to your workflow, verify your new platform supports it before migrating.
Channels Trengo Doesn't Support
Trengo has no integration for Discord or Zalo. If your customers use these platforms, switching to a platform with native support opens new communication channels without third-party middleware. Discord connects via a bot token and app ID, Zalo via OAuth — both take under 5 minutes to configure.
Migration order: Start with your lowest-volume channel (likely Telegram or Instagram), validate the setup, then migrate higher-traffic channels. Save WhatsApp for last since the BSP release process has the most variables.
Need the full migration guide?
This page covers migrate all messaging channels specifically. For the complete step-by-step migration process:
Read the complete Trengo migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial