Migrate All Messaging Channels

Converge Team

• Updated March 12, 2026

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

Migrating Channels from Drift

Drift natively supports only two channels: website live chat and Drift Email. It does not have native integrations for WhatsApp, Telegram, Messenger, Instagram, Discord, Zalo, or SMS. Migrating from Drift is less about transferring channels and more about expanding to the channels your customers actually use.

Website Chat Widget

Drift's chat widget is embedded on your website via a JavaScript snippet (or through CMS integrations for Shopify, WordPress, Webflow, and others). To migrate, remove the Drift snippet from your site's HTML or uninstall the Drift app from your CMS platform. Then add your new platform's widget code. If you had Drift playbooks configured for specific pages (e.g., pricing page bot, demo request bot), document those page-specific triggers before removing Drift — you'll want to recreate equivalent auto-reply rules or chatbot flows on your new platform.

Drift Email

If you used Drift Email, see the email migration guide for detailed DNS and configuration steps. The short version: update your subdomain DNS records, move outbound campaigns to a dedicated email tool, and connect inbound support email to your new platform.

Channels You're Adding (Not Migrating)

Since Drift doesn't support messaging apps natively, you're setting up these channels from scratch: WhatsApp — connect via OAuth using your Meta Business Manager account (5 minutes). Telegram — create a bot via @BotFather and enter the token (2 minutes). Messenger/Instagram — connect your Facebook page via Meta OAuth (3 minutes). Discord — create a bot application and enter the token and app ID (5 minutes). Zalo — connect your Zalo Official Account via OAuth (3 minutes). Each channel is independent and can be added one at a time.

CRM Integrations to Disconnect

If you integrated Drift with Salesforce, HubSpot, Marketo, or other CRMs, disable the Drift connection in those platforms before canceling. In Salesforce, check for the Drift managed package and any OAuth connections. In HubSpot, remove the Drift integration from Settings > Integrations > Connected Apps. Leaving stale OAuth tokens active was a factor in the September 2025 security incident that affected over 700 organizations — clean up all Drift-related integrations as part of your migration.

Migration Order for New Channels

Start by replacing the website chat widget — this is your only active channel in Drift and should be migrated first to avoid any gap in coverage. Then add messaging channels based on where your customers are. If you serve customers in Southeast Asia, prioritize WhatsApp and Zalo. For European customers, WhatsApp and Telegram. For community-driven businesses, Discord. Each new channel is additive — no downtime or switchover risk since these are fresh connections.

Key difference from other migrations: When switching from most competitors, you're disconnecting and reconnecting existing channels. With Drift, you're replacing one channel (website chat) and adding several new ones. This makes the migration simpler in some ways — there's less to break — but means your team needs training on channels they haven't managed before.