Migrate From tawk.to or Tidio to Another Website Chat Without Losing Conversations or Visitors
Switching website chat is scary: history, contacts, the script, the team. A 7-step migration plan with exports, a brief overlap and a clean cutover.
In this article
Nobody wants to migrate from tawk.to or Tidio on a Friday. The chat has been on the site for years, the team knows the shortcuts, and somewhere in there are thousands of conversations with customers who may come back. The fear is specific: lose the history and the contacts, break the script, confuse visitors with two bubbles, retrain everyone under pressure.
All of that is avoidable if you treat the switch as a data-and-cutover project rather than a script swap. Here is the seven-step version for a business moving from a free or basic website chat to an omnichannel platform where the chat sits next to email, SMS and WhatsApp. The example throughout is a Tampa, Florida outdoor-gear store leaving tawk.to after three years.
Before you start: what you can and cannot bring
The honest answer to "will we lose anything?" is "a little, and here is exactly what."
| Asset | Can it be migrated? | How |
|---|---|---|
| Contacts with an email or phone | Yes | Export CSV; import into the new CRM (CSV, API or n8n) |
| Transcripts attached to a known contact | Partly | Export; store as a file or note on the contact record, not as live threads |
| Anonymous transcripts (no contact details) | No, as conversations | Keep the export as an archive; they will not appear in the new inbox |
| Canned responses / shortcuts | Yes, manually | Copy the ten you actually use |
| FAQ and bot answers | Yes, and improve them | Turn them into the AI agent's knowledge base |
| Widget look (colors, position, name) | Yes | Reproduce in the appearance settings |
| Conversations open on cutover day | No | Announce the change; the new tool starts fresh |
The "no" rows are the ones people fight. Anonymous logs are useful for finding your real FAQs (step 5), but they were never customer records. Archive and move on.
Step 1: export history and contacts from the current provider
Export everything the current tool allows, in CSV where possible: contacts, transcripts, tags and custom fields. tawk.to and Tidio both offer exports from their dashboards; menu names change, so use their help center for the current path. Do it twice: now for planning, and on cutover day.
Save the exports in a dated shared folder, and note what your current plan includes so you can confirm the new one covers it; check each provider's pricing page today. tawk.to pricing · Tidio pricing · Crisp pricing.
Details verified on 14-09-2026 from each provider's public pages; they may change without notice.
Step 2: import contacts into the CRM
Clean the CSV first: one row per person, a valid email or phone in the right column, tags mapped to the new names. Drop rows with no contact method; they cannot be matched later anyway.
In Omnifox, contacts import from CSV into the CRM; for larger or ongoing syncs use the API, webhooks or n8n. Tag every imported contact "migrated-from-tawk" so you can later tell which relationships predate the switch. The Tampa shop imported two years of customers who had left an email and attached transcripts as notes.
Step 3: rebuild the widget so visitors do not notice
Continuity is the goal: same corner, colors, name, similar greeting. Screenshot the old widget and reproduce it in the appearance settings: primary and accent color, position, button size and shape, header avatar, welcome message, light/dark mode. Turn off the "powered by" mark if the plan allows.
Then re-create the old bot's behavior with triggers: the homepage greeting, the "need sizing help?" bubble on product pages, the exit-intent message on the cart, each once per session. If the old pre-chat form had four fields, cut it to one or two.
Step 4: install through GTM and decide on the overlap
Install the new loader through Google Tag Manager so you can switch it on and off without touching the theme. The install is one line:
<script src="https://omnifox.io/widget/loader.js" data-widget-key="YOUR_KEY" async></script>
Now the overlap question. Both widgets on one page means two bubbles and visitors choosing at random; avoid it. Two clean options:
- No overlap (recommended). Test the new widget on a staging domain or one low-traffic page for a few days; the dashboard shows which domains it is installed on and when it was last seen. Then cut over in one go.
- Short overlap on separate pages. New widget on blog and help pages, old one on product and checkout pages, for a few days at most. In GTM that is two tags with page-path triggers.
The Tampa shop chose the first: new widget on a /help subpage for four days, then the switch.
Step 5: build the AI knowledge base from real questions
Your exported transcripts are the most honest FAQ you will ever get. List the questions that repeat (shipping to Puerto Rico, return window, sizing, "is this in stock") and write clean answers. Upload them with your policy pages and catalog to the AI agent's knowledge base, and set the response strategy: "always", or "first message only" if a human picks up after the greeting.
Run the twenty most common questions through the simulator before publishing. Where the old bot had a decision tree, the AI gives a plain answer plus a handoff when unsure:
Visitor: I ordered a tent last week, can I still return it if I haven't opened the box?
AI agent: Yes. Unopened items can be returned within 30 days of delivery for a full refund; shipping back is on us for orders over $75. I can start the return now if you share the order number, or send you the prepaid label by email.
Step 6: train the team on the differences, not the whole product
Two hours, not two days. Focus on what changed: where conversations land (a shared inbox that also holds email and WhatsApp), how assignment works (departments and distribution rules), how to continue by SMS or WhatsApp once you have a phone number, and how to hand a conversation to the AI or take it back. Have each agent run a test chat from a phone.
Step 7: cut over and measure the first two weeks
Cutover-day checklist, in order:
- Take the final export from the old tool.
- Pause or unpublish the old tag in GTM (or delete the old script from the theme).
- Publish the new tag site-wide.
- Send a test message from a phone on the homepage, a product page and the cart.
- Check the four widget events (loaded, opened, conversation started, message sent) appear in the dashboard funnel and in GA4 via
dataLayer. - Keep the old account readable for a month, then close it.
For two weeks, compare the funnel week over week (not against the old tool's numbers, measured differently) and read every AI transcript for wrong answers. The Tampa shop's first correction was a Puerto Rico shipping line the old bot had handled with a canned reply nobody exported.
Frequently asked questions
Can I import old chat transcripts into the new website chat?
Transcripts tied to a contact with an email or phone can be stored on that contact as a note or file, not as live conversations. Anonymous transcripts cannot be matched to anyone; archive them outside the new tool.
Should I run the old and new chat widgets at the same time?
Avoid both on the same page; visitors see two bubbles. Test the new widget on a staging domain and cut over in one step, or split by page in Google Tag Manager for a few days at most.
How do I keep the same look so visitors are not confused?
Screenshot the old widget and match color, position, button shape, name and greeting in the new appearance settings. Keep the same proactive messages on the same pages for the first month.
What happens to conversations that are open on cutover day?
They end in the old tool. Announce the change in the old widget the day before, and have the new welcome message tell returning visitors they can pick up where they left off by leaving their email.
Move the customers, not the clutter
A website chat migration from tawk.to, Tidio or Crisp comes down to one export, one clean import, a matching widget, a knowledge base built from real questions and a single-step cutover. The anonymous logs stay behind; the customers and the answers come with you. If the destination is a platform where the website chat shares an inbox with email, SMS and WhatsApp, follow the same steps on a 7-day free trial and check the pricing page for your team size. Before launch, review 10 mistakes when adding chat to your website.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-

How to Close a Sale on WhatsApp Step by Step (Practical Guide)
-

How to Integrate Notion With Your CRM and Workflows
-
Handling STOP, HELP and Opt-Out Management the Right Way
-

How Much Does an AI Agent Cost? Understanding Token Usage
-

Signs Your WhatsApp Number Is About to Be Banned
-

Coexistence for Businesses That Won't Give Up Their Number
-

Short Codes vs Long Codes in SMS: Which One to Choose
-

Co-Browsing + Video Call: Complete Visual Support
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.