Platform · Migrations

Coming from another tool? Here's the shape.

Intercom, Zendesk, HubSpot, ManyChat, Tidio, GoHighLevel and more. One migration pattern, ten platforms: connect channels, import contacts, rebuild automations, cut over.

  • Reconnect channels first, cut over last
  • Import contacts via CSV or matching integration
  • Rebuild nurture sequences as MessageMind automations
Try MessageMind free Jump to reference

What's inside

The headlines before you dive in.

  • Intercom. Export Contacts and Companies as CSV from Intercom's data export; import the contacts into MessageMind through Google Sheets contacts or by syncing them into HubSpot or Brevo first and letting the matching MessageMind integration pull them. Reconnect each channel (website chat snippet, WhatsApp, email forwarding) to MessageMind. Rebuild Intercom Series as MessageMind automations. The Intercom conversation archive stays on Intercom as a read-only record.

  • Zendesk. Export Users and Organizations as CSV from Zendesk's admin area; import into MessageMind the same way (CSV via Google Sheets contacts, or sync into HubSpot/Brevo and connect that CRM). Point your support email, website chat and WhatsApp number at MessageMind so new tickets open there. Rebuild Zendesk macros and triggers as MessageMind automations or as answers in the knowledge base.

  • HubSpot. There is a native MessageMind HubSpot integration. Connect it on /integrations, approve the OAuth consent, and HubSpot contacts flow into MessageMind through contact-creation and property-change webhooks, with meeting booking available on your selected scheduler links. Rebuild HubSpot workflows that touched messaging (sequences, chatflows) as MessageMind automations; leave CRM-side workflows on HubSpot.

  • ManyChat. Export subscribers as CSV from ManyChat's audience view and import them into MessageMind. Reconnect Facebook, Instagram and WhatsApp directly to MessageMind so new conversations arrive there instead of ManyChat. Rebuild each ManyChat Flow as a MessageMind automation using the trigger that fires on contact or conversation events.

  • Tidio / Lyro. Export contacts and visitors from Tidio as CSV and import them into MessageMind. Replace the Tidio website widget with the MessageMind website chat snippet, reconnect your Messenger and Instagram inboxes, and rebuild Lyro's trained answers as MessageMind knowledge-base entries plus automations.

  • GoHighLevel. Export Contacts as CSV from the GHL sub-account and import into MessageMind. Repoint the phone number, email domain and website widget to MessageMind. GHL campaigns (SMS and email drips) are rebuilt as MessageMind automations; GHL pipeline stages stay in GHL if you keep it as the CRM, or move to HubSpot/Brevo and connect that.

Documentation Platform fundamentals Migration guides

Platform integration

Migration guides

  • CategoryPlatform

Overview

Most MessageMind customers arrive from another tool, usually Intercom, Zendesk, HubSpot, ManyChat, Tidio or GoHighLevel. The migration shape is the same every time: connect the live channels first (WhatsApp, Instagram, Messenger, SMS, email, website chat) so new messages land in MessageMind, import your contacts through the matching MessageMind integration or a CSV, then rebuild nurture sequences as MessageMind automations before turning the legacy tool off. Conversation history on the legacy platform stays where it is as a read-only archive, because very few platforms expose a lossless transcript export and importing it would create duplicate threads.

What MessageMind can do with it

  • Intercom. Export Contacts and Companies as CSV from Intercom's data export; import the contacts into MessageMind through Google Sheets contacts or by syncing them into HubSpot or Brevo first and letting the matching MessageMind integration pull them. Reconnect each channel (website chat snippet, WhatsApp, email forwarding) to MessageMind. Rebuild Intercom Series as MessageMind automations. The Intercom conversation archive stays on Intercom as a read-only record.
  • Zendesk. Export Users and Organizations as CSV from Zendesk's admin area; import into MessageMind the same way (CSV via Google Sheets contacts, or sync into HubSpot/Brevo and connect that CRM). Point your support email, website chat and WhatsApp number at MessageMind so new tickets open there. Rebuild Zendesk macros and triggers as MessageMind automations or as answers in the knowledge base.
  • HubSpot. There is a native MessageMind HubSpot integration. Connect it on /integrations, approve the OAuth consent, and HubSpot contacts flow into MessageMind through contact-creation and property-change webhooks, with meeting booking available on your selected scheduler links. Rebuild HubSpot workflows that touched messaging (sequences, chatflows) as MessageMind automations; leave CRM-side workflows on HubSpot.
  • ManyChat. Export subscribers as CSV from ManyChat's audience view and import them into MessageMind. Reconnect Facebook, Instagram and WhatsApp directly to MessageMind so new conversations arrive there instead of ManyChat. Rebuild each ManyChat Flow as a MessageMind automation using the trigger that fires on contact or conversation events.
  • Tidio / Lyro. Export contacts and visitors from Tidio as CSV and import them into MessageMind. Replace the Tidio website widget with the MessageMind website chat snippet, reconnect your Messenger and Instagram inboxes, and rebuild Lyro's trained answers as MessageMind knowledge-base entries plus automations.
  • GoHighLevel. Export Contacts as CSV from the GHL sub-account and import into MessageMind. Repoint the phone number, email domain and website widget to MessageMind. GHL campaigns (SMS and email drips) are rebuilt as MessageMind automations; GHL pipeline stages stay in GHL if you keep it as the CRM, or move to HubSpot/Brevo and connect that.
  • Drift. Export Contacts and Conversations metadata as CSV from Drift. Swap the Drift playbook snippet on your site for the MessageMind website chat snippet, reconnect any email and calendar touchpoints, and rebuild Drift Playbooks as MessageMind automations keyed to the website-chat and lead-created events.
  • Crisp. Export People as CSV from Crisp and import into MessageMind. Replace the Crisp chatbox with the MessageMind website chat snippet and reconnect WhatsApp, Messenger and email. Crisp's bot scenarios become MessageMind automations; Crisp's canned responses become knowledge-base entries so the AI learns them once instead of being read verbatim.
  • Respond.io. Export contacts as CSV from Respond.io and import into MessageMind. Reconnect every channel Respond.io was fronting (WhatsApp Business Platform, Instagram, Messenger, SMS, email) directly to MessageMind so inbound messages route to the AI. Rebuild Respond.io workflows as MessageMind automations with the matching channel triggers.
  • Fin AI (Intercom's AI). Fin lives inside Intercom, so a Fin migration is an Intercom migration plus a knowledge move: export the Fin content library (articles, snippets) and re-ingest it as MessageMind knowledge-base entries. The AI then answers across every channel you connect, not only the Intercom Messenger.

Requirements

  • CSV export access on the legacy platform (every platform listed above exposes a contacts export, usually under Settings, Data or Export).
  • Or a matching MessageMind integration you can sync the legacy data through: HubSpot, Salesforce, webCRM, Brevo, Odoo, or Google Sheets contacts.
  • Admin access to each channel you want to repoint (WhatsApp Business account on Meta, Facebook Page, Instagram professional account, email domain DNS, website HTML or CMS footer).
  • A list of the automations, drips, sequences, playbooks or flows currently running on the legacy platform, so you know what to rebuild as MessageMind automations.

How to connect

  1. Inventory the channels and tools the legacy platform is fronting (website chat, WhatsApp number, Instagram DMs, Facebook Page, SMS number, support email, CRM, calendar) and write them down.
  2. Decide which channels stay on the legacy tool during cutover and which move first. A common pattern is to move website chat and Instagram/Messenger first, keep email on the legacy tool for one week as a safety net, then move WhatsApp last.
  3. Connect the chosen channels to MessageMind through Settings, Channels so new messages land in the MessageMind inbox. Verify each one by sending a test message end to end.
  4. Import contacts: either sync them through a matching integration (HubSpot, Salesforce, webCRM, Brevo, Odoo) or export a CSV from the legacy platform and import through Google Sheets contacts.
  5. Rebuild the legacy platform's automations, drips, sequences, playbooks or flows as MessageMind automations. Ingest FAQ articles and canned replies as knowledge-base entries rather than scripted messages so the AI phrases them in-conversation.
  6. Run both tools in parallel for a short window (usually two to seven days) with the legacy tool set to not auto-reply, so any stragglers are visible but do not double-send.
  7. Cut over: deactivate the legacy platform's channels, remove its website snippet, change the WhatsApp number owner on Meta Business, and leave the legacy account open in read-only mode for history.

AI agent use cases

  • A support team on Zendesk moves inbound email, website chat and WhatsApp to MessageMind, keeps Zendesk open for ninety days as an archive, and rebuilds the top ten macros as knowledge-base entries so the AI answers them in natural language.
  • An ecommerce brand on Tidio replaces the Tidio widget with the MessageMind website chat snippet, imports the Tidio contacts list through Google Sheets, and reconnects Messenger and Instagram directly to MessageMind.
  • A sales team on HubSpot keeps HubSpot as the CRM, connects the HubSpot integration so contact creation and property changes flow into MessageMind, and rebuilds HubSpot chatflow sequences as MessageMind automations.
  • An agency on GoHighLevel migrates one sub-account at a time: export contacts to CSV, reconnect the GHL-managed phone number to MessageMind, rebuild the SMS and email drip as a MessageMind automation, and leave the GHL pipeline for the client to keep using.

Example workflows

Migrate from Intercom in a weekend

  1. Friday morning. In Intercom, open Settings, Data, Export and queue a Contacts export and a Companies export. Note down every Intercom Series and Custom Bot that is live.
  2. Friday afternoon. In MessageMind, connect your website chat (replace the Intercom snippet with the MessageMind snippet in your site footer), connect WhatsApp through the Add WhatsApp wizard, and connect your support email forwarder.
  3. Friday evening. Import the Intercom contacts CSV into MessageMind through Google Sheets contacts, or sync them into HubSpot or Brevo first and connect that integration so the contacts flow in automatically.
  4. Saturday. Rebuild each Intercom Series as a MessageMind automation. Ingest the Intercom Help Center articles as MessageMind knowledge-base entries so the AI learns the content rather than reading canned replies.
  5. Sunday morning. Set Intercom to office-closed mode so it does not auto-reply, and run both tools in parallel for a day. Watch the MessageMind inbox to confirm every channel is landing new conversations correctly.
  6. Sunday evening. Deactivate Intercom's Messenger, email and WhatsApp channels, remove the Intercom snippet from the site (if it is still there), and keep the Intercom account open in read-only mode for the historical archive.

Replace a ManyChat broadcast with a MessageMind automation

  1. In ManyChat, open the Flow you want to replace and write down the trigger (keyword, button, tag, scheduled time), the message steps, the delays and the branching logic.
  2. In MessageMind, create a new automation and pick the matching trigger (contact-created, message-received on a specific channel, or a scheduled campaign).
  3. Recreate each ManyChat message step as an automation step. For free-form branches, let the AI handle the branching with knowledge-base content instead of writing explicit if/then rules.
  4. Export the ManyChat subscribers tagged by that Flow as a CSV and import them into MessageMind so the audience is already in the inbox before the automation runs.
  5. Run the MessageMind automation on a small test audience (five to ten contacts) and confirm the messages arrive on the correct channel with the correct cadence.
  6. In ManyChat, pause the original Flow and leave it paused for a few days as a rollback option. Once the MessageMind automation has run a full cycle without issues, delete the ManyChat Flow.

Limitations

  • Saved replies, canned responses and macros do not auto-migrate. They are rebuilt as MessageMind knowledge-base entries so the AI phrases them in context rather than copy-pasting a template.
  • Routing rules, assignment rules and SLA policies on the legacy platform do not auto-migrate. MessageMind's AI answers first and escalates when it cannot; the equivalent of 'route to team X' is an escalation rule, not a rule-based router.
  • Custom reports and dashboards do not auto-migrate. MessageMind reports on its own events (conversations, bookings, lead creation, campaign enrolment) and does not re-produce vendor-specific metrics.
  • Conversation history is intentionally not imported. Importing threads from Intercom, Zendesk or Respond.io would create duplicate contacts and distort analytics; keep the legacy tool open in read-only mode for the archive instead.
  • ManyChat and GoHighLevel subscriber tags do not have a one-to-one equivalent in MessageMind. Model them as contact properties on import, or as the trigger that enrols a contact into an automation.
  • Fin AI's answer tuning and feedback history stay in Intercom. Only the content library (articles, snippets) is portable, by re-ingesting it as MessageMind knowledge-base entries.

Troubleshooting

Contacts receive the same nurture message twice during cutover (one from the legacy tool, one from MessageMind).

The legacy platform's drip or series is still enrolled on those contacts. Pause every nurture, drip, series or flow on the legacy tool BEFORE enabling the matching MessageMind automation. Running both in parallel is only safe if the legacy side is set to read-only or office-closed.

Imported contacts are not merging with contacts already in MessageMind (duplicates appear).

The CSV import keys on the primary identifier (email or phone). Make sure the export from the legacy platform includes a clean, normalised email and E.164 phone column, and that it matches the identifier MessageMind already stored for that contact. If duplicates still appear, reconcile them in the matching integration (HubSpot, Brevo, webCRM) before re-importing.

Old conversation history is missing in MessageMind after cutover.

This is expected. MessageMind does not import legacy transcripts, because very few platforms expose a lossless export and importing them would create duplicate threads. Keep the legacy tool open in read-only mode for the archive and link to it from a contact note if a specific thread needs to stay reachable.