Importing from Tidio

Updated Nov 20, 202615 min read
English
On this page

Bring your Tidio tickets, live chats, contacts and Lyro knowledge into Deskwoot with your Tidio API key. Everything comes over by default, and you can choose to import less. The import runs in the background, keeps going through Deskwoot updates and can be started again safely. Nothing in your Tidio project changes. Tidio hands out part of each day's data only on the next day, so start the import again the next day to bring in the rest.

What comes over

  • Tickets become conversations with every message, internal notes (as private notes), attachments, subject, status and priority. Tidio's priorities Low, Normal and High become Low, Medium and High. The department becomes the team and the agent the assignee (see below). Ticket tags become labels, and ticket custom fields become custom attributes with their values.
  • Deskwoot tickets: if your workspace uses tickets (your plan includes them and they are switched on under Settings > Tickets), each Tidio ticket also becomes a Deskwoot ticket next to its conversation. The ticket takes over the status, priority, subject, team and agent. Its conversation keeps every message, is resolved as the handover and shows a private card that names the ticket. Without tickets, the conversation keeps Tidio's status.
  • Live chats become conversations, one per chat, with their messages and the files sent in them, also the chats of visitors who never left an email. Messages of Tidio's bots (Flows, Workflows and Lyro) arrive without an agent. The first agent who answered becomes the assignee.
  • Satisfaction ratings of tickets and live chats, with the customer's comment, become CSAT ratings on the matching conversation.
  • Contacts with their name, email, phone, language, country, city and email consent. Contact properties become custom attributes with their values. Notes your agents added about a visitor become contact notes. A visitor without a Tidio contact gets a contact of their own.
  • Departments become teams, except "General", which in Tidio holds every agent. Agents are matched to your teammates by email (see below).
  • Lyro knowledge: the questions and answers that Lyro, Tidio's AI agent, answers from become articles of a new help center called "Tidio Lyro knowledge", for your team only (see "What stays internal").

Files and images

The import copies every file Tidio hosts into Deskwoot: ticket attachments, images and files inside ticket messages, files sent in live chats and the images in Lyro's answers. Nothing stays a link to Tidio, so your files keep working after you leave Tidio. A link in a Lyro answer that leads to your Tidio help center keeps only its text, because that page goes away with your Tidio account. If your workspace has booked the Virus scan, every file is scanned before it is stored.

  • If a file cannot be copied right now (Tidio does not answer even after several tries, or the virus scanner or Deskwoot's storage cannot be reached), the import ends with Imported partly. Start the import again to copy it. When 3 files in a row from the same server do not arrive, the run skips that server's files for 2 minutes and then tries one of them again. If that file arrives, the run carries on with the server's files. If not, it waits another 2 minutes. That way a server that does not answer cannot hold up the whole import, and the next run tries the skipped files again.
  • A file that no run can copy is left out, and the import still finishes. This includes a file that could not be reached in 3 runs, so a server that never answers cannot keep your import at Imported partly. Only runs in which the file could not be reached count, not runs in which the virus scanner or the storage was down. The count starts over when the last of those runs was more than 7 days ago, and deleting any import of your workspace clears it.
  • Each import in Import History lists these files under Files not imported with the reason, for example too large (over 25 MB), a file type that is not allowed, refused by the virus scan or no longer available at Tidio.
  • Images that a message or an article loads from another website, such as your own, stay as they are.

What does not come over

  • Canned responses (Tidio calls them Macros), Flows, Workflows and saved views. Tidio has no API for them.
  • Organizations, because Tidio has no companies.
  • Customer tags, profile pictures of contacts and the members of each department. No Tidio API gives them, so add your teammates to the teams in Deskwoot.
  • Your Tidio help center, because Tidio has no API for it. An article you switched on for Lyro or Copilot comes with Lyro's knowledge, as far as Tidio lists it there.
  • Files you uploaded to Lyro, such as PDFs. Their questions and answers come, the file itself does not.
  • Internal notes in live chats, because Tidio's APIs do not mark them as notes. Internal notes in tickets come as private notes.
  • The CC and BCC of email tickets.
  • Tickets in Tidio's spam folder and tickets you deleted. Tidio deletes a ticket it merges into another, and its messages come with that other ticket.
  • The pages a contact viewed, the links into your Tidio panel, the channel a live chat came through, and whether a rating was for an agent or for Lyro.

What stays internal

Lyro's knowledge is what Tidio's AI agent answers from, not a page for your customers. So the import keeps it for your team:

  • Every category of the "Tidio Lyro knowledge" help center is Team only: one for each Lyro folder, with its subfolders below it, and one called "Lyro Q&A" for the questions outside any folder.
  • Questions and answers that Lyro or Tidio's Copilot uses arrive published. The ones switched off in Tidio arrive as drafts.
  • A new import of the same project makes these categories team only again and moves an article your team put into a category For customers back into its Lyro category.

Team only articles are visible only to your team in the dashboard: in the Help Center, pick "Tidio Lyro knowledge" and Team only. Customers, the chat widget and Fynn, the AI bot, never see them, and Copilot uses the published ones when it answers your team. More in For customers and team only articles.

Before you start

  1. Check your Tidio plan: Tidio documents its API for the Plus and Premium plans. If Tidio does not allow API access for your project, Deskwoot tells you so when you start the import.
  2. In Tidio, open Settings > Developer > Tidio APIs as the project owner or an admin.
  3. Click Generate API key and copy the Client ID and the Client secret. Tidio shows the secret only once.
  4. Invite your teammates to Deskwoot with the same email they use in Tidio. You can also do this later.
  5. For imported tickets to land in an inbox, set up your email, Telegram, WhatsApp or SMS inboxes first.

How to import

  1. In Deskwoot, go to Settings > Import & Migration. Only admins can import.
  2. Under Where does your data come from?, pick Tidio.
  3. Paste the Client ID (it starts with ci_) and the Client secret (it starts with cs_).
  4. Under What should come along?, choose what comes over. Everything is on by default. To import only newer conversations, pick a day under Only conversations created on or after.
  5. Under Which inbox should the conversations go to?, pick an inbox for each kind (Email, Chat, Web forms and help center, Phone, WhatsApp, SMS, Everything else), or leave No inbox. This is for your Tidio tickets: live chats get no inbox. Only email, Telegram, WhatsApp and SMS inboxes are offered. If your workspace has exactly one email, WhatsApp or SMS inbox, it is already picked for that kind.
  6. Click Start Import. Deskwoot first checks the Client ID and the Client secret with Tidio. If Tidio refuses them, the panel says so and nothing starts.

While the import runs

  • The import runs in the background, so you can close the page. The import page shows the step it is on and how many records are done. After a few minutes of measuring, it also shows the speed. Under How fast the import goes, it shows how many API calls per minute your Tidio account allows and how many of them the import uses at most.
  • Tidio limits the API calls of each project per minute (its docs name 60 on Plus and 120 on Premium). The import uses at most 85% of that, so your other apps keep working. When the limit is reached anyway, the import waits and then carries on.
  • Deskwoot updates and server restarts don't stop it. It continues where it stopped. If a run crashes or gets stuck 3 times in a row without getting any further, the import stops and says so. Start it again to continue.
  • One import runs per workspace at a time. Start the next one when the current one has finished.
  • To stop an import, click Cancel import on the import page and confirm with Cancel and delete. The import stops and what it imported so far is deleted. A conversation someone wrote in since then keeps those new messages.
  • If Tidio stops answering or refuses a list, the import keeps what it already read, finishes the other steps and ends with Imported partly and the steps that stopped early. Start the import again to continue.

Your agents' conversations and replies

A ticket assigned to a Tidio agent, and a live chat that an agent answered first, go to the teammate with the same email, and the agent's replies show them as the sender. With tickets switched on, the Deskwoot ticket goes to that teammate too. If that person has no Deskwoot account yet, the conversation arrives unassigned and their replies show their name with (imported). Agents you removed from Tidio keep their name on their replies the same way.

When they join your workspace later with the same email, Deskwoot hands them their work automatically: their unassigned imported conversations are assigned to them and they become the sender of their replies. Open, pending and snoozed conversations come with one notification for all of them. Resolved ones are assigned quietly. No status changes, and your customers see nothing. A conversation that someone in Deskwoot has already held stays as it is. The Deskwoot tickets the import made are not handed over this way: assign those by hand.

Imported conversations stay quiet

Imported conversations are history, so they stay quiet until the customer writes again or someone on your team replies in Deskwoot. Until then Deskwoot sends the customer nothing from them (no farewell message, no satisfaction survey), starts no SLA clock and does not resolve them automatically. Imported conversations never count toward your plan's monthly conversation limit and are never locked by it, also after the customer writes again. Resolving or reopening one by hand fires no webhook and no automation rule. From the first new message on, the conversation works like any other, except that Fynn, the AI bot, never answers in an imported conversation. The Deskwoot tickets the import made are history in the same way.

Inboxes for imported tickets

  • Tidio notes where each ticket came from, for example an email or a contact form. The import puts each ticket's conversation into the inbox you picked for its kind, so your team can answer it there. Live chats get no inbox.
  • Tidio gives where a ticket came from only on the next day (see "After the import"). A ticket of today therefore comes without an inbox, and the import in Import History counts it under Conversations without a saved channel. A run on the next day puts it into the inbox you picked.
  • A conversation only goes into an inbox where Deskwoot can reach the customer: an email inbox needs their email address, a Telegram inbox their Telegram chat, and a WhatsApp or SMS inbox their phone number. Other conversations come in without an inbox.
  • When you start the import again, conversations you imported before go into the inboxes you pick too, if they have no inbox yet. One that already has an inbox, or that someone on your team wrote in, stays where it is. The next import starts from the inboxes of the last one.
  • The import in Import History shows the inboxes you picked and how many conversations went into one.

After the import

  • Start the import again the next day. Tidio fills its Analytics API, which the live chats, the ratings and the notes on contacts come from, once a day: each day's data arrives the next day at about 10:00 UTC. Tickets and their messages come right away, but of the current day the first run cannot bring everything yet: the live chats (only the chats of contacts Tidio created since its last daily update come right away), their ratings, new notes on contacts, and the tags, field values and inbox of today's tickets. A run after 10:00 UTC the next day adds what was missing and duplicates nothing.
  • A conversation without an inbox (because you picked none for its kind, Deskwoot can't reach the customer there, or it is a live chat) needs one before you reply: open it and pick an inbox in the This conversation has no inbox notice. When you picked inboxes, the import in Import History counts the tickets left without one under Still to do.
  • Add your teammates to the teams that came from your departments.

Frequently asked questions

Which Tidio plan do I need?

Tidio documents its API for the Plus and Premium plans. When you click Start Import, Deskwoot first asks Tidio for your project. If Tidio does not allow API access for it, the panel says so and nothing is imported: check your Tidio plan, then start the import again.

Some of today's chats are missing. Why?

Tidio hands out live chats, ratings, notes on contacts and some details of tickets through its Analytics API, which Tidio fills once a day: each day's data arrives the next day at about 10:00 UTC. Start the import again after that. It adds what was missing, for example today's chats, their ratings and the inbox of today's tickets, and duplicates nothing.

Can I start the import again?

Yes, that is safe. A new run finds what is already in Deskwoot and skips it, so conversations, contacts and articles are not duplicated. It brings in what is new or was missing, for example after a run that ended with Imported partly. A ticket or chat that changed in Tidio takes over its new status, as long as nobody on your team has written in it. A new message in a ticket you imported before comes right away when something else of the ticket changed too (its status, priority, agent, department or subject), else with a run on the next day.

Lyro answers your team edited in Deskwoot keep their new text. An answer switched off in Tidio since then becomes a draft, but only if your team has not edited it.

Keep in mind that conversations, contacts and notes you deleted or erased in Deskwoot since the last import come back if Tidio still has them, and so do contacts you merged.

Can I import only part of my data?

Yes. Under What should come along?, everything is on by default, and you can switch off Conversations (your tickets and live chats), Contacts, Knowledge base (your Lyro knowledge) and Satisfaction ratings. With a day under Only conversations created on or after, only conversations created on or after that day come. Ratings come only with the conversations they rate, so that option is greyed out without the conversations. Teams, agents and fields always come, and labels come with the conversations. If you leave out the contacts, each imported conversation still brings its own contact, without the notes.

When you open an import in Import History, Your choice shows what was not selected and the start date. To get the rest later, start an import with everything selected: it skips what is already in Deskwoot and brings in what was left out.

My contacts are already in Deskwoot. Does the import use them?

Yes. Before the import adds a contact, it looks for that person in Deskwoot: first by the Tidio ID, then by the email address, whether it is written in upper or lower case. Their conversations then go to the contact you already have, and its name, details and fields stay as they are. To match by ID, give each contact its Tidio ID when you add or update it through the API, in the externalId field: tidio:, your Tidio project ID (Tidio's API gives it as project_id), a colon and the contact's ID in Tidio's API, for example tidio:1234567:5f1c2b9e-8a7d-4c3b-9e21-0d4f6a7b8c9d. If all of your contacts are in Deskwoot already, you can switch off Contacts: each conversation still goes to its contact, and one that Deskwoot does not have yet comes with the conversation.

How do I undo an import?

In Import History, click Delete next to the import and enter your password. This deletes the conversations, tickets and contacts it created, together with the files it copied for them. A conversation someone wrote in since then stays with those new messages, without the imported ones, and a contact who still has a conversation stays too. Teams, agents, labels, fields, the Lyro knowledge and other settings stay. Deleting continues after a restart, and you can start a new import once it is done. While another import runs, an import cannot be deleted. If you imported from Tidio more than once, delete the imports from the newest to the oldest: while a newer Tidio import exists, Deskwoot asks you to delete that one first.

Was this guide helpful?

Keep reading

Ask Fynn about this guide

Get a short answer from this guide and the rest of the help center.

Still need help?

Fynn answers from these guides in the chat, and you can reach the team there too.