Tidio to Zendesk migration
We migrate Contacts, Conversations, and Tags from Tidio to Zendesk with full message history preserved through the Zendesk API, custom contact properties mapped to Zendesk fields, and every Tidio Flow and Lyro data source documented for your admin to rebuild after cutover.
FlitStack AI migrates users, tickets, tags, zendesk ai bot / flows and zendesk guide / advanced ai knowledge sources from Tidio to Zendesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-4 weeks.

What moves from Tidio to Zendesk?
Tidio's unified inbox model treats Contacts and live conversations as a single stream; Zendesk separates Tickets, Users, Organizations, and channel-specific records into distinct objects.
Read the full summary
We resolve that schema difference during migration: Tidio conversations become Zendesk Tickets with channel metadata in custom fields, and Tidio contacts become Zendesk Users with Organization linkage where a company relationship exists. Tidio's visual Flow automations (chatbot builders) and Lyro AI knowledge bases have no export mechanism — we document them as a manifest so your team can rebuild them in Zendesk natively. Macros transfer as content lists, not reusable templates. Operating hours, department routing, and channel tokens export as structured data for manual reconfiguration at the destination.
Contact → User (and Organization where applicable)
Tidio Contacts map to Zendesk Users.
How it maps
Standard fields (name, email, phone) transfer directly. Any Tidio custom contact properties export as structured data and require pre-creation as Zendesk user fields (text, numeric, date, or dropdown) before migration. If a Tidio Contact has a company association, we resolve it to an Organization in Zendesk and link via the Organization field on the User record. Tags on contacts migrate as a JSON array stored in a custom field for post-migration segmentation.
Conversation → Ticket
Tidio conversations become Zendesk Tickets.
How it maps
The conversation subject or first message becomes the Ticket subject; the full message thread (agent messages, customer messages, internal notes) migrates as threaded comments. Channel origin (chat, email, WhatsApp, Messenger, Instagram) is stored in a custom Ticket field to preserve the source channel for reporting. Timestamps and assignee IDs transfer to preserve the original activity timeline and agent ownership.
Tags → Tags
Tidio tags are flat string labels attached to contacts and sometimes conversations.
How it maps
We export the full tag list as a string array and attach each tag to the corresponding Zendesk User or Ticket record. In Zendesk, tags are not a separate object but a field on Tickets and Users. No tag merging or renaming is required unless the customer has duplicate tags with different capitalization.
Flows (Chatbot Automations) → Zendesk AI Bot / Flow (manual rebuild required)
Tidio Flows have no public API endpoint.
How it maps
We enumerate all active Flows by name, trigger type, block count, and step descriptions and export this as a JSON manifest. The manifest includes the Flow logic graph so your Zendesk admin can rebuild equivalent automation using Zendesk's own bot builder or Flow product. This manifest is a planning deliverable, not a data migration.
Lyro AI Knowledge Bases → Zendesk Guide / Advanced AI knowledge sources (manual rebuild required)
Lyro data sources (imported Help Center articles, Shopify product feeds, web page crawls, Q&A pairs) live inside Tidio's proprietary AI infrastructure with no export API.
How it maps
We document which sources were connected, their last-sync dates, and the topics Lyro was trained on. Your team re-authorizes and re-syncs these data sources in Zendesk Guide or an external knowledge base post-migration. This is manual work with no automated path.
Lyro Conversations → Zendesk Ticket analytics (not migrated)
Lyro conversation logs are not accessible via API and do not carry forward to Zendesk.
How it maps
We flag the existence of Lyro conversation history in the scope so you understand what AI analytics you will leave behind. Zendesk's Advanced AI analytics are available as a post-migration reporting layer but require fresh data accumulation.
- ContactUser1:1
- ConversationTicket1:1
- TagsTags1:1
- FlowsZendesk AI Bottransformed
- Lyro AI Knowledge BasesZendesk Guidetransformed
- Lyro ConversationsZendesk Ticket analyticstransformed
+ 6 more in the mapping below
How Tidio and Zendesk differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Tidio | Zendesk |
|---|---|---|
| Object model | Unified inbox: Contacts and conversations share one stream | Separate Ticket, User, Organization, and channel objects with foreign-key relationships |
| Knowledge base | Lyro AI with no export; no true knowledge base product | Zendesk Guide as a separate product with articles, sections, and categories |
| Chatbot builder | Visual Flow builder with no API access to Flow logic | Zendesk AI bots with no direct import from Tidio Flows |
| Channel scope | Live chat, email, Facebook, Instagram, WhatsApp (limited) | Support across email, chat, phone, WhatsApp, Facebook, Twitter/X, Instagram, and custom messaging channels |
| AI offering | Lyro AI (proprietary, non-exportable) as a bundled feature | Advanced AI add-on ($50/agent/mo) on top of Suite plans; Intelligent Triage and Copilot available separately |
| Agent limit | 10-agent hard cap on all self-serve tiers | Team plan starts at $55/agent/mo with no stated team ceiling |
| Pricing model | Per-agent with monthly billable conversation caps that do not roll over | Per-agent per-month with optional AI add-on; conversation volumes are not tier-gated |
What to watch for in a Tidio to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Flows cannot be exported — documented as a manifest only
Tidio's visual Flow builder has no public API endpoint to read Flow logic.
How we handle it
The platform stores Flow definitions server-side in a non-exportable format. We enumerate all active Flows by name, trigger type, block count, and step description and export this as a JSON manifest. Your Zendesk admin uses this to rebuild equivalent bot flows using Zendesk's own bot builder or Flow product. This is the most common source of migration surprise for Tidio customers and the most significant limitation of the migration scope.
Lyro AI training data and knowledge bases are not portable
Lyro is Tidio's proprietary AI agent.
How we handle it
Its knowledge bases (Q&A pairs, imported Help Center articles, Shopify product feeds, web page crawls) live inside Tidio's infrastructure with no export mechanism. Lyro conversation logs are also not accessible via API. We document which data sources were connected and their last sync dates so your team knows what content to re-authorize and re-train in Zendesk Guide or a connected AI knowledge base. This is manual work that must be done post-migration.
Bulk conversation export requires Tidio Plus API access
Tidio does not expose a bulk download endpoint for conversation history in its standard interface.
How we handle it
Agents can export individual transcripts by email, but there is no self-serve bulk export on Starter or Growth plans. On Plus plan, OpenAPI access allows us to query the API for all conversation records within a date range and assemble them into a migration bundle. If your Tidio account is on Starter or Growth, we flag the scope and may need to coordinate a manual export step with your Tidio admin before we can proceed programmatically.
Tidio custom field types may not map directly to Zendesk field types
Tidio custom contact properties can include types (dropdown, multi-select, checkbox) that Zendesk represents differently.
How we handle it
Zendesk's User Fields support text, numeric, date, and dropdown, but multi-select and complex checkbox structures may require conversion to a text field, a tag-based approach, or a custom Zendesk App. We flag field-type mismatches during scoping and propose a resolution strategy before migration begins.
Zendesk Guide is a separate product requiring activation
Zendesk Guide is a separate product tier that must be activated, configured, and published before your knowledge base is live.
How we handle it
If you plan to migrate Lyro data sources to a Zendesk Help Center, Guide must be enabled in your Zendesk admin account before we can configure article imports. We flag this as a pre-migration step and can assist with Guide configuration as a separate engagement.
How the migration runs
Discovery and scope confirmation
We audit the Tidio account across plan tier (Starter, Growth, Plus), agent count, conversation volume, active Flows, connected Lyro data sources, macros, channel configurations, and department structure.
What this step covers
We determine whether Plus-plan OpenAPI access is available (required for automated bulk export of conversations). We also confirm the Zendesk plan tier and whether Zendesk Guide is active or needs to be provisioned. The discovery output is a written migration scope with record counts, a list of objects we can migrate, and a manifest of objects we document only.
Schema design in Zendesk
We configure the Zendesk destination environment before any data arrives.
What this step covers
This includes creating custom User fields to match Tidio custom contact properties, setting up channel configurations for the active email addresses and social accounts, configuring Business Hours, creating Groups to match Tidio departments, and preparing tag-handling rules. If Zendesk Guide is not yet active, we flag this for your admin to activate so the Help Center is ready for knowledge base work post-migration.
Data extraction from Tidio
We extract all Contacts, Conversations, Tags, channel metadata, agent records, operating hours, department assignments, and macro content from Tidio via API (Plus plan) or via a coordinated manual export step (Starter/Growth).
What this step covers
We assemble the export into a structured staging bundle and validate field coverage before mapping begins. Any gaps in the export (Lyro data, Flow logic) are documented in the manifest. This step produces the migration bundle that feeds the Zendesk import.
Test migration to Zendesk Sandbox
We run a full migration into a Zendesk Sandbox environment using production-like data volume.
What this step covers
Your team reconciles record counts, spot-checks 20-30 random Tickets and Users against the Tidio source, and validates that channel metadata and custom fields populated correctly. Any field mapping corrections, custom field type adjustments, or tag-handling changes happen here before production migration begins. Sign-off on the Sandbox run is required before we proceed to production.
Production migration in dependency order
We run the production migration in record-dependency order: Users first (with Organization linkage where applicable), then Tickets with full message thread preservation, then Tags attached to records, then channel and operating-hours configuration data.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Conversation-to-Ticket conversion preserves the original channel metadata in a custom Ticket field. We use Zendesk's REST API with rate-limit handling and exponential backoff to avoid triggering Zendesk's concurrent-request limits.
Cutover and post-migration handoff
We freeze Tidio writes during the cutover window, run a final delta migration of any records modified during the migration run, then enable Zendesk as the system of record.
What this step covers
We deliver the Flows manifest, Lyro data sources document, and macro content list to your admin team along with a full reconciliation report showing record counts in both systems. We support a one-week hypercare window for any reconciliation issues. We do not rebuild Flows in Zendesk, configure Zendesk Guide, or set up Zendesk routing rules as part of the standard migration scope.
Tidio - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume and the number of objects requiring migration. Tidio Plus-plan API access (required for automated bulk export) may require a Tidio subscription upgrade if not already active; this sits outside the migration fee. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Tidio to Zendesk →Why teams move from Tidio to Zendesk
- Teams hit Tidio's 10-agent hard cap and need to scale beyond what any self-serve plan allows. At 11 or more agents, Tidio requires the $749/mo Plus tier, which is priced near the combined cost of a Zendesk Suite Team plan ($55/agent) for a larger team without the ceiling. G2 reviews and Reddit threads document teams moving to Zendesk specifically because Zendesk scales agent counts without a self-serve cap at the lower price tiers.
- Tidio's Lyro AI is described as underperforming by power users compared to dedicated AI chatbot platforms. Multiple Reddit and review threads cite limited training data control, inability to use Lyro and Flows simultaneously, and responses that lack accuracy for multi-part questions. Teams moving to Zendesk cite Zendesk's Advanced AI add-on and Intelligent Triage as more capable replacements, though at an additional per-agent cost.
- Growing businesses need omnichannel support beyond Tidio's live-chat-centric model. Zendesk natively supports phone, Twitter/X, custom messaging channels, and a full-service knowledge base (Guide) that Tidio does not offer as a structured product. DelightChat and Jotform comparisons note that Zendesk's channel coverage is more exhaustive than Tidio's for teams needing social channel automation beyond Facebook and Instagram.
- Zendesk's reporting and analytics are more granular and are included at all paid tiers rather than gated behind a higher-priced plan. Tidio's advanced analytics require Growth or Plus tier, and custom reporting is limited. Enterprise teams and RevOps managers moving to Zendesk cite the ability to build multi-dimensional SLA, CSAT, and agent productivity reports without exporting to a BI tool as a primary driver.
- Monthly billable conversation caps on Tidio's Starter and Growth plans reset without rollover, creating billing unpredictability for teams with variable ticket volumes. Reviewers on Capterra and G2 consistently cite quota surprises as a frustration that drives evaluation of flat-rate or per-agent pricing models. Zendesk's per-agent model does not impose monthly conversation limits, making costs more predictable at scale.
Questions, answered
Tidio to Zendesk migration questions
How long does a Tidio to Zendesk migration take?
Most migrations land between two and four weeks for accounts under 10,000 contacts and 20,000 conversations with no complex custom field structures. Migrations with large conversation histories (over 50,000 tickets), multiple active social channels, or multi-department routing configurations move to six to ten weeks because of delta migration handling, Sandbox validation, and department reconfiguration work.
Do Tidio Flows and Lyro AI conversations migrate to Zendesk?
No. Tidio Flows are built in a visual builder with no API access to the underlying logic — they cannot be exported programmatically and must be rebuilt manually in Zendesk using Zendesk's bot builder or Flow product. Lyro AI knowledge bases, Q&A pairs, and conversation logs are stored in Tidio's proprietary infrastructure with no export mechanism. We document which Lyro data sources were connected and their last sync dates so your team can re-authorize and re-train in Zendesk Guide post-migration.
What objects can FlitStack AI migrate from Tidio to Zendesk?
We migrate Contacts (to Zendesk Users), Conversations (to Zendesk Tickets with full message history), Tags, channel configurations, operating hours, department structure, macros (as a content document), and agent records. We document Flows and Lyro data sources for manual rebuild. We do not migrate Lyro conversation logs, Flow automation logic, or Tidio-proprietary integrations that require OAuth re-authentication at the destination.
Can Tidio chatbot Flows be migrated as code to Zendesk?
No. Tidio's visual Flow builder does not expose an API for Flow logic. We cannot export Flows as code or configuration data to any destination platform including Zendesk. We provide a manifest listing every active Flow by name, trigger condition, block count, and step description. Your Zendesk admin rebuilds these using Zendesk's bot builder, Flow product, or a third-party automation tool. This is manual work that is scoped separately from the data migration.
What happens to our Tidio conversation history during migration?
On Tidio Plus plan, we use the OpenAPI to extract all conversation records within the specified date range including message threads, channel origin, agent assignments, and timestamps. On Starter or Growth plans, we coordinate a manual export step with your Tidio admin to extract conversation data. Full message history transfers to Zendesk as Ticket comments with channel origin preserved in a custom field. Individual transcript attachments migrate as file comments on the corresponding Ticket.
Do you migrate Tidio workflows, automations, or reporting dashboards to Zendesk?
No. We do not migrate Tidio automations as code because Tidio's Flow builder has no export API. Reporting dashboards are platform-specific and do not transfer between products. We deliver a written inventory of every active Tidio Flow with trigger, conditions, and step descriptions, and a list of configured macros and operating hours for your Zendesk admin to rebuild. This is manual work scoped outside the data migration.
What Zendesk plan is required to receive the migrated data?
Zendesk Suite Team ($55/agent/mo) is sufficient for most migrations from Tidio, covering Tickets, Users, Groups, and basic reporting. If you need Zendesk Guide for a knowledge base, SLA management, advanced analytics, or the Advanced AI add-on, Suite Growth ($89/agent/mo) or Suite Professional ($115/agent/mo) is required. We do not recommend a specific Zendesk plan tier but can advise on which features your migrated data requires based on the Tidio feature set in use.
Related migrations
Sources: official documentation
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
- Bulk importing user data with the data importer — Zendesk help
- How do I format the date field in Sell — Zendesk help
- About custom ticket fields — Zendesk help
- About lookup relationship fields — Zendesk help
Get a quote
Moving from Tidio to Zendesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.
Get a quote