Intercom → Crisp

Plan mapping at the entry paid tier

The lowest non-free, non-custom tier on each side. Use this for the "if I'm on $X with Intercom, what's the equivalent on Crisp?" gut check.

Step-by-step migration

1. 01

   Export your list from Intercom

   Pull a fresh CSV of every active subscriber. Capture the fields you actually use downstream: email is required, name is standard, signup date and tier (free/paid) are useful when Intercom provides them.

2. 02

   Provision Crisp

   Sign up, set sender identity, and verify your sending domain (DKIM, SPF, DMARC). Do this before importing the list; sending from an unverified domain is the single fastest way to land in spam at the moment of cutover.

3. 03

   Import the list and map fields

   Upload the CSV. Map email + name + any custom fields. Decide whether to import as one list or split into segments/tags. Intercom-style organization rarely maps 1:1, so plan the split before the upload, not after.

4. 04

   Rebuild automations and templates

   Crisp's automation builder is structurally similar but won't import Intercom's flows directly. Rebuild only what you actively use; the move is a chance to delete the unused ones rather than lift-and-shift dead infrastructure.

5. 05

   Send a test broadcast

   Pick a small segment and send a real broadcast (not just a preview). Verify deliverability, link clicks, and unsubscribe flow. If anything's off, you find it before the announcement, not after.

6. 06

   Announce the move and cut over

   Send your last broadcast from Intercom announcing the new sender domain and what to expect. Cut over DNS and sending from Crisp on the same day, not staggered. A dual-send week creates more confusion than it prevents.

Intercom-to-Crisp specific gotchas

Universal steps cover most of the work. These are the failure modes unique to this exact pair.

• #1

  Intercom conversations export as JSON via the API; Crisp's import wizard accepts a structured format. Plan a freeze window of 24 to 48 hours where both inboxes are watched, then point new conversations at Crisp once the historical import settles.

• #2

  Intercom user segmentation is event-property-driven; Crisp's segmentation is simpler (tags, last-seen, location). Audit which Intercom segments are load-bearing before assuming they translate.

• #3

  Intercom's Resolution Bot / Fin AI Agent ticket-deflection logic does NOT translate. If you've built deflection workflows, expect to either rebuild simpler versions in Crisp's MagicReply or accept higher human-handled ticket volume post-migration.

• #4

  Webhooks and integrations are vendor-specific. Slack, Zendesk Sell, HubSpot, and Salesforce all need to be reconnected on the Crisp side. Test critical handoffs (lead-routing, ticket-creation) before cutover.

• #5

  Mobile SDKs differ. If you ship the Intercom Messenger inside an iOS or Android app, swap to Crisp's mobile SDK well before the cutover; SDK migration is the slowest part of any chat-tool move.

• #6

  Subscription cancellation: Intercom contracts often have annual commitments. Match the migration date to the renewal cycle to avoid paying both tools simultaneously for an extended period.

Common questions

Is Crisp cheaper than Intercom?

At the entry tier, yes: Crisp starts at Free while Intercom starts at $29/mo. Pricing scales differently above that, so check the side-by-side plan grid for your specific contact count.

Will my data transfer cleanly?

Most live chat data transfers, but rarely 1:1. The "Pair-specific gotchas" section above is hand-curated for this exact migration: it covers what exports from Intercom, how it imports into Crisp, and which structural pieces (workflows, integrations, custom domains) require rebuild rather than direct port. The constraint usually isn't the data export; it's the rebuild work for anything Crisp models differently.

How long does the migration take?

A clean migration for this pair is typically 1-2 weeks of focused work: data export, integration reconnection (CRMs, webhooks, payment processors), feature rebuild for whatever doesn't port directly, test run, cutover. The constraint is rarely the export itself; it's the integration reconnection and the rebuild work for any feature that Crisp models differently from Intercom.

Are Intercom and Crisp direct competitors?

Yes. Both are primarily live chat tools, which is why this is a defensible head-to-head migration rather than a cross-category consolidation.

Where can I see Intercom vs Crisp side-by-side?

The /compare/crisp-vs-intercom page on TierGauge shows side-by-side plans, headline pricing, included features, and limit comparison at the entry paid tier. This migration guide is the long-form decision narrative; the compare page is the data-only dashboard.