Migrate All Messaging Channels
Converge Team
Part of the Dixa migration guide
Complete guide to migrating all your messaging channels (WhatsApp, Telegram, Messenger, etc.) from Dixa.
Migrating All Channels from Dixa
Dixa supports phone, email, live chat (Dixa Messenger), WhatsApp, Facebook Messenger, Instagram, SMS, and contact forms. It does not offer native Telegram, Discord, or Zalo support. Here's how to migrate each channel type.
Voice/Phone (Dixa Only)
Dixa includes a full cloud phone system with IVR, call recording, voicemail, and callback scheduling — all built into the agent workspace. If voice is critical to your support operation, this is a feature you'll need to replace separately. Converge focuses on messaging and does not include voice support. If you use Dixa for both voice and messaging, consider keeping a standalone VoIP solution for calls while moving messaging to your new platform.
Social Channels (Facebook Messenger, Instagram)
In Dixa, Facebook and Instagram are configured under Settings → Third-party messaging. Both connect via Meta OAuth through your Facebook Business pages. Disconnect from Dixa, then reconnect the same pages to your new platform. Your page followers, message history on the platform side, and page settings remain intact — they're stored by Meta, not Dixa. Reconnection takes 2–3 minutes per channel.
Dixa allows one WABA per organization with multiple numbers. Disconnect each number from Dixa before connecting to your new platform. See the WhatsApp migration guide for detailed steps.
Dixa Messenger (Live Chat Widget)
Dixa Messenger is Dixa's proprietary chat widget, available for web, iOS, Android, and React Native. It includes flow-based routing, knowledge article surfacing, and chatbot integration. This widget will stop working when you cancel Dixa. Replace it with your new platform's chat widget. In Converge, install the widget via script tag, Google Tag Manager, or native plugins for Shopify, WooCommerce, Wix, Squarespace, and more. Converge's widget also includes lead capture, FAQ, and visitor tracking features.
Email and SMS
Email migration involves redirecting forwarding rules (see email migration guide). Dixa's SMS channel (text messaging) connects separately and may not be available on all platforms. Contact forms created in Dixa will also need to be recreated on your new platform.
New Channel Opportunities
Dixa doesn't support Telegram, Discord, or Zalo natively. If you have customers on these platforms, switching to a platform with native support opens new communication channels. Converge natively supports all three — Telegram via bot token, Discord via bot token, and Zalo via OAuth — making it the only unified inbox with native Zalo support.
Migration order: Start with your lowest-volume channel to verify the setup works. Move high-traffic channels last. Plan voice separately from messaging — it's a distinct infrastructure decision.
Need the full migration guide?
This page covers migrate all messaging channels specifically. For the complete step-by-step migration process:
Read the complete Dixa migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial