Skip to content
Sendora Cloud
Create account
Migrate from Intercom

Move from Intercom to Sendora.

Move Messenger + inbox + Help Center + Fin AI from Intercom to Sendora Support + Contact Widget + KB.

Total effort: 1-2 weeks depending on Series / Tour depth.

Step-by-step

  1. 1

    1. Export conversations + users + companies

    Intercom Data Export covers conversations, contacts, companies. Pull last 90 days. Tag mapping → Customer profile traits.

    2 hours
  2. 2

    2. Import tickets into Support

    Sendora Support bulk-import accepts Intercom's conversation shape. `contact_id` → Customer user_id. Custom attributes become traits.

    Half a day
  3. 3

    3. Migrate Help Center articles

    Intercom Articles export → Sendora KB import. Markdown + categories + URL slugs preserved. Public KB live at `sendoracloud.com/help/<orgSlug>`.

    Half a day
  4. 4

    4. Replace Messenger widget

    Drop Intercom Messenger script tag from your site. Add Sendora Contact Widget (~12 KB). Submissions land in Support inbox; AI chatbot (gpt-oss:20b on Ollama Cloud) answers from your imported KB — replaces Fin AI without separate billing.

    1 hour
  5. 5

    5. Rebuild Series → Sendora Automation

    Intercom Series export gives JSON of every flow. Port to Sendora Automation — branches, delays, wait-for-event all port directly. AI step type (generate / decide / extract) lets you collapse multi-step decision branches.

    1-2 days depending on Series count
  6. 6

    6. Migrate Product Tours

    Intercom Tours port to Sendora In-App Messages (tooltips + banners + modals). Visual editor + audience targeting + A/B variants from Experiments module.

    Half a day
  7. 7

    7. Cut over + sunset

    Run parallel for 1-2 weeks. Agents in Sendora inbox, Messenger widget still live as fallback. Once parity holds, swap widget DNS + cancel Intercom.

    1-2 weeks parallel run

Watch-outs

  • Intercom Messenger's polish + agent UX is years ahead — set agent expectations.
  • Intercom App Marketplace integrations (Salesforce sync, Shopify event ingest) port to Sendora webhooks + Workflows.
  • Fin AI's pricing motivates the switch — review per-conversation cost vs. Sendora's bundled AI chatbot.
Lands you on

Support

Ticket inbox + portal + inbound email pipeline + SLAs + canned replies + saved views — same tenant as your customer data + audiences + KB.

Zendesk lets you import CRM data. Sendora Support IS your CRM data. Tickets live in the same tenant as Auth, Customers, Analytics, and KB. The win is bundle + identity, not feature-parity with Zendesk: tickets + replies + public portal + a real inbound email pipeline (4 routing modes — reply-token + plus-addressing + BYOD + slug subdomain) + priority-based SLA policies + canned responses + saved views + CSAT survey + Contact Widget → ticket. Honest about what's NOT built: audience-routed SLAs, Slack Connect channel, assignment rules + round-robin, automatic CSAT → profile-trait flow.

Read full Support page

Stuck on the migration? We'll help.

Launch partners get white-glove migration help direct from the engineering team. Free plan covers real product use during the parallel-run period.

Create free accountBecome a launch partnerSide-by-side vs Intercom