Switching from Chatbase

Moving from Chatbase to ClerkChat

This is the least painful move of any on this list, because both products work from the same raw material: your site, your documents, your question-and-answer pairs. There are no flows to rebuild, only sources to re-point.

Realistic time: About an hour
The catch: Easiest

What you lose

The question everyone actually has, answered first.

Conversation historyPast chats stay in Chatbase. Export anything you want for reference before you close the account, because you will not get it afterwards.
API integrations built against ChatbaseIf you called their API from your own code, that code needs rewriting. For most people this is nothing; for anyone who built on Chatbase as a component it is the bulk of the work.
Your unused credit balanceCredits are not transferable and are not usually refundable. Time the switch for the end of a billing period.

What carries across

Every training source, unchangedBoth products crawl a site and accept uploaded documents. Whatever you fed Chatbase, feed us the same thing. If you kept a folder of PDFs and help pages, that folder is your migration.
Your question-and-answer pairsChatbase lets you add explicit Q&A. Export them and paste them in; they are a strong source because they encode answers you already decided were correct.
The widget position on your siteBoth embed with a single script tag. Swap the snippet and the widget stays where your visitors already expect it.

How to do it

1
Collect your sourcesList the URLs Chatbase crawls and gather the documents you uploaded. This is the only genuinely manual part.
2
Point ClerkChat at the same materialGive us the site URL and upload the documents. Training takes minutes, not hours.
3
Ask it the ten questions you get mostCompare the answers against what Chatbase gives you. If ours are worse, the gap is almost always a missing source rather than the model.
4
Add the channels Chatbase could not reachConnect WhatsApp, Instagram, Messenger or Telegram, or publish the hosted page. This is the part that was not available to you before.
5
Swap the widget snippet, then cancelReplace the script tag on your site. Leave Chatbase running for a few days if you want a fallback, then close it at the end of the period.

What catches people out

Answer quality is about your sources, not the switchIf Chatbase was answering badly, moving will not fix it. Both products are limited by what you wrote down. Use the move as a reason to fix the thin pages in your help centre, which is the change that actually improves answers.
Check the pricing crossover honestlyAt low volume a small Chatbase credit plan genuinely costs less than a flat plan. The flat model wins as usage grows. Work out which side of that line you are on before moving for cost reasons.

When not to move

If any of these describe you, staying with Chatbase is the right call and we would rather say so than sell you a migration you regret.

Your customers only ever reach you through your website, so multichannel buys you nothing
You built on the Chatbase API and the integration work outweighs the benefit
Your volume is low and a small credit plan is cheaper than a flat plan

Questions

How long does moving from Chatbase actually take?: About an hour for most people, and most of that is gathering the documents you already gave Chatbase. There are no flows or rules to rebuild because neither product uses them.
Can I bring my conversation history?: No. Past conversations stay in Chatbase, so export anything worth keeping before you close the account. Training material is what matters for answer quality, and that moves fine.
Can I run both while I test?: Yes, and it is the sensible approach. Keep the Chatbase widget live on your site and use our hosted page or a messaging channel to test ours, then swap the snippet once you are satisfied.

Moving from something else

Re-point your sources and see the difference

Train on the same material in minutes. Free plan, no card needed.

Start free See pricing