Kayako to Zendesk migration
We migrate Conversations, Users, Organizations, Knowledge Base Articles, and custom field data from Kayako into Zendesk with the custom field API keys resolved upfront, Knowledge Base hierarchy rebuilt in Zendesk Guide, and a written automation inventory delivered so your admin can rebuild triggers and SLA policies post-migration.
FlitStack AI migrates tickets, agents, organizations, custom fields and articles from Kayako 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: 3-5 weeks.

What moves from Kayako to Zendesk?
Moving from Kayako to Zendesk is a structural migration that requires more than a record copy.
Read the full summary
Kayako organizes support around Conversations linked to Users and Organizations; Zendesk uses Tickets with a parallel Help Center (Guide) for self-service. We map Kayako custom field API keys during discovery and use them in all Zendesk API writes to avoid silent field-population failures. Knowledge Base articles and their category hierarchy migrate to Zendesk Guide, which must be activated before import. We do not migrate automations, triggers, SLA policies, or saved reports as configuration; these are documented in a written inventory for your admin to rebuild in Zendesk.
Conversation → Ticket
Kayako Conversations map 1:1 to Zendesk Tickets.
How it maps
We map Conversation status to Zendesk Ticket status, priority to priority, assignee (via email lookup against Zendesk User table) to assignee, and channel to the Zendesk channel field with the original requester metadata preserved. Message threads transfer as Ticket Comments. Any Conversation without a valid requester email is flagged for admin review before migration because Zendesk requires a requester on every imported ticket.
User (Agent/Admin) → Agent
Kayako Agents and Admins map to Zendesk Agents by email match.
How it maps
Role and permissions from Kayako (admin, agent, team assignment) are documented for manual role assignment in Zendesk because Zendesk's role model uses a different permission hierarchy. Any Kayako Agent without a matching Zendesk account is placed in a reconciliation queue for the admin to provision before tickets are assigned.
Organization → Organization
Kayako Organizations map directly to Zendesk Organizations.
How it maps
The Organization domain becomes the Zendesk Organization domain field and is used as a deduplication key during import. We create Organizations before Users and Conversations so that the Organization lookup relationship is satisfied at the moment of User and Ticket insert.
Custom Field → Custom Field
Custom fields on Kayako Conversations require API field key discovery during scoping before any data moves.
How it maps
Each Kayako custom field maps to a Zendesk Custom Field of the matching type (text, dropdown, checkbox, date, numeric). Zendesk drop-down and multiselect fields automatically generate tags from selected values on import, which can duplicate existing tags if the source data uses both custom fields and manual tags for the same label. We document this behavior and recommend tag deduplication as a post-migration step.
Knowledge Base Article → Article (Guide)
Kayako Knowledge Base articles and their category hierarchy migrate to Zendesk Guide, which is a separate product that must be activated before import.
How it maps
We export articles and their category structure from Kayako, then rebuild the category hierarchy in Zendesk Guide sections and categories. Zendesk Guide Enterprise supports hierarchical article subsections up to five levels deep with a maximum of 20 subsections per parent section. Only the default language migrates unless the customer has multilingual content requiring manual section recreation in each locale.
KB Category → Section (Guide)
Kayako Knowledge Base categories map to Zendesk Guide Sections.
How it maps
We preserve the parent-child hierarchy and reparent articles at the destination. Naming conflicts with existing Zendesk Guide sections are resolved by appending a suffix or by the customer choosing to merge during scoping.
- ConversationTicket1:1
- UserAgent1:1
- OrganizationOrganization1:1
- Custom FieldCustom Fieldtransformed
- Knowledge Base ArticleArticlesplit
- KB CategorySection1:1
+ 4 more in the mapping below
How Kayako 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 | Kayako | Zendesk |
|---|---|---|
| Automation model | Trigger-based rules with conditions and actions native to Kayako | Triggers, Macros, and Automations in Zendesk Suite; different event model |
| Knowledge Base | Integrated Kayako Knowledge Base with articles and hierarchical categories | Zendesk Guide as a separate product requiring activation and separate admin setup |
| Custom field handling | Custom fields use API field keys (not display names); keys must be discovered before migration | Custom fields use field IDs; drop-downs and multiselects auto-generate tags on import |
| Pricing structure | $79/user/month (Elite) plus $1/AI-resolved-ticket; no entry-level tier | Suite Team at $55/agent/month through Enterprise at $169/agent/month; per-agent billing only |
| SLA configuration | SLA definitions are native to Kayako with response/resolution time tiers | SLA policies configured in Zendesk Admin with separate business hours setup |
| Reporting | Dashboard lacks depth; reporting across large conversation histories described as insufficient | Advanced analytics and reporting available; Enterprise adds custom report types |
| Integration ecosystem | Smaller ecosystem with fewer native integrations | Over 1,500 integrations via the Zendesk Marketplace |
What to watch for in a Kayako to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Kayako automations do not migrate to Zendesk
Kayako automation rules (triggers, conditions, escalation rules) and Zendesk Triggers use different event models, action types, and condition syntax.
How we handle it
We do not migrate automations as code. During discovery, we inventory every active Kayako automation and deliver a written map with trigger events, conditions, actions, and a Zendesk Trigger or Macro equivalent. The customer's admin or a Zendesk partner rebuilds these post-migration. Skipping this step means every historical ticket imported into Zendesk arrives without the routing, assignment, or notification logic that governed it in Kayako.
Zendesk Guide must be activated before KB migration
Zendesk Guide is a separate product from Zendesk Support and must be manually activated before any Knowledge Base articles can be imported.
How we handle it
Only the account owner can activate Guide via Admin > Products > Guide > Activate. If the customer plans to migrate Knowledge Base content and Guide is not activated, the KB migration phase fails silently at the import step. We confirm Guide activation status during scoping and include it in the pre-migration checklist.
Kayako custom fields require API field keys, not display names
Kayako custom fields have system-generated API field keys that differ from their admin display names.
How we handle it
API calls referencing the display name silently fail to populate the field. We discover all custom field keys during the discovery phase and re-verify keys for any fields created after initial setup. If a custom field key is incorrect or missing, the field value drops during migration without an error. This is especially disruptive for custom fields used in reporting or SLA logic.
Zendesk auto-generates tags from drop-down and multiselect custom fields
When Zendesk imports a drop-down or multiselect custom field value, it automatically generates a tag from that value for reporting and workflow use.
How we handle it
If the source Kayako data also uses tags for the same labels, this creates duplicate tags after migration. We document this behavior during scoping, recommend a tag-deduplication run post-migration, and can optionally strip or rename tags during import if the customer specifies a tag hygiene strategy upfront.
Attachments require per-Conversation API calls and have size limits
Kayako does not bulk-export file attachments.
How we handle it
Each Conversation with attachments requires a separate API call to retrieve its files, which increases extraction time for attachment-heavy accounts. Zendesk enforces plan-dependent file size limits (50MB per file on Suite Team, higher on Suite Enterprise), and we flag any Kayako attachments exceeding the target plan's limit before migration begins. Inline images in message threads migrate as Comment attachments, and we verify a representative sample after migration to confirm attachment-to-ticket linkage.
How the migration runs
Discovery and scoping
We audit the source Kayako account across version (cloud vs Classic), conversation volume, custom field count with API keys, active automation rules, Knowledge Base structure and article count, SLA definitions, and attachment volume per conversation.
What this step covers
We pair this with a Zendesk readiness check: confirming the target Zendesk Suite tier, whether Guide is active or requires activation, existing user count, and current ticket field configuration. The discovery output is a written migration scope specifying what migrates, what documents for rebuild, and what we flag as non-migratable.
Schema design and custom field mapping
We design the destination schema in Zendesk before any data moves.
What this step covers
This includes creating custom fields matching Kayako's types (text, dropdown, checkbox, date, numeric) with the correct Zendesk field IDs, configuring SLA policies from the Kayako SLA metadata, mapping Kayako agent roles to Zendesk role equivalents, and aligning conversation channel values to Zendesk channel fields. For Knowledge Base migration, we design the Zendesk Guide section and category hierarchy that mirrors Kayako's structure. All schema design is validated in a Zendesk Sandbox before production migration begins.
Test migration and reconciliation
We run a full migration into a Zendesk Sandbox using production-like data volume.
What this step covers
The customer reconciles record counts across all object types, spot-checks 25-50 randomly sampled records against the Kayako source, and validates Knowledge Base article rendering in Zendesk Guide. Mapping corrections, SLA policy adjustments, and Knowledge Base hierarchy refinements happen in this sandbox phase. No production data moves until the sandbox sign-off is received.
Knowledge Base migration
If the customer migrates Knowledge Base content, we export Kayako articles and category hierarchy, activate Zendesk Guide (if not already active), create the Guide section and category structure in Zendesk, then import articles in hierarchy order.
What this step covers
Article attachments are handled separately from conversation attachments. Only the default language migrates unless multilingual content is in scope. The Help Desk Migration service notes that Enterprise Guide supports subsection nesting up to five levels with a maximum of 20 subsections per parent section; we confirm the target structure fits within these limits before importing.
Production migration in dependency order
We run the production migration in strict record-dependency order to satisfy Zendesk's foreign-key requirements: Organizations (created first for deduplication), Users (matched by email), Conversations mapped to Tickets (using the Tickets API with comment threads, custom field values via field IDs, and tag assignment), and attachments (extracted per-conversation via Kayako API, uploaded to Zendesk with ticket-comment linkage).
What this step covers
We disable Zendesk triggers and automations during import to prevent unwanted email notifications firing on historical tickets. We flag any Kayako conversations without a valid requester email for admin resolution before the ticket insert batch resumes.
Cutover, validation, and rebuild handoff
We freeze Kayako writes during cutover, run a final delta migration of any new conversations created during the migration window, then switch communication routing to Zendesk.
What this step covers
We validate a representative sample of migrated tickets, organizations, and KB articles in production. We deliver the written automation inventory and SLA configuration guide for the customer's Zendesk admin. We support a one-week hypercare window for reconciliation issues. We do not rebuild Kayako automations as Zendesk Triggers inside the migration scope; that is a separate Zendesk implementation engagement.
Kayako - 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
Pricing reflects conversation volume, custom field count, knowledge base article migration, and attachment complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Kayako to Zendesk →Why teams move from Kayako to Zendesk
- Kayako's per-agent pricing at $79/user/month plus a $1/AI-resolved-ticket surcharge creates unpredictable total cost at scale. Reviewers on G2, Capterra, and Reddit note the AI-resolution billing multiplying costs silently as ticket volume grows, and the absence of an entry-level tier forces small teams onto a price that does not match their size. Zendesk Suite Team at $55/agent/month provides more predictable per-agent billing with phone and social support included at the lowest tier.
- Search across conversation history in Kayako is widely described as insufficient for teams with large knowledge bases and long ticket histories. Admins on Reddit's r/sysadmin report that Kayako's cloud version lacks features present in the on-premise version, including the ability to generate reports on prepaid customer hours and time entries. Zendesk's search and reporting engine is consistently cited as deeper, more flexible, and better suited for operational segmentation across customer tiers and regions.
- Kayako's analytics and reporting dashboard lacks the depth that enterprise and mid-market teams require for staffing decisions, SLA strategy, and executive reviews. Zendesk provides stronger reporting flexibility with multi-dimensional segmentation, custom report types at Enterprise, and a BI-compatible data model. Comparison reviews consistently identify reporting depth as a decisive factor for teams evaluating Zendesk as an upgrade path.
- Zendesk supports over 1,500 marketplace integrations versus Kayako's smaller ecosystem. Teams running complex tech stacks with ERP, CRM, contract lifecycle management, or voice integrations find Zendesk's AppExchange listings provide more first-party or certified options without Zapier routing. The integration gap becomes a practical constraint for teams that need native telephony, advanced telephony analytics, or CPQ connections.
- Kayako Classic remains in use by long-standing customers and runs on older PHP versions approaching end-of-life. Teams on Classic face migration challenges upgrading within Kayako's product line, and some find it simpler to switch platforms entirely rather than execute an in-place upgrade. This legacy-product uncertainty drives teams toward Zendesk's actively developed cloud-native platform as a known, stable destination.
Questions, answered
Kayako to Zendesk migration questions
How long does a Kayako to Zendesk migration take?
Most migrations land between three and five weeks for accounts under 30,000 conversations with no Knowledge Base migration. Projects involving large Knowledge Base migrations (over 1,000 articles), complex multi-type custom fields, or more than 100,000 historical attachments extend to seven to ten weeks because of Knowledge Base hierarchy mapping, per-conversation attachment extraction, and custom field key verification. Timeline phases include discovery and scoping (three to five business days), sandbox migration and reconciliation (five to ten business days), production migration (three to seven business days depending on volume), and cutover with delta sync (one to two business days).
What does and does not migrate from Kayako to Zendesk?
We migrate Conversations (tickets) with message threads, Users and Organizations, Knowledge Base articles and their category hierarchy, Tags, and custom field values. We do not migrate automations, triggers, or escalation rules (configuration objects with no portable API); SLA policies (rebuilt from metadata we document); saved reports and analytics (raw data migrates so reports can be rebuilt); integrations with Slack, WhatsApp, voice channels, or third-party tools (OAuth tokens and webhook URLs are source-instance-specific and must be reconfigured in Zendesk); and VoIP configurations (rebuilt in Zendesk's voice settings).
Can we migrate our Kayako Knowledge Base to Zendesk Guide?
Yes, with preparation. Zendesk Guide is a separate product from Zendesk Support and must be activated by the account owner before any articles can be imported. We export Kayako Knowledge Base articles and their category hierarchy, then rebuild the structure in Zendesk Guide sections and categories. Article attachments migrate as Guide article attachments separately from conversation attachments. Only the default language migrates by default; multilingual content requires manual section creation in each additional locale. Enterprise Guide supports article subsections up to five levels deep with a maximum of 20 subsections per parent section, which constrains the hierarchy depth we can replicate from Kayako.
Do Kayako automations migrate to Zendesk Triggers?
No. Kayako automation rules (triggers, conditions, escalation actions) are configuration objects with no portable API export and no direct Zendesk Trigger equivalent. Kayako automations use Kayako-specific event models and action types; Zendesk Triggers use Zendesk's event model and action syntax. We do not migrate automations as code. During discovery, we inventory every active Kayako automation and deliver a written map covering trigger events, conditions, actions, and recommended Zendesk Trigger and Macro equivalents. The customer's Zendesk admin or a Zendesk implementation partner rebuilds these post-migration.
What happens to custom fields during migration?
Kayako custom fields are discovered during scoping using their API field keys (not display names), which must be resolved before migration because API calls referencing the display name silently fail to populate the field. We map each Kayako custom field to a Zendesk custom field of the matching type. An important Zendesk behavior to note: drop-down and multiselect custom fields automatically generate tags from their values during import, which can duplicate existing tags if the source data uses both custom fields and manual tags for the same labels. We document this and recommend a tag-deduplication run as a post-migration step.
How do you handle attachments during migration?
Kayako does not support bulk attachment export. Each Conversation with attachments requires a separate API call to retrieve its files, which makes attachment-heavy accounts significantly slower to extract than clean ticket migrations. We flag any Kayako attachments exceeding the target Zendesk plan's file size limit during scoping. Inline images in message threads migrate as attachments linked to the parent Comment. After migration, we verify a representative sample of attachments to confirm they remain linked to the correct Ticket Comments. The customer should test attachment rendering for common file types (PDFs, screenshots, exported documents) before finalizing cutover.
Do we need to prepare Zendesk before migration begins?
Yes. At minimum, the Zendesk account must exist, agents must be provisioned (matched by email to Kayako Users), and Zendesk Guide must be activated if Knowledge Base migration is in scope. We also recommend disabling Zendesk triggers and automations before the migration run so that historical tickets do not trigger email notifications to customers when imported. SLA policies should be configured in Zendesk Admin before migration so that imported tickets can reference them. We provide a pre-migration checklist during scoping covering all required Zendesk configuration steps and the contacts responsible for completing each item.
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 Kayako 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