Skip to main content

Migrate from Crisp to Hunch

This guide walks through every step of moving from Crisp to Hunch: replacing the widget, preserving what matters, reconnecting your tools, and validating the new setup before going live.

Before you start​

Hunch and Crisp are not identical products. Crisp is a help-desk and live chat platform. Hunch is a website AI operator — it answers, acts, books, fills forms, routes to humans, and runs across channels.

What you keep:

  • Your website visitors and their behavior (Hunch starts fresh with live traffic)
  • Your knowledge base content (export from Crisp, import to Hunch)
  • Your CRM connections (reconnected in Hunch)
  • Your human handoff workflows (rebuilt in Hunch's operator model)

What changes:

  • The chat widget on your site (one script tag replacement)
  • Your knowledge management approach (from article-based to retrieval-eval based)
  • Your reporting model (from inbox metrics to site analytics + influenced revenue)

Timeline estimate: Most teams complete the switch in an afternoon. Script replacement takes minutes. Knowledge migration and workflow tuning take the bulk of the time.

Step 1: Replace the Crisp script with Hunch​

This is the only step with a direct cutover. Plan for 5 minutes of downtime on the widget.

1a. Remove the Crisp snippet​

In your site's <head> or before </body>, find the Crisp installation script. It looks like this:

<script type="text/javascript">
  window.$crisp = []
  window.CRISP_WEBSITE_ID = 'YOUR_CRISP_WEBSITE_ID'
  ;(function () {
    d = document
    s = d.createElement('script')
    s.src = 'https://client.crisp.chat/l.js'
    s.async = 1
    d.getElementsByTagName('head')[0].appendChild(s)
  })()
</script>

Delete the entire block.

1b. Install the Hunch embed script​

Add this single script tag in the same location:

<script src="https://cdn.hunchbank.com/embed.js" data-website-id="YOUR_HUNCH_WEBSITE_ID"></script>

You can find your website ID in the Hunch dashboard under Settings > Installation.

1c. Verify the widget loads​

Open your site in a browser and confirm the Hunch widget appears. Open browser DevTools and check the console for any errors. The widget should show a chat button in the bottom-right corner.

Step 2: Migrate your knowledge base​

Crisp stores knowledge in Crisp Knowledge Base articles. Hunch uses a retrieval-based knowledge model — it indexes your actual website content rather than requiring a separate article database.

What to export from Crisp​

  1. Go to Crisp > Knowledge Base > Articles
  2. Export your articles — Crisp offers a CSV export under Settings > Data Export
  3. Save each article's content — especially:
    • Pricing and plan information
    • FAQ content
    • Product documentation
    • Onboarding guides

What to do with it in Hunch​

Hunch can ingest this content in two ways:

Option A: Add to your website pages (recommended) If the knowledge already lives on your site (pricing page, FAQ page, docs), Hunch will discover it automatically during its scan. No import needed.

Option B: Upload as reference documents For content that is not on your public website, use the Knowledge section in the Hunch dashboard:

  1. Go to Configuration > Knowledge
  2. Create a new retrieval source
  3. Paste or upload your article content
  4. Run a validation check to confirm the AI can find the right answers

Migration tip​

Start with the 5-10 most-used Crisp Knowledge Base articles. Validate that Hunch retrieves accurate answers, then expand.

Step 3: Handle chat history​

Hunch does not import historical chat transcripts from Crisp. This is intentional — Hunch is built around live visitor interactions and commercial outcomes, not a chat archive.

What to do with old transcripts​

  • Export from Crisp: Go to Crisp > Settings > Data Export > Conversations. Request a CSV export.
  • Store the export: Save it to your internal data warehouse, Google Drive, or a secure bucket.
  • Mark the cutover date: Note when you switched so your team knows which system to check.

What about ongoing conversations?​

Any active Crisp conversations at the time of cutover should be:

  1. Resolved or assigned in Crisp before removing the script
  2. Started fresh in Hunch — the visitor will see the Hunch widget on their next page load

Step 4: Reconnect CRM and integrations​

Hunch connects to the same CRM and tools you used with Crisp, but through Hunch's native integration layer.

HubSpot​

In the Hunch dashboard:

  1. Go to Extensions > HubSpot CRM
  2. Click Connect
  3. Enter your HubSpot private app token
  4. Map the data you want to sync: contacts, deals, company enrichment

Other tools​

Check the Extensions page in the Hunch dashboard for available integrations. Hunch also supports:

  • Webhooks for custom integrations
  • Slack notifications for handoffs and alerts
  • Email, Telegram, and WhatsApp channels

Step 5: Configure workflows and handoffs​

Crisp's workflow model is based on routing rules and chatbot flows. Hunch's model is intent-centric (detect intent, resolve or route).

Rebuild your most common flows​

Crisp flowHunch equivalent
FAQ chatbotKnowledge retrieval + rich response cards
Lead captureIntent detection + form-filling tool + CRM sync
"Talk to a human" buttonHandoff trigger — configure in Configuration > Triggers
Bot → Human escalationConfidence-threshold handoff in Configuration > Handoffs

Set up notifications​

  1. Go to Configuration > Notifications
  2. Configure Slack alerts for handoffs and high-intent visitors
  3. Set up email digests for daily/weekly summaries

Validate with a test run​

Before removing the Crisp script completely:

  1. Run Hunch side-by-side with Crisp on a staging environment
  2. Test each workflow path
  3. Verify handoffs reach the right team members

Rollback plan​

If something goes wrong, revert by:

  1. Removing the Hunch embed script
  2. Re-adding the Crisp snippet

Hunch does not modify your website's content, database, or server configuration.

FAQ​

Will I lose my chat history? No — you export it from Crisp before switching.

Can I run Crisp and Hunch at the same time? Yes, during a transition period. Run both widgets. We recommend a 1-2 week parallel run.

Do I need to change my DNS or server config? No. Hunch requires no DNS changes, no CNAME records, and no server-side modifications.

How long does the full migration take? Script replacement: 5 minutes. Knowledge migration: 1-2 hours. Workflow reconfiguration: 2-3 hours.

Can I import Crisp's chatbot flows into Hunch? Not automatically. Flows need to be rebuilt in Hunch's trigger + action model.