Migrating from Tidio, Intercom, or Chatbase to Wengrow

A step-by-step guide for operators switching chatbot platforms. Honest about what moves, what doesn't, and what typically takes an afternoon.

Most "migration guides" for SaaS are really data-portability docs — how to export years of records and re-import them without losing anything. Chatbot migrations are different. Most of the value in a chatbot platform isn't records you've accumulated; it's the knowledge base you pointed it at, the widget placement on your site, and the downstream CRM integration that catches leads. All three of those are easy to recreate on a new platform. That's why this guide exists — and why it's short.

What actually needs to move

Three things:

1. The knowledge base content. The documents, URLs, FAQ entries, or Q&A pairs that taught your current bot to answer. You either export them from your current platform or re-point Wengrow at the same source URLs. Either way, Wengrow rebuilds the index from scratch using hybrid retrieval — you don't move vector data between tools.
2. The widget placement. Your current platform has a one-line script tag on your site. You swap it for Wengrow's one-line script tag. Done.
3. The CRM integration. If you've wired your current platform into HubSpot, Salesforce, or a webhook, you re-wire Wengrow. Wengrow has native Salesforce and HubSpot sync at Growth and above, so for most operators this is a handful of clicks, not a build.

That's it. If a migration document is promising you more than that, ask them exactly what "more" means in field-mapping terms.

What does not move — and why you should not care

We get asked about two other categories. Both deserve an honest answer.

Conversation history. Your current platform has a log of every conversation the bot ever had. Wengrow does not ingest that log. Importing transcript data from a different bot would be a practical and compliance headache — different schemas, different message formats, different retention rules, different PII handling — and it would not make your new bot smarter because the historical conversations were with a different model and a different knowledge base. The value of past conversations is already in the data you extracted from them: captured leads (which live in your CRM), content improvements to your knowledge base, and tuning to your prompts. You already own all three.

Lead pipeline. If you've been capturing leads through your old chatbot, those records belong in your CRM — HubSpot, Salesforce, or whichever system is the system of record for sales. That's where they were when your old bot was live; that's where they'll stay. Wengrow writes new leads into the same CRM from day one. We do not re-import historical leads from the old platform because your CRM already has them.

If a vendor is telling you they can migrate conversation history or lead pipeline from a competitor, ask to see the field-mapping document and a live demo with real data. What typically happens is a shallow import that breaks on edge cases and creates duplicates in your CRM. We'd rather be straight with you.

Now the per-vendor specifics.

Migrating from Tidio

Tidio is strongest in e-commerce live chat + its Lyro AI bot. Operators leaving Tidio for Wengrow are typically moving from a live-chat-with-AI setup to a purpose-built B2B lead-capture flow. See Wengrow vs Tidio for the category framing.

Step 1 — Export your knowledge base content. Tidio's FAQ / knowledge-base content is managed inside their admin panel. Their docs describe how to export FAQs and automations; the current export path lives under their help center. If you built your current bot by pointing Tidio's Lyro at a URL, the "export" step is trivial — just note the URLs; Wengrow will crawl them directly.

Step 2 — Start your Wengrow trial. 14 days, no credit card. During onboarding, paste the same URL your old bot crawled. The auto-setup wizard drafts an agent from your site content; you review the qualification fields and the system prompt before anything goes live.

Step 3 — Upload any non-URL KB content. FAQ exports typically come out as CSV or JSON. Open them; paste the Q&A pairs into Wengrow's knowledge base as manual entries, or convert to a markdown doc and upload the file. Hybrid retrieval handles mixed-source content well.

Step 4 — Swap the embed snippet. Tidio's script tag comes out; Wengrow's one-line JS goes in. Same install location (typically a global footer or <head> tag in your site template). Most site builders let you do this in one save.

Step 5 — Run both for a week. Seriously. Put Wengrow on one page (or on a staging subdomain) and keep Tidio live on the rest. Compare lead quality and volume after 7 days. Only then decide.

Step 6 — Cancel Tidio. Tidio's monthly plans are flexible — cancellation does not typically require a sales-assisted motion. Check your specific contract; if you're on an annual plan, time the switch so you don't overlap costs.

Typical elapsed time, start to finish: an afternoon of setup, a week of parallel running, five minutes to cancel.

Migrating from Intercom

Intercom is a different category — it's a mature support platform with the Fin AI layered on top. Operators leaving Intercom for Wengrow are typically changing the job: moving from support-ticket deflection to net-new lead generation. See Wengrow vs Intercom for the category framing and why the pricing models are different on purpose.

Step 1 — Understand which Intercom contract you're on. Intercom's paid plans are often annual, and Fin charges are typically per-resolution on top of the core subscription. The cancellation timing matters more here than with Tidio. Look at your renewal date before you plan the cutover.

Step 2 — Export your help center / knowledge base. Intercom's help center articles can be exported — their platform supports article export in common formats. If your bot relied on your help-center articles, save them locally (HTML or markdown). You will re-upload those into Wengrow's knowledge base, or point Wengrow at the public URLs of your help center if they're indexable.

Step 3 — Export or snapshot your Fin configuration. Fin typically has custom prompts, conversation routing rules, and connected actions. These are not "moved" — they are re-implemented in Wengrow's agent config during onboarding. Take notes on what Fin was doing (which paths routed to humans, what qualification fields were collected). The auto-setup wizard handles most of this; you tune the qualification fields to match.

Step 4 — Start your Wengrow trial. 14 days, no credit card. Paste your marketing-site URL (the one visitors land on when they might fill a form). Auto-setup drafts an agent; you review and adjust.

Step 5 — Swap the widget snippet on your lead-capture pages. Keep Intercom live on your support / in-app surfaces during the trial — they're solving different jobs. Only swap Intercom for Wengrow on the marketing pages where you want net-new lead capture. Many operators end up running both platforms indefinitely for this reason.

Step 6 — Wire Wengrow to your CRM. If you were using Intercom-to-HubSpot or Intercom-to-Salesforce sync, wire up Wengrow's native CRM integration. Takes a few minutes per CRM.

Step 7 — Plan the Intercom contract change at renewal. If Intercom is still doing a support job that Wengrow doesn't replace, keep it. If you're fully replacing it, time the cancel to align with your renewal. Intercom's renewal cliff is real — don't let auto-renew catch you.

Typical elapsed time, start to finish: an afternoon of setup, a week of parallel running, a longer window if you're waiting on a renewal date.

Migrating from Chatbase

Chatbase (and the broader SMB AI chatbot category — Chatsimple, SiteGPT, and similar tools) are the easiest migration. These platforms are intentionally simple: point at a URL, get a bot, paste an embed. Switching platforms is the same simple thing in reverse. See Wengrow vs Chatbase for the positioning.

Step 1 — Export your KB content. Chatbase's chatbot settings let you view and export the sources you uploaded (URLs, files, Q&A pairs). For URL-based bots, just note the URLs. For file-based bots (PDFs, Word docs), download the files — you'll re-upload them into Wengrow.

Step 2 — Snapshot your system prompt and Q&A pairs. Chatbase exposes the system prompt / instructions you gave the bot. Copy it. You'll paste a refined version into Wengrow during setup — though the auto-setup wizard typically drafts a better one from your actual site content.

Step 3 — Start your Wengrow trial. 14 days, no credit card. Auto-setup from your URL, or upload the files you exported from Chatbase.

Step 4 — Tune the qualification fields. This is where Wengrow is materially different from Chatbase. Chatbase asks for an email and maybe a name. Wengrow's lead qualification state machine can extract multiple fields through natural conversation, handle declines, and write structured records to your CRM. Spend 15 minutes configuring the fields that matter for your sales process.

Step 5 — Swap the embed. One-line JS change, same as Chatbase.

Step 6 — Cancel Chatbase. Chatbase's trial-cancellation flow is self-serve; monthly plans are flexible. If you're on an annual plan, time accordingly.

Typical elapsed time, start to finish: one to two hours of setup, optional week of parallel running.

The same-day checklist

Whichever platform you're leaving, the setup is the same shape:

Where to start

If you're actively evaluating Wengrow during an in-flight contract with another vendor:

• If you're leaving Tidio: start the Wengrow trial and run both in parallel on a single landing page for a week. Compare lead volume and quality.
• If you're leaving Intercom: start the trial on your marketing-site surfaces only. Keep Intercom on in-app / support until renewal. Many teams end up running both long-term.
• If you're leaving Chatbase / Chatsimple / SiteGPT: start the trial and cut over whole-site within a day or two — the category's setup simplicity cuts both directions.

Everything is a 14-day free trial with no credit card. The fastest way to know if migration is worth it is to run real traffic through both bots and look at the leads at the end.