Kayako vs Zendesk: Architecture, TCO, and Migration Guide

Kayako vs Zendesk: Architecture, TCO, and Migration Guide

Kayako and Zendesk are both helpdesk platforms, but they serve different teams at different scales — and the gap widened in 2026. Zendesk is a mature, enterprise-grade support suite with published per-agent pricing starting at $19/agent/month and scaling well past $200/agent/month once add-ons are included. Kayako has pivoted to an AI-first model called "Kayako One," shifting away from traditional seat-based licensing toward resolution-based billing. If you're evaluating a switch between them — or stuck on a legacy Kayako Classic instance — this guide covers architecture differences, real total cost of ownership, API constraints, known migration failure modes, and the technical steps for a clean migration.

How do Kayako and Zendesk differ architecturally?

Zendesk is a modular platform. Its core ticketing product (Support) handles email, while the Suite tier layers on live chat, messaging, phone, a help center, and AI. Zendesk offers three main support plans — Support, Suite Team, and Suite Professional — plus a quote-only Enterprise tier. Support plans focus on email ticketing and basic automation; Suite plans add omnichannel support and AI Agents. Each module — voice, workforce management, quality assurance, Copilot — is a separately priced add-on. This gives large teams the ability to compose exactly the stack they need, but it also means your final bill is rarely the sticker price.

Kayako takes a different approach. Its "Single View" customer journey unifies every interaction (email, chat, and social) into one continuous timeline, giving agents the full context of a customer's history before responding. The trade-off: Kayako's feature surface is thinner. Kayako has no native integration with any third-party voice system — IVR and CTI are absent entirely, not just limited.

Integration ecosystem is where the gap is starkest. Zendesk has 1,500+ integrations through its marketplace, with deep native connections to Salesforce, Jira, Shopify, and Slack. Kayako connects to over 700 apps via Zapier and webhooks, but native, first-party integrations are limited. If your workflows depend on tight CRM or ITSM coupling, that difference matters practically — Zapier introduces latency, per-task billing, and failure modes that native webhooks don't.

What does Zendesk actually cost in 2026?

Zendesk's published per-agent pricing runs from $19 to $115/month on annual billing, but the real spend is usually higher.

Here's how the tiers break down:

Plan	Annual Price	What It Includes
Support Team	$19/agent/mo	Email ticketing, basic automation, standard reporting
Suite Team	$55/agent/mo	Omnichannel (chat, messaging, social), help center, AI Agents
Suite Professional	$115/agent/mo	Skills-based routing, deeper analytics, SLA management
Suite Enterprise	Quote only	Advanced security, sandbox, custom roles

The catch is add-ons. Zendesk's published plans cover the core help desk, but several capabilities most teams expect are paid extras stacked on top of every seat:

• AI Agents / Copilot — from approximately $50/agent/month
• Quality Assurance (QA) — from approximately $35/agent/month
• Workforce Management (WFM) — from approximately $25/agent/month

Zendesk advertises a $55/month entry point, but a properly configured mid-market team rarely pays anywhere near that. Once you add Copilot, QA, WFM, and per-resolution AI fees, most mid-market teams land between $165 and $265 per agent per month — a figure that appears consistently in third-party analyst breakdowns of Zendesk contracts, though Zendesk does not publish bundled totals.

The other variable: AI resolution billing. AI Agents now bill per resolution ("outcome-based pricing"), not per seat. Zendesk does not publish the per-resolution rate on its pricing page; third-party contract analysis and reseller documentation put the figure at approximately $1.50–$2.00 per resolution. As of January 2026, usage above the committed volume is billed automatically with no cap — meaning a spike in deflected tickets generates an uncapped overage charge.

Verification note: Per-resolution pricing should be confirmed directly with your Zendesk account executive before signing. The $1.50–$2.00 range reflects figures cited in reseller documentation and third-party procurement analyses as of early 2026; Zendesk may negotiate this rate for high-volume commitments.

What does Kayako actually cost in 2026?

Kayako's pricing is harder to pin down because published sources conflict. In 2026, Kayako retired its old per-agent tiers (Inbox at ~$30/agent/month, Growth at ~$60/agent/month, Scale at higher rates) and consolidated into a single offering called "Kayako One."

Some sources report a pure resolution-based model: $1 per ticket successfully resolved by the "Kay" AI agent, with no per-seat fees and no setup fees. Other sources report $79 per agent per month plus $1 per fully AI-resolved ticket on top. A third category of sources reports only the $1/resolution figure with no mention of a base fee.

One more factor: the legacy Kayako Classic platform is in maintenance mode, running on end-of-life PHP versions with no new features being added. If you're still on Classic, migration isn't optional — it's a matter of when and where.

TCO comparison: 10-agent team at 2,000 tickets/month

To make this concrete, here's a side-by-side estimate for a 10-agent support team handling 2,000 tickets per month, assuming 40% AI resolution rate (800 tickets/month deflected by AI):

Cost Component	Zendesk (Suite Professional)	Kayako One ($79/seat model)	Kayako One (no-seat model)
Base seat cost	$115 × 10 = $1,150/mo	$79 × 10 = $790/mo	$0
AI resolutions (800 tickets @ $1.50–$2.00)	~$1,200–$1,600/mo	$800/mo	$800/mo
Copilot add-on	$50 × 10 = $500/mo	Included	Included
QA + WFM add-ons	$60 × 10 = $600/mo	Not available	Not available
Estimated monthly total	$3,450–$3,850	$1,590	$800

The range for Kayako is wide because the pricing model isn't settled publicly. Zendesk's costs are higher but published and predictable — a meaningful advantage when building annual budgets or seeking finance approval. Note also that Kayako One does not offer native QA or WFM tooling, so those costs don't disappear; they shift to third-party tools if needed.

Kayako API rate limits

Kayako does not publish a tiered API rate limit table equivalent to Zendesk's. Based on available documentation and migration practitioner reports:

• Kayako Classic (self-hosted): Rate limits depend on server configuration; no enforced platform limit is documented publicly.
• Kayako Cloud (v1, modern): Rate limits apply per plan but are not published in Kayako's public developer documentation. Kayako support has confirmed limits exist and recommends contacting them before large-volume API operations.

Practical implication: Before beginning any large extraction from Kayako via API, contact Kayako support to request a temporary rate limit increase and get the current limit for your plan in writing. This is the same recommendation Kayako's own migration documentation makes. Running an unbounded extraction without knowing your rate limit risks throttling errors that corrupt partial exports.

Zendesk API rate limits that affect migration

Zendesk API rate limits are account-level and plan-dependent. These numbers directly impact how long a data migration takes.

Zendesk Plan	Rate Limit (req/min)
Support Team / Suite Team	200
Support Professional / Suite Professional	400
Suite Enterprise	700
Suite Enterprise Plus	2,500

The High Volume API add-on increases a qualifying plan's limit to 2,500 requests per minute for the Support and Help Center APIs. It does not stack — it replaces the plan limit, not adds to it. A minimum of 10 agent seats is required to purchase this add-on.

Endpoint-specific limits matter too — and for large migrations, these usually become the actual bottleneck before the account-wide limit does:

• Incremental Exports: 10 requests per minute
• Update Ticket endpoint: 30 updates per 10 minutes, per user, per ticket
• Ticket Import API (POST /api/v2/imports/tickets): Subject to account-wide rate limits, but does not count toward the standard ticket creation endpoint's burst limits

For a migration of 100,000 tickets at 400 req/min (Suite Professional), assuming each ticket requires one import call plus one call to attach comments: estimated minimum extraction/load time is approximately 8–9 hours at sustained throughput, excluding retry overhead.

How to extract data from Kayako

Kayako offers two extraction paths: the REST API and a MySQL database dump. The right choice depends on your volume and version.

Kayako Classic vs. Kayako One: API schema differences

These two platforms have different API schemas, and migration tooling written for one will not work unmodified on the other:

Field / Endpoint	Kayako Classic	Kayako One (Cloud v1)
Authentication	Signature-based (API Key + Secret Key + Salt + generated Signature)	Basic HTTP Auth or OAuth 2.0
Ticket endpoint	/api/v2/tickets (REST-like)	/api/v2/cases
Conversation object	posts	replies
User object	staffusers / users	agents / contacts
Attachments	Linked via attachments sub-resource	Linked via files sub-resource
Rate limits	Server-dependent, not documented	Plan-dependent, not published

Migrations that assume a single schema across both versions will fail silently on field mapping — producing imported tickets with missing conversation history or broken assignee references.

REST API extraction: Kayako Classic uses a signature-based authentication method requiring an API Key, Secret Key, Salt, and a generated Signature. Kayako v1 (the modern cloud version) supports both Basic HTTP Authentication and OAuth 2.0. Migration speed depends on your Kayako plan's API rate limit.

MySQL dump extraction: For migration exports, Kayako supports a full data dump/backup request. The backup is provided as a MySQL dump, with options for database only, attachments only, or database with attachments. Kayako delivers dumps in MySQL format only — no CSV option. Download links expire within 1–7 days of generation.

Before extracting: If you're working with a large dataset, reach out to Kayako support to temporarily increase API rate limits. To avoid unnecessary disruptions, disable all triggers, monitors, and email notifications in Kayako's Administration panel before starting. This prevents automated messages from firing on tickets that are touched during extraction.

How to migrate from Kayako to Zendesk

There is no native migration path between these platforms — no import wizard, no built-in connector. The realistic path is Kayako API extraction (or MySQL database dump) plus Zendesk's Ticket Import API for loading.

Step 1: Prepare the Zendesk target environment

Create a pre-migration checklist:

• Recreate all custom fields from Kayako in Zendesk (matching names, types, required flags, and dropdown options)
• Create agent profiles corresponding to all Kayako agents
• Enable the Help Center if you're migrating knowledge base content
• Disable all triggers and automation on Zendesk — without this step, migrated historical tickets will fire SLA clocks, welcome emails, and auto-assignments against tickets that were resolved months or years ago
• Deactivate ticket conditions in Zendesk
• Set up macros (saved replies) to match Kayako's canned responses

Step 2: Migrate users first

When creating a ticket via the Zendesk API, the requester and assignee Users must already exist in Zendesk. If they don't, the import will either reject the ticket or assign it to a fallback user, silently corrupting your assignee history.

Extract all agents, end-users, and organizations from Kayako. Import them via the Zendesk Users API using bulk endpoints (up to 100 users per request) to stay within rate limits. User passwords are not migrated — plan for a password-reset communication to agents and end-users before cutover.

Step 3: Import tickets and conversations

Use Zendesk's Ticket Import API (POST /api/v2/imports/tickets) rather than the standard Tickets API (POST /api/v2/tickets). This distinction is critical:

• The import endpoint allows you to set created_at and updated_at timestamps, preserving original ticket chronology.
• The standard endpoint overwrites timestamps with the time of the API call, destroying historical ordering.
• The import endpoint also bypasses most trigger and automation evaluation, provided you've disabled automations in Step 1.

Map before you import — not during:

• Status values: Kayako uses open, pending, resolved, closed; Zendesk uses new, open, pending, solved, closed. These are not 1:1 — new in Zendesk has no Kayako equivalent, and resolved in Kayako maps to solved in Zendesk, not resolved.
• Custom fields: Match field types carefully. A Kayako multi-select field may need to become a Zendesk multi-line text field or a custom tag, depending on how you use it downstream.
• Assignees: Map Kayako agent IDs to Zendesk user IDs from Step 2 before the import run. Do not resolve these dynamically during import — it dramatically increases error rate.

Step 4: Handle Knowledge Base hierarchy differences

This is one of the most common failure points in Kayako-to-Zendesk migrations.

Kayako Classic allows articles to exist directly under Categories without an intermediate Folder level. Zendesk Guide requires a strict three-level hierarchy: Category → Section → Article. Any article that exists at the Category level in Kayako has no valid destination in Zendesk without an intermediate Section.

Resolution: Create placeholder Sections for orphaned articles before the KB import. Name them consistently (e.g., "General" under each Category) so they're easy to reorganize after go-live.

If you're migrating Knowledge Base content that includes embedded links or custom HTML formatting, enable the option to "Allow potentially unsafe HTML in Help Center articles" under Zendesk's Security → Security Policies settings before import. Without this, Zendesk will strip or sanitize HTML that Kayako permitted, breaking article formatting.

Step 5: Fix inline images

Kayako stores inline images as embedded URLs pointing to the Kayako instance or as base64-encoded content embedded in the HTML body. After migration, Kayako-hosted URLs become inaccessible — either because the Kayako instance is decommissioned or because authentication is required to access the assets.

Resolution: For each migrated article or ticket comment containing inline images, you must:

1. Download the image from Kayako's storage
2. Upload it to Zendesk as an attachment via the Zendesk Attachments API
3. Replace the src attribute in the HTML body with the new Zendesk-hosted URL

This step is easy to skip in a test migration (the images appear to load from cache) and catastrophic to discover post-cutover when customers report broken images in tickets from the past two years.

Step 6: Handle import API rejections

The Zendesk Ticket Import API returns HTTP 422 (Unprocessable Entity) for the most common field-level errors. Known rejection causes and their resolutions:

Rejection Reason	HTTP Response	Resolution
Requester user ID doesn't exist	422	Ensure user migration (Step 2) completed before ticket import
Invalid status value	422	Remap status values before import (see Step 3)
Custom field type mismatch	422	Audit field type mapping; dropdown values must exist before use
created_at in the future	422	Check timezone handling; normalize all timestamps to UTC
Attachment size exceeds plan limit	422	Zendesk limits attachment size by plan; compress or externalize large files
Malformed HTML in description	422	Strip unsupported tags or enable unsafe HTML in Help Center settings

Log all 422 responses with the source ticket ID, the Zendesk error message, and the offending field. Reprocessing rejections without logging them means you discover missing tickets only after cutover, not during QA.

Step 7: Run a delta migration and cut over

Between your initial full migration and go-live, new tickets will arrive in Kayako. Run a delta pass — extracting only tickets created or updated after your initial migration cutoff timestamp — to capture them. Tag all migrated tickets (e.g., migrated-from-kayako) so they're distinguishable from native Zendesk tickets during the transition period.

For delta migrations to work cleanly, the Zendesk import endpoint must be idempotent for your use case: if a ticket already exists in Zendesk (matched by external ID), the delta pass should update it, not create a duplicate. Set the external_id field on every imported ticket to the Kayako ticket ID to enable this matching.

Step 8: Rollback plan

Define your rollback criteria before cutover, not after. A rollback-capable migration requires:

1. Kayako remains live and writable during the cutover window — do not decommission it until Zendesk has been validated
2. A rollback timestamp — the exact moment Zendesk was set as the system of record; any tickets created in Zendesk after this point need to be manually reconciled if you roll back
3. Agent communication — agents must know the rollback signal (e.g., a Slack message to revert to Kayako) and must not work tickets in both systems simultaneously during the validation window
4. Validation checklist — define pass/fail criteria before cutover: ticket count within X% of expected, attachment accessibility spot-check, SLA clocks firing correctly, routing rules verified on 5 test tickets

If cutover validation fails, revert agents to Kayako immediately, export any Zendesk-native tickets created during the window, and import them into Kayako before decommissioning the Zendesk instance.

What doesn't migrate (and has to be rebuilt)

No automated migration tool can move configuration between platforms with different architectures. These items require manual rebuilding in Zendesk:

• Triggers, workflows, macros, SLA policies, and routing rules
• Reporting dashboards and saved views (Zendesk's reporting schema is different from Kayako's)
• Customer satisfaction survey configurations
• Help center themes and branding
• Agent skill assignments and group memberships

Going Kayako → Zendesk means rebuilding with more options than Kayako offered, which typically takes longer than expected — Zendesk's trigger logic is more expressive than Kayako's, meaning a single Kayako automation may require multiple Zendesk triggers to replicate exactly.

Going Zendesk → Kayako means the reverse: Kayako's automation and reporting is shallower, so plan for deliberate feature loss and identify workarounds before migration, not after.

Compliance: What Zendesk and Kayako actually cover

Zendesk's compliance posture varies by product and infrastructure tier:

• SOC 2 Type II: Applies to Zendesk's main cloud products
• HIPAA: Available via Business Associate Agreement (BAA) on Suite Professional and above; not available on Support Team or Suite Team plans
• GDPR: Applies across Zendesk's cloud products with data processing agreements available
• FedRAMP: Zendesk has FedRAMP authorization specifically for Zendesk for Government, a separate offering deployed on GovCloud infrastructure. The standard Zendesk Suite does not carry FedRAMP authorization. If FedRAMP compliance is a requirement, you must procure Zendesk for Government specifically, not the standard Suite.

Kayako's compliance documentation is less detailed publicly. Kayako Classic instances are self-hosted, so compliance scope depends on your own infrastructure controls. Kayako One (cloud) compliance certifications are not published in detail on the Kayako website as of early 2026; request a compliance summary directly from Kayako before making a decision that depends on it.

Who should choose Zendesk

Zendesk fits teams that need:

• Enterprise-scale ticketing with fine-grained routing, multi-brand support, and SLA management across multiple products
• Deep native integrations with Salesforce, Jira, Shopify, and 1,500+ other tools — not Zapier bridges
• Native voice support including IVR, CTI, call recording, and workforce management
• Predictable, published pricing — even if high, the cost structure is auditable and budgetable
• HIPAA-covered environments — available via BAA on Professional and above
• FedRAMP-covered environments — available via Zendesk for Government only

Budget realistically: $150–$265/agent/month for a mid-market team using Suite Professional with Copilot, QA, and WFM.

Decision rule: If your team exceeds 20 agents, requires native voice, or has integration requirements that Zapier cannot satisfy reliably, Zendesk is the stronger technical choice regardless of cost.

Who should choose Kayako

Kayako fits teams that need:

• A simpler helpdesk with less configuration overhead and a shallower learning curve
• Unified customer journey view across channels without assembling a module stack
• Resolution-based pricing that directly aligns cost with AI automation output — valuable when deflection rates are high and predictable
• An AI layer on top of existing tools — Kay is designed to sit on top of Zendesk, Freshdesk, Intercom, or the Kayako helpdesk itself

On Kay's claimed performance: Kayako's own site describes Kay as an autonomous agent with a claimed 68% resolution rate. No independent benchmark has corroborated this figure. Treat it as vendor-stated until validated against your own ticket taxonomy. Kay is a recent relaunch with limited third-party track record as of 2026.

Decision rule: If your team is under 20 agents, your ticket types are well-suited to AI deflection, and you can validate pricing directly with Kayako, the economics may favor Kayako One — particularly under the pure-resolution model at moderate volumes.

When to stay put (and when to move)

Stay on Kayako if your team is small, your ticket volume is moderate, and the Single View approach genuinely improves agent workflow. The platform does what it does well — it just doesn't do everything.

Move to Zendesk if you're outgrowing Kayako's automation capabilities, need native voice, or your integration requirements keep bumping into Zapier's limits.

Move from Zendesk to Kayako only if you've modeled the resolution-based pricing against real monthly volumes across a 12-month period (accounting for volume spikes) and confirmed you'll save money without losing compliance, voice, or integration dependencies.

If you're on Kayako Classic: the platform is in maintenance mode on end-of-life PHP versions with no new development. The question is not whether to migrate, but where and when. Staying on Classic is a security risk posture decision, not just a feature decision.

Migration complexity by data volume

Data Volume	Tickets	Estimated Migration Duration	Primary Bottleneck
Small	< 10,000	2–4 hours	Field mapping and setup
Medium	10,000–100,000	8–24 hours	Zendesk API rate limits
Large	100,000–500,000	2–5 days	Rate limits + attachment re-hosting
Very large	500,000+	1–3 weeks	Rate limits + delta management + QA

These estimates assume Suite Professional rate limits (400 req/min), standard attachment volumes, and no significant data quality issues in the source. Self-hosted Kayako Classic with large attachment stores, corrupted ticket data, or non-standard character encoding will increase duration at any volume tier.

What doesn't transfer between Kayako and Zendesk: field-level summary

Data Type	Migrates Automatically	Requires Manual Work	Cannot Migrate
Tickets (open/closed)	✓ via Import API	Status remapping	—
Conversation history	✓	Timestamp normalization	—
User accounts	✓	—	Passwords
Custom fields (text, numeric)	✓	Field recreation in target	—
Custom fields (dropdown)	✓	Option recreation in target	—
Attachments	✓	Re-hosting inline images	—
Knowledge base articles	✓	Hierarchy restructuring	—
Triggers / automations	—	Full rebuild	—
SLA policies	—	Full rebuild	—
Routing rules	—	Full rebuild	—
Reporting dashboards	—	Full rebuild	—
Help center themes	—	Full rebuild	—
CSAT configurations	—	Full rebuild	—

---

The hardest part of a Kayako-to-Zendesk migration isn't the data — it's the planning. Field mapping, hierarchy mismatches, inline image re-hosting, automation rebuilds, API rate-limit math, and rollback preparation all compound into a project that's larger than it appears on paper. The migration steps above are the complete technical sequence; work through them in order, validate each step before proceeding, and define your rollback criteria before cutover day.