Kayako to Freshdesk migration
We migrate Conversations, Users, Organizations, and Knowledge Base content from Kayako into Freshdesk, resolving Kayako's API field-key naming before writes, accounting for Freshdesk's Sprout-tier API restriction, and flagging the Knowledge Base deduplication pattern that appears in Freshdesk community migrations before any record is touched.
FlitStack AI migrates tickets, contact or agents, companies, custom fields and solution articles from Kayako to Freshdesk, 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 Kayako to Freshdesk?
Moving from Kayako to Freshdesk is a migration between two cloud-native helpdesk platforms with different field-naming conventions, tier-based API access, and automation models.
Read the full summary
Kayako's Conversations map 1:1 to Freshdesk Tickets, and Kayako's Users split into Freshdesk Contacts (customers) and Agents (agents), while Organizations map to Freshdesk Companies. The most common migration failure points are Kayako's system-generated API field keys on custom fields (which silently fail if referenced by display name), Freshdesk's Sprout tier lacking API access entirely (requiring Blossom or above before migration runs), and Knowledge Base article duplication in Freshdesk that occurs when the migration tool reimports articles without deduplication checks. We discover all Kayako custom field keys during scoping, pre-create the equivalent Freshdesk custom fields before migration, use the Freshdesk API with exponential backoff, and deliver an automation inventory so your admin rebuilds Kayako automations as Freshdesk Scenario Automations post-migration. Workflows, SLA policies, and saved reports do not migrate as code; we document them for your team to rebuild.
Conversation → Ticket
Kayako Conversations map 1:1 to Freshdesk Tickets.
How it maps
Standard fields (status, priority, assignee, channel, timestamps) map to Freshdesk equivalents (status_name, priority, agent_id, source, created_at). Message threads migrate as ConversationDetails with agent and customer messages preserved in chronological order. We extract conversations via the Kayako Conversations API and insert via the Freshdesk Tickets API, batching in groups of 50 to avoid rate limit saturation.
User → Contact or Agent (split required)
Kayako Users split into Freshdesk Contacts (customers and requesters) and Agents (support staff).
How it maps
We determine the split by examining Kayako's user role assignments and permissions. Contacts get email, name, phone, and custom field values. Agents get name, email, and group assignment. Active/inactive status maps from Kayako's user status field.
Organization → Company
Kayako Organizations map directly to Freshdesk Companies.
How it maps
Organization name becomes the company name, and domain maps to the website field. The organization-to-user linkage is preserved via Freshdesk's customer_id field on Contact records. If Kayako Organizations have custom properties, we pre-create matching Freshdesk company fields before migration.
Custom Fields → Custom Fields
Kayako custom fields have system-generated API field keys that differ from display names, and these keys are required for API writes.
How it maps
We discover all field keys during scoping and map them to Freshdesk custom fields that we pre-create with matching types (text, dropdown, number, date, checkbox). If Kayako custom fields were added after initial setup, we re-verify their keys before migration. Freshdesk Sprout tier does not support custom fields; Blossom or above is required.
Knowledge Base Articles → Solution Articles
Kayako KB Articles map to Freshdesk Solution Articles with category and section hierarchy preserved.
How it maps
Article content, status (draft/published), and view counts migrate. Freshdesk community posts document a known duplication risk where migration tools have re-imported articles multiple times, creating 4x article counts. We implement a pre-migration article ID audit and post-migration deduplication check to prevent this. Article attachments require separate per-article API calls.
KB Categories → Solution Categories
Kayako KB Categories and Sections map to Freshdesk Solution Categories with hierarchical structure preserved.
How it maps
Category names and descriptions migrate directly. If Freshdesk already has categories with conflicting names, we resolve naming collisions during scoping and document the resolution for customer sign-off.
- ConversationTicket1:1
- UserContact or Agentsplit
- OrganizationCompany1:1
- Custom FieldsCustom Fieldstransformed
- Knowledge Base ArticlesSolution Articles1:1
- KB CategoriesSolution Categories1:1
+ 2 more in the mapping below
How Kayako and Freshdesk 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 | Freshdesk |
|---|---|---|
| API access by tier | Full API available on all tiers | API disabled on Sprout (free) tier; requires Blossom ($15/agent/mo) or above |
| Custom field naming | System-generated API field keys distinct from display names | Field names used directly in API calls with pre-created field definitions |
| On-premise option | Had legacy Kayako Classic on-prem; new Kayako cloud-only | Cloud-only; no on-premise deployment available |
| Pricing entry point | $15/user/month Lite tier | Free Sprout tier (2 agents), paid from $15/agent/month Blossom |
| Automation model | Workflow automations with triggers, conditions, and actions | Scenario Automations with different event model and editor UI |
| Knowledge Base | Articles with categories and sections; API-migratable | Solution Articles with categories; known duplication risk during import |
| SLA policies | Configuration-based; migratable as metadata | Business hours and SLA policies scoped per plan; rebuilt at destination |
What to watch for in a Kayako to Freshdesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Kayako custom fields require API field keys, not display names
Kayako generates a system-level API field key for each custom field that is distinct from its admin-display name.
How we handle it
API calls referencing the display name will silently fail to populate the field. We discover all custom field keys during migration discovery and use them in all API writes. If custom fields were added after initial Kayako setup, we re-verify their keys before running any data writes. Freshdesk custom fields must be pre-created by an admin before migration because the Freshdesk API cannot create custom field definitions.
Freshdesk Sprout tier has no API access
Freshdesk's free Sprout plan explicitly disables API access.
How we handle it
Migrations cannot run on Sprout; the destination account must be on Blossom ($15/agent/month) or above. We confirm the destination Freshdesk tier during scoping and flag if API access is not yet enabled. Additionally, Freshdesk requires API activation via email request on Blossom even after upgrading, which adds a short administrative step before migration credentials are issued.
Knowledge Base migration can duplicate articles silently
Freshdesk community posts document cases where Knowledge Base migration tools re-imported articles multiple times, creating 4x article counts.
How we handle it
This occurs when the migration tool does not check for existing article IDs before inserting. We perform a pre-migration audit of existing Freshdesk KB articles and implement a deduplication check before importing Kayako articles, ensuring no duplicate categories or articles land in the destination.
Kayako Classic requires different extraction method than cloud Kayako
If the source Kayako instance is Kayako Classic (on-premise/download legacy product), it uses a different database schema and export mechanism than the current cloud Kayako.
How we handle it
Kayako recommends migrating Classic data via a partner service using API-based transfers. We confirm which Kayako version the customer is running before scoping the migration and apply the appropriate extraction method. Database-direct export is not part of standard scope.
Automations and SLA policies do not migrate between platforms
Kayako workflow automations and SLA policy definitions are configuration objects that do not export via API in a structured, portable format.
How we handle it
Freshdesk's Scenario Automations use a different event model and editor. We document every active Kayako automation and SLA policy with its trigger conditions, actions, and time delays, delivering a written handoff for your admin to rebuild in Freshdesk. Reports and saved analytics similarly cannot migrate as code.
How the migration runs
Discovery and version confirmation
We audit the source Kayako instance to confirm whether it is the current cloud product or Kayako Classic.
What this step covers
We extract record counts for Conversations, Users, Organizations, KB Articles, and attachments, and identify custom field definitions including their API field keys. We confirm the destination Freshdesk tier (Blossom or above required for API access) and identify any existing data in the Freshdesk account that might conflict with incoming records. The discovery output is a written scope with record counts, field mapping draft, and Freshdesk tier confirmation.
Freshdesk pre-configuration
We create all required Freshdesk custom fields to match Kayako's custom field definitions, using Freshdesk admin credentials.
What this step covers
We create Freshdesk Agents with matching email addresses to the Kayako users designated as agents, and configure Freshdesk Groups to match Kayako Teams so that ticket assignments resolve correctly. We disable Freshdesk automation rules that might fire on incoming ticket creation during migration to prevent unwanted notifications or routing during the load.
Demo migration and reconciliation
We run a limited migration of approximately 20 random tickets and KB articles into the Freshdesk account to validate field mapping, attachment handling, and Knowledge Base deduplication.
What this step covers
The customer reviews the migrated sample data and confirms mapping accuracy before we proceed to full migration. Any custom field corrections, tag mapping adjustments, or tag-to-field remapping decisions happen here.
Full migration in dependency order
We run production migration in record-dependency order: Companies (from Kayako Organizations) first, then Contacts and Agents with group assignments resolved, then Tickets with conversation threads and attachments, then Knowledge Base Categories and Articles.
What this step covers
Custom fields are populated on each record using the Kayako API field keys discovered in Step 1. We apply tags from Kayako as Freshdesk tags and implement the Knowledge Base deduplication check before each article batch insert.
Cutover and post-migration validation
We freeze Kayako writes during cutover, run a delta migration of any records created or modified in the migration window, then validate total record counts match the discovery phase totals.
What this step covers
We deliver the automation and SLA inventory document to the customer's admin team for rebuild in Freshdesk Scenario Automations. We support a three-day hypercare window to resolve any record-level reconciliation issues.
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
A quote scales with record volume, Knowledge Base article count, and custom field complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Kayako to Freshdesk →Why teams move from Kayako to Freshdesk
- Kayako's per-agent Elite tier at $79/user/month plus $1/AI-resolved-ticket charges creates unpredictable total cost as ticket volume grows. Freshdesk's tiered pricing (Sprout free, Blossom $15, Garden $29, Pro $49, Enterprise $79) offers predictable per-agent cost without volume-based billing, and teams cited Freshdesk's 4.4 value-for-money rating versus Kayako's 3.8 as a driver in Capterra and G2 comparisons.
- G2 users rated Freshdesk's ticket creation UX at 8.9 versus Kayako at 7.0, and Freshdesk's quality of support at 8.8 versus Kayako's 8.1. Support teams cited Kayako's onboarding ramp-up taking weeks before full productivity, while Freshdesk's interactive tutorial and intuitive feature placement reduced time-to-productivity for new agents.
- G2 reviewers rated Freshdesk's automation features at 8.5 versus Kayako's 8.2, and Freshdesk's multichannel coverage at 8.4 versus Kayako's less-emphasized channel integration. Teams managing email, live chat, WhatsApp, and voice under one inbox cited Freshdesk's unified agent interface as a reason to consolidate after leaving Kayako.
- Freshdesk's Knowledge Base scored 8.7 on self-service experience versus Kayako's 8.6, and Freshdesk offers deeper integration with CRMs and third-party tools (8.3 vs 7.9) including Salesforce, Jira, and Slack at the Pro tier without additional per-integration fees. Teams needing broader ecosystem connectivity preferred Freshdesk's App Marketplace depth.
- Kayako's search functionality across large conversation histories is widely described as insufficient, and the dual-product confusion between Kayako Classic and the new cloud Kayako creates uncertainty for long-standing customers about which export mechanism applies. Freshdesk's cloud-only model eliminates this ambiguity and offers better reporting depth per G2 incident and problem management ratings.
Questions, answered
Kayako to Freshdesk migration questions
How long does a Kayako to Freshdesk migration take?
Most migrations land between two and four weeks for accounts under 10,000 tickets and 2,000 contacts with no complex custom fields or large Knowledge Base. Migrations with Kayako Classic as the source, Knowledge Base volumes over 500 articles, or custom fields across multiple object types (Conversations, Users, Organizations) move to five to eight weeks because of database extraction complexity, KB deduplication verification, and per-attachment API calls.
Do Kayako automations and SLA policies migrate to Freshdesk?
No. Kayako workflow automations and SLA policies are configuration objects that do not export via API in a structured, portable format. Freshdesk's Scenario Automations use a different event model, trigger syntax, and action library. We do not migrate them as code. We deliver a written inventory of every active Kayako automation and SLA policy with its trigger conditions, actions, and recommended Freshdesk Scenario Automation equivalent for your admin to rebuild. Reports and saved analytics similarly do not migrate; we deliver the underlying data so your team rebuilds reports from scratch.
Can we migrate our Kayako Knowledge Base articles to Freshdesk?
Yes. Kayako KB Articles, Categories, and Sections map to Freshdesk Solution Articles and Solution Categories with hierarchy preserved. We implement a pre-migration article ID audit and deduplication check to prevent the known Freshdesk KB duplication issue that has been documented in Freshworks community posts, where migration tools re-imported articles multiple times.
What happens to Kayako custom fields during migration?
Kayako custom fields use system-generated API field keys that differ from display names, and these keys are required for API writes. We discover all field keys during scoping, pre-create matching Freshdesk custom fields with equivalent types (text, dropdown, number, date, checkbox) using Freshdesk admin credentials, then populate them using the correct Kayako API field keys during migration. If custom fields were added after initial Kayako setup, we re-verify their keys before migration runs.
Do we lose attachment files from Kayako conversations?
No. We extract file attachments from Kayako Conversations via the Kayako API using separate per-conversation calls. Each attachment is then uploaded to Freshdesk via the Freshdesk API attachment endpoint and linked to the corresponding ticket conversation detail. Large attachments over 20MB may require chunked upload handling. We flag any size-restricted files during discovery and agree on handling before migration begins.
What Freshdesk tier do we need for migration?
The destination Freshdesk account must be on Blossom ($15/agent/month) or above. The free Sprout tier explicitly disables API access, making automated migration impossible. Additionally, custom fields require Blossom or above because they are not available on Sprout. We confirm the destination tier during scoping and verify that API access has been activated via Freshdesk's email request process before migration credentials are issued.
Will our Kayako conversations maintain their full message history in Freshdesk?
Yes. We migrate the complete conversation thread including all agent and customer messages, internal notes, and system-generated entries in chronological order. Each message detail becomes a Freshdesk ConversationDetail record linked to the parent Ticket. Timestamps, sender identification, and message attribution are preserved. The full message history is visible in Freshdesk's ticket timeline after migration completes.
Related migrations
Sources: official documentation
- Import to Freshdesk — Freshworks Marketplace
- Import and export customers and company information — Freshdesk
- Throughput and plan-tier limits — Freshdesk
- Associating different object types in Freshdesk
- Freshdesk integration reference
- Ticket attachment size limit — Freshdesk Support
- Freshworks Data Import to Freshdesk — Marketplace
Get a quote
Moving from Kayako to Freshdesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.
Get a quote