Export Your Data
Converge Team
Part of the Tidio migration guide
Learn how to export your customer data, conversation history, and contacts from Tidio before migrating to a new platform.
How to Export Your Data from Tidio
Tidio provides contact export through its panel and a REST API for conversation history. There is no single "export everything" button — you need separate methods for contacts, conversations, tickets, and automations.
Step 1: Export Contacts as CSV
Go to the Contacts section in your Tidio panel. Use checkboxes to select specific contacts or click Select All to grab everyone, then click Export. Tidio generates a CSV file with these fields: first name, last name, email, phone number, creation date, and subscription status. Any custom Contact Properties you've defined under Settings > Fields > Contact Properties (text, number, email, phone, or URL fields) are included as additional columns. Newsletter subscriber lists from Tidio's email marketing features are also exportable from the Contacts section. This works on all plans, including Free.
Step 2: Export Conversation History via API
Tidio's REST API lets you retrieve full conversation data programmatically. Generate your API credentials at Settings > Developer > OpenAPI (owner or admin access required). You get two keys: a Client ID (prefixed ci_) and a Client Secret (prefixed cs_). Use them as request headers: X-Tidio-Openapi-Client-Id and X-Tidio-Openapi-Client-Secret. Call GET https://api.tidio.com/contacts with cursor-based pagination to list all contacts, then GET https://api.tidio.com/contacts/{contactId}/messages for each contact's full message history — including visitor messages, operator replies, and chatbot interactions. Full OpenAPI access requires the Plus plan ($749/month) or above.
Step 3: Export Tickets
Tidio's helpdesk tickets (created from email or live chat) are managed within the Inbox, but there is no native bulk ticket export in the UI. Use the GET https://api.tidio.com/tickets API endpoint to retrieve ticket data programmatically (Plus plan required). Alternatively, the third-party migration tool Help Desk Migration (help-desk-migration.com) supports Tidio as a source platform and can extract tickets, conversations, and contacts without API access on your end.
Step 4: Document Flows and Automations
Tidio's Flows (visual chatbot paths) cannot be exported. Screenshot each Flow's trigger conditions, decision trees, and response text — or copy the text into a document. Do the same for macros (canned response shortcuts, available on Growth+), operating hours settings, auto-assignment rules, and any ticketing automations. You'll recreate these as auto-reply rules and quick replies on your new platform.
Step 5: Save Lyro AI Training Sources
Lyro AI's knowledge base — FAQ uploads, website scrapes, and custom knowledge entries — is not exportable from Tidio. Save the original FAQ documents and website URLs you used to train Lyro. If you created custom knowledge entries directly in Tidio's panel, copy that text manually. You'll need these source materials to configure AI features on your new platform.
Tip: If you've connected Tidio to Shopify, WooCommerce, or other e-commerce platforms, document which integrations are active and their configurations before canceling. These store connections won't transfer — you'll set up equivalent integrations on your new platform separately.
Need the full migration guide?
This page covers export your data specifically. For the complete step-by-step migration process:
Read the complete Tidio migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial