Skip to main content

Migrate from Tawk.to to Hunch

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

Before you start​

Hunch and Tawk.to are not identical products. Tawk.to is a free live chat and support 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 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 approach to visitor engagement (from manual live chat to AI-led with human handoff)
  • Your reporting model (from chat metrics to site analytics + influenced revenue)

Timeline estimate: Most teams complete the switch in an afternoon. Script replacement takes minutes. Workflow tuning takes the bulk of the time.

Step 1: Replace the Tawk.to script with Hunch​

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

1a. Remove the Tawk.to snippet​

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

<!--Start of Tawk.to Script-->
<script type="text/javascript">
  var Tawk_API = Tawk_API || {},
    Tawk_LoadStart = new Date()
  ;(function () {
    var s1 = document.createElement('script'),
      s0 = document.getElementsByTagName('script')[0]
    s1.async = true
    s1.src = 'https://embed.tawk.to/YOUR_TAWK_WIDGET_ID/default'
    s1.charset = 'UTF-8'
    s1.setAttribute('crossorigin', '*')
    s0.parentNode.insertBefore(s1, s0)
  })()
</script>
<!--End of Tawk.to 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​

Tawk.to does not have a built-in knowledge base. Most Tawk.to users either rely on agents manually answering questions or use a separate knowledge management tool. Hunch uses a retrieval-based knowledge model — it indexes your actual website content.

What to bring into Hunch​

If you had FAQ content managed outside Tawk.to (in a separate tool, Google Doc, or on your website):

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 FAQ content
  4. Run a validation check to confirm the AI can find the right answers

Migration tip​

If you do not have a written knowledge base, this is a good opportunity to create one. Start with the 10 questions your team answers most often in Tawk.to.

Step 3: Handle chat history​

Hunch does not import historical chat transcripts from Tawk.to. This is intentional — Hunch is built around live visitor interactions and commercial outcomes.

What to do with old transcripts​

  • Export from Tawk.to: Go to Tawk.to > Dashboard > History and export conversations (CSV format).
  • 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 Tawk.to conversations at the time of cutover should be:

  1. Resolved or assigned in Tawk.to 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 Tawk.to, 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​

Tawk.to's model is primarily manual live chat (agents respond in real time). Hunch's model is AI-first with human handoff.

Set up your first workflows​

Tawk.to interactionHunch equivalent
Live agent chatAI response + confidence-threshold handoff
Offline contact formForm-filling tool + email notification
Proactive chat inviteIntent-triggered engagement — configure in Configuration > Triggers
"Talk to a human" buttonHandoff trigger — configure in Configuration > Triggers

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 Tawk.to script completely:

  1. Run Hunch side-by-side with Tawk.to 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 Tawk.to 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 Tawk.to before switching.

Can I run Tawk.to 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 is Hunch different from Tawk.to? Tawk.to is a free live chat tool where agents respond manually. Hunch is an AI operator that handles conversations autonomously and only involves humans when needed.

How long does the full migration take? Script replacement: 5 minutes. Knowledge setup: 1-2 hours. Workflow configuration: 1-2 hours. Most teams complete everything in half a day.