Migrate from Tidio to Hunch
This guide walks through every step of moving from Tidio to Hunch: replacing the widget, preserving what matters, reconnecting your tools, and validating the new setup before going live.
Before you start
Hunch and Tidio are not identical products. Tidio is a customer service chat platform with AI chatbots. 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 Tidio, 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 chatbot approach (from flow-based to intent-based)
- 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. Knowledge migration and workflow tuning take the bulk of the time.
Step 1: Replace the Tidio script with Hunch
This is the only step with a direct cutover. Plan for 5 minutes of downtime on the widget.
1a. Remove the Tidio snippet
In your site's <head> or before </body>, find the Tidio installation script. It looks like this:
<script src="//code.tidio.co/YOUR_TIDIO_PUBLIC_KEY.js" async></script>
Delete the entire line.
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
Tidio stores knowledge in Lyro AI training data and chatbot flows. Hunch uses a retrieval-based knowledge model — it indexes your actual website content rather than requiring a separate article database.
What to export from Tidio
- Go to Tidio > Lyro AI > Training
- Review the questions and answers Lyro was trained on
- Export or copy your chatbot flows from Tidio > Chatbots > Flows — especially:
- FAQ answers
- Product and pricing information
- Shipping and return policies
- Common customer questions
Tidio does not offer a bulk knowledge export. Review and copy your Lyro training data and flow content manually.
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:
- Go to Configuration > Knowledge
- Create a new retrieval source
- Paste or upload your training content
- Run a validation check to confirm the AI can find the right answers
Migration tip
Start with the most common questions your Tidio Lyro AI was handling. Validate that Hunch retrieves accurate answers before migrating the rest.
Step 3: Handle chat history
Hunch does not import historical chat transcripts from Tidio. 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 Tidio: Go to Tidio > Settings > Export Data. Tidio will generate a CSV export of your conversations.
- 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 for historical vs. new conversations.
What about ongoing conversations?
Any active Tidio conversations at the time of cutover should be:
- Resolved or assigned in Tidio before removing the script
- 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 Tidio, but through Hunch's native integration layer.
HubSpot
In the Hunch dashboard:
- Go to Extensions > HubSpot CRM
- Click Connect
- Enter your HubSpot private app token
- 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
Tidio's workflow model is flow-based (drag-and-drop chatbot builder). Hunch's model is intent-centric (detect intent, resolve or route).
Rebuild your most common flows
| Tidio flow | Hunch equivalent |
|---|---|
| FAQ chatbot | Knowledge retrieval + rich response cards |
| Lead capture | Intent detection + form-filling tool + CRM sync |
| "Talk to a human" button | Handoff trigger — configure in Configuration > Triggers |
| Product recommendations | Knowledge retrieval + rich response cards |
| Bot → Human escalation | Confidence-threshold handoff in Configuration > Handoffs |
Set up notifications
- Go to Configuration > Notifications
- Configure Slack alerts for handoffs and high-intent visitors
- Set up email digests for daily/weekly summaries
Validate with a test run
Before removing the Tidio script completely:
- Run Hunch side-by-side with Tidio on a staging environment
- Test each workflow path
- Verify handoffs reach the right team members
Rollback plan
If something goes wrong, revert by:
- Removing the Hunch embed script
- Re-adding the Tidio snippet
Hunch does not modify your website's content, database, or server configuration. The entire integration is a single script tag.
FAQ
Will I lose my chat history? No — you export it from Tidio before switching.
Can I run Tidio 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 Tidio's chatbot flows into Hunch? Not automatically. Flows need to be rebuilt in Hunch's trigger + action model.