message.comDevelopers

Migrate from Drift to message.com

Drift is a sales-led conversational marketing tool with high per-seat pricing. message.com keeps the proactive-engagement patterns (playbooks become proactive messages) and adds the unified inbox, AI grounded in your data, and a flat predictable cost structure.

What stays the same

  • Snippet install. Async script before </body>.
  • Proactive engagement. Drift "playbooks" map to message.com proactive messages and AI agent flows.
  • CRM hooks. Both push qualified leads to CRM. Same Salesforce / HubSpot patterns.
  • Calendar booking. Both support meeting scheduling inside chat.

What is different

  • No per-seat pricing. Drift seats add up fast on growing teams.
  • Unified inbox. Drift is chat-led with a bolt-on email product. message.com puts chat, email tickets, and phone in one inbox.
  • AI in base. Drift AI Conversations is a tier-up; message.com AI ships in base.
  • Native phone. Drift does not include phone. message.com does.

1. Export Drift data

  1. In Drift, go to Settings → Data → Export.
  2. Export Contacts as CSV.
  3. Export Conversations as CSV / JSON.
  4. Screenshot or document your active Playbooks; they do not export cleanly.

2. Set up message.com

  1. Sign up at app.message.com/register.
  2. Enable chat as the first channel.
  3. Copy the snippet from Settings → Chats → Installation.

3. Import contacts

Upload contacts CSV under Settings → Visitors → Import. Mapping:

  • Drift emailemail.
  • Drift namename.
  • Drift contact ID → externalId with drift: prefix.
  • Drift custom attributes → message.com attributes.

4. Swap the snippet

Remove the Drift snippet (loads from js.driftt.com). Paste:

HTML
<script>
  (function(d,s,o){
    var j=d.createElement(s);j.async=1;j.src='https://app.message.com/widget.js';
    j.dataset.workspace=o;
    d.head.appendChild(j);
  })(document,'script','YOUR_WORKSPACE_ID');
</script>

5. Recreate playbooks

Three patterns to rebuild Drift playbooks:

  • Welcome bot. Proactive message on first page view with a brand-aligned greeting. See Send proactive messages.
  • Target-account playbook. Identify visitors by company (via your reverse-IP enrichment), proactively offer help. Wire the lookup as an AI custom tool.
  • Sales calendar drop. Add a calendar link to the AI agent's allowed tools or use a saved reply.

6. Connect CRM

Cutover checklist

  • Staging install verified, identify wired up.
  • Playbooks rebuilt as proactives and / or AI flows.
  • Calendar booking flow tested end to end.
  • CRM sync flowing in both directions (push to and from).
  • Mobile tested.
  • Dual-load Drift + message.com for a week.
  • Remove Drift from production.
  • Cancel Drift.

Common pitfalls

  • Playbook complexity. Some Drift playbooks have branching conversation trees that took months to tune. Plan time to translate logic. The AI-agent path often replaces a complex tree with a single prompt.
  • Drift Email product. Separate from Drift Chat. If you used it, plan email migration as part of the same effort.
  • ABM enrichment. Drift includes ABM enrichment by default. If you depend on it, plug in a third-party enrichment (Clearbit, Apollo) called from an AI custom tool.
  • Hand-off to sales reps. Drift's round-robin assignment maps to message.com's department routing. See Route by department.