Migrate All Messaging Channels
Converge Team
Part of the Crisp migration guide
Complete guide to migrating all your messaging channels (WhatsApp, Telegram, Messenger, etc.) from Crisp.
Migrating All Channels from Crisp
Crisp supports live chat (website widget), email (Mini+), Telegram (Mini+), Facebook Messenger (Mini+), Instagram DMs (Essentials+), and WhatsApp (Essentials+). It does not natively support Zalo on any plan. Discord exists only as a third-party notification plugin — not as a conversation channel in the inbox.
Website Chat Widget
Crisp's chat widget is embedded via a JavaScript snippet or through native plugins for WordPress, Shopify, WooCommerce, Wix, and other platforms. To migrate: remove the Crisp widget code from your site. For Shopify, uninstall the Crisp app from your Shopify admin. For WordPress, deactivate the Crisp plugin. For other platforms, remove the <script> tag containing CRISP_WEBSITE_ID from your HTML. Then install your new platform's chat widget using their equivalent method.
Telegram
Crisp's Telegram integration (Mini+) uses a standard bot token created through Telegram's BotFather. To migrate: you can either reuse the same bot token on your new platform (disconnect from Crisp first) or create a new bot. In Crisp, the integration is configured through Settings → Plugins → Telegram. Remove the token from Crisp, then paste it into your new platform's Telegram connection settings. Only one platform can use a bot token at a time.
Facebook Messenger and Instagram DMs
Messenger (Mini+) and Instagram (Essentials+) connect through Meta OAuth in Crisp's integration settings. Disconnect these channels from Crisp, then reconnect the same Facebook pages and Instagram accounts to your new platform. Your page followers, business verification, and settings remain intact — they're tied to your Meta Business account. Each reconnection takes 2–3 minutes.
WhatsApp (Essentials+) requires a number transfer through Meta's WhatsApp Manager. See the dedicated WhatsApp migration guide for the full disconnect-reconnect process. Plan this during low-traffic hours to minimize the gap between platforms.
Crisp handles email through forwarding (Mini+). Update forwarding rules in your email provider to point to your new platform's inbound address. See the email migration guide for detailed steps, including DNS changes for custom email domains.
Channels Crisp Doesn't Support Natively
Crisp has no native inbox integration for Discord (only a notification plugin that sends alerts to a Discord channel — conversations aren't managed in the Crisp inbox) or Zalo on any plan. If your customers use these platforms, switching to a platform with native support opens new channels without workarounds. Discord connects via a bot token (2 minutes to set up), and Zalo via OAuth with PKCE flow — these are net-new channels you gain by switching, not channels you need to migrate.
Migration order: Start with your lowest-volume channel. Migrate the website chat widget and Telegram first (quick, low risk). Save WhatsApp and email for last — they carry the most traffic and have the highest impact if something goes wrong during the switch.
Need the full migration guide?
This page covers migrate all messaging channels specifically. For the complete step-by-step migration process:
Read the complete Crisp migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial