Migrate your Tidio data
AI-first helpdesk combining live chat, Flows chatbot builder, and Lyro AI agent in one workspace. Best suited for SMBs and eCommerce teams wanting quick setup without a complex enterprise toolchain.
In its favor
Why people choose Tidio
The signal that keeps Tidio on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Fast, code-free onboarding lets small teams deploy live chat and a basic chatbot in an afternoon without developer involvement, validated by reviewers who highlight setup speed as a primary reason for choosing Tidio.
Bundled live chat, ticketing, and AI chatbot in one workspace eliminates the need to buy and integrate separate tools, which reviewers on G2 consistently rank as a top advantage over point solutions.
Lyro AI offers genuine automation for common support questions and shows measurable ROI for small teams that lack budget for a full customer service staff, backed by Tidio's published 67% automation claims.
Native Shopify integration gives support agents access to cart contents, order status, and shipment data without leaving the chat widget — a feature eCommerce operators specifically call out in reviews.
Starter tier provides a legitimate free trial with 100 billable conversations and 50 Lyro conversations, allowing teams to validate fit before committing to a paid plan, which reviewers appreciate for lowering adoption risk.
Conversation quotas, Lyro conversation limits, and Flow visitor caps all reset every 30 days with no rollover — teams on Starter and Growth find themselves regularly hitting billing surprises mid-month.
The 10-agent hard cap on all self-serve tiers forces growing teams into the $749/mo Plus tier or forces an exit to platforms with more generous team-based pricing.
Lyro AI feels basic to power users — multiple Reddit and review threads describe the AI as underperforming compared to dedicated AI chatbot platforms, with limited training data control and occasional incorrect responses.
Multichannel coverage is a known weakness; businesses relying on Facebook, Instagram DMs, or WhatsApp automation find Tidio's social channel support thinner than competitors like Intercom or Crisp.
Advanced automation features and deeper analytics are gated behind Plus, pushing mid-size teams toward enterprise platforms where those capabilities are included at lower price points.
Reasons to switch
Why people leave Tidio
The recurring reasons buyers give for replacing Tidio. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Tidio fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Tidio pricing overview
Tidio uses a per-agent model with billable conversation caps that increase at each tier. All self-serve plans cap at 10 agents; larger teams require the custom Plus tier. Lyro AI conversations are limited on Starter (50 one-time) and grow with higher tiers. Annual billing provides approximately two free months. Quotas do not roll over between billing cycles.
Starter
Tier 1 of 3
$24.17/mo (billed monthly) or $20.14/mo (billed annually)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Tidio's schedule — see our quote-based pricing →
What gets migrated
Tidio object support
Object-by-object support for Tidio migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts in Tidio carry name, email, phone, and custom contact properties. We export all standard fields plus any custom properties and tags added to a contact. Merge logic applies if the destination already has a matching email address.
Conversations
Fully supportedConversations include both open and resolved threads. We preserve the full message history, channel origin (chat, email, WhatsApp, Messenger, Instagram), assigned agent, status, and timestamp. Pre-chat survey responses are attached as metadata.
Channels
Mapping requiredChannel configuration (email addresses, WhatsApp number, Messenger page, Instagram account) includes platform-specific tokens and webhook URLs. We export the channel list and connection metadata so you can reconfigure them at the destination. Live tokens (OAuth sessions) cannot be transferred and must be re-authenticated.
Flows (Chatbot Automations)
Mapping requiredFlows are built in Tidio's visual drag-and-drop builder. The Flow logic itself cannot be exported via API. We capture Flow names, trigger conditions, block counts, and step descriptions as a JSON manifest so your team can rebuild them at the destination.
Lyro AI Knowledge Bases
Not in this platformLyro's question-and-answer pairs and training data are stored within Tidio's proprietary AI infrastructure. There is no export endpoint and no third-party tool can read this data. We document which data sources were connected (Zendesk, Shopify, web pages) so you know which content to re-upload at the destination.
Lyro Conversations
Not in this platformLyro conversation logs are accessible within Tidio but are not available via API. We flag the existence of these records in the scope so you understand what analytics you will leave behind when departing Tidio.
Tags
Fully supportedTags are flat string labels applied to contacts. We export the full tag list and attach them to the corresponding contact records at the destination.
Contact Properties
Mapping requiredStandard contact properties (name, email, phone, location) map directly. Custom contact properties may use Tidio-specific field names and types that need renaming at the destination. We flag any custom fields for explicit mapping review.
Visitors
Mapping requiredVisitor records include location, viewed pages, and session duration. Full visitor history is only retained while a visitor is active. Historical visitor aggregates are captured from conversation context, not as standalone records.
Agents
Mapping requiredAgent records include name, email, and role. User permissions and department assignments are only available on Growth and Plus tiers. We export available agent data and flag missing permission fields for Plus-plan migrations.
Macros
Mapping requiredMacros are pre-written response templates with variable placeholders. They cannot be exported as reusable templates. We list all macro names and content so you can recreate them manually at the destination.
Operating Hours
Mapping requiredOperating hours are configured per-channel and control when automated replies fire. We export the configured hours as structured data so you can re-enter them at the destination.
Departments
Mapping requiredDepartments are only available on the Plus plan. Agent-to-department assignments and routing rules are exported as structured data and must be re-created at the destination.
Data Sources (Lyro)
Mapping requiredLyro data sources include Zendesk Help Center imports, Shopify product feeds, and web page crawls. We document which sources were connected and their last sync dates so you can re-authorize and re-sync them at the destination.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts in Tidio carry name, email, phone, and custom contact properties. We export all standard fields plus any custom properties and tags added to a contact. Merge logic applies if the destination already has a matching email address. |
| Conversations | Fully supported | Conversations include both open and resolved threads. We preserve the full message history, channel origin (chat, email, WhatsApp, Messenger, Instagram), assigned agent, status, and timestamp. Pre-chat survey responses are attached as metadata. |
| Channels | Mapping required | Channel configuration (email addresses, WhatsApp number, Messenger page, Instagram account) includes platform-specific tokens and webhook URLs. We export the channel list and connection metadata so you can reconfigure them at the destination. Live tokens (OAuth sessions) cannot be transferred and must be re-authenticated. |
| Flows (Chatbot Automations) | Mapping required | Flows are built in Tidio's visual drag-and-drop builder. The Flow logic itself cannot be exported via API. We capture Flow names, trigger conditions, block counts, and step descriptions as a JSON manifest so your team can rebuild them at the destination. |
| Lyro AI Knowledge Bases | Not in this platform | Lyro's question-and-answer pairs and training data are stored within Tidio's proprietary AI infrastructure. There is no export endpoint and no third-party tool can read this data. We document which data sources were connected (Zendesk, Shopify, web pages) so you know which content to re-upload at the destination. |
| Lyro Conversations | Not in this platform | Lyro conversation logs are accessible within Tidio but are not available via API. We flag the existence of these records in the scope so you understand what analytics you will leave behind when departing Tidio. |
| Tags | Fully supported | Tags are flat string labels applied to contacts. We export the full tag list and attach them to the corresponding contact records at the destination. |
| Contact Properties | Mapping required | Standard contact properties (name, email, phone, location) map directly. Custom contact properties may use Tidio-specific field names and types that need renaming at the destination. We flag any custom fields for explicit mapping review. |
| Visitors | Mapping required | Visitor records include location, viewed pages, and session duration. Full visitor history is only retained while a visitor is active. Historical visitor aggregates are captured from conversation context, not as standalone records. |
| Agents | Mapping required | Agent records include name, email, and role. User permissions and department assignments are only available on Growth and Plus tiers. We export available agent data and flag missing permission fields for Plus-plan migrations. |
| Macros | Mapping required | Macros are pre-written response templates with variable placeholders. They cannot be exported as reusable templates. We list all macro names and content so you can recreate them manually at the destination. |
| Operating Hours | Mapping required | Operating hours are configured per-channel and control when automated replies fire. We export the configured hours as structured data so you can re-enter them at the destination. |
| Departments | Mapping required | Departments are only available on the Plus plan. Agent-to-department assignments and routing rules are exported as structured data and must be re-created at the destination. |
| Data Sources (Lyro) | Mapping required | Lyro data sources include Zendesk Help Center imports, Shopify product feeds, and web page crawls. We document which sources were connected and their last sync dates so you can re-authorize and re-sync them at the destination. |
Gotchas
What to watch for in Tidio migrations
Issues we've hit on past Tidio migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Conversation and Lyro quotas reset monthly without rollover
Flows cannot be exported — only documented as a manifest
Lyro AI knowledge and conversation logs are not portable
Chat history requires manual export by agents
Agent limits and department routing are plan-gated
| Severity | Issue |
|---|---|
| High | Conversation and Lyro quotas reset monthly without rollover |
| High | Flows cannot be exported — only documented as a manifest |
| High | Lyro AI knowledge and conversation logs are not portable |
| Medium | Chat history requires manual export by agents |
| Medium | Agent limits and department routing are plan-gated |
Leaving Tidio?
Where Tidio customers move next
7 destinations Tidio can migrate to.
How a Tidio migration works
Four steps, Tidio-specific
Connect
API key (private token) into Tidio. Scopes limited to read-only on the data we move.
Map
We translate Tidio-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Tidio quirks before production.
Migrate
Full migration with Tidio rate-limit handling. Rollback available throughout.
FAQ
Tidio migration FAQ
Answers to the questions buyers ask most during Tidio migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Tidio migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Tidio.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Tidio setup and destination — written quote back within a business day.