EU, US and India data residency · a DPA you can sign
Trust Center →Kayako to FlowTux: the backup, the field map, the cutover
Kayako has no export button. You either request a full backup, which Kayako charges for and delivers as a MySQL dump, or you pull cases through the API. Choose before you start.
Getting your data out of Kayako
Each line below was checked against Kayako’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- Backup
- Requested through the Contact Us form by the billing contact or an Owner. It carries a service fee: Sales sends a quote and delivers after payment. Source: help.kayako.com
- Format
- MySQL dumps only; CSV is not available. Choose database, attachments, or both. Download links expire in 1 to 7 days. Source: help.kayako.com
- Attachments
- In the backup, attachment files sit apart from the SQL dump and may not be named by ticket id; the dump holds the mapping. Source: help.kayako.com
- API
- Kayako’s alternative: the API returns cases, users, organizations and Help Center articles as JSON. Kayako does not support importing into other systems. Source: help.kayako.com
- Cases and posts
- GET /api/v1/cases.json, then /api/v1/cases/:id/posts.json (filter ALL, MESSAGES or NOTES). Tags only return with fields=+tags. Source: developer.kayako.com
- Rate limits
- Per minute, on some actions only; Kayako publishes no numbers. Throttled calls return 429 with Retry-After. Source: developer.kayako.com
- Knowledge base
- GET /api/v1/articles.json, with attachments at /api/v1/articles/:id/attachments.json. Source: developer.kayako.com
- Kayako Classic
- No end-of-life date is published. 4.98.9 is the latest stable version, maintained for stability and security only. Source: classichelp.kayako.com
Not verified
We could not confirm these from Kayako’s documentation. Check them in your own account.
- The backup fee and turnaround time.
- Numeric API rate limits and the maximum page size.
- Whether the paid backup process applies to Kayako Classic.
Field mapping
What each Kayako field becomes in FlowTux. We confirm every row with you before loading.
| Kayako | FlowTux | Notes |
|---|---|---|
| case id, legacy_id | Original ticket number, kept on the imported ticket | |
| subject, first post | Ticket title and first message | |
| status NEW, OPEN | Open | |
| status PENDING | In Progress | |
| status COMPLETED / CLOSED | Resolved / Closed | |
| priority | Priority: Critical, High, Medium, Low | |
| type, tags | Category, the starting taxonomy Tux AI triages against | |
| requester | Requester, matched by email address | |
| assigned_agent, assigned_team | Owner: an Admin or Agent member | |
| posts (messages) | Comment on the ticket thread | |
| notes | Internal note, never shown to the requester | |
| custom_fields | Ticket body, or archive | FlowTux has no documented custom-field object. Values you need are written into the ticket during import; the rest stay in the archive. Agreed field by field on the scoping call. |
| rating | Not carried | |
| Help Center article | Knowledge base article in the Support Portal (write it, import a page by URL, or upload a file) |
What carries over
- Cases in the window you choose, with messages and notes kept apart
- Status, priority and tags, mapped as in the table
- Requesters and agents, matched by email
- Help Center articles you choose to reload
What does not
- Triggers, monitors and macros
- SLA definitions and satisfaction ratings
- Messenger configuration
- Attachments on closed cases, unless you decide otherwise on the scoping call
The Kayako plan, step by step
- Choose backup or APIThe backup is complete but paid and MySQL-only. The API is free, JSON, and paced by unpublished rate limits. For an internal queue moving a recent window, the API is usually enough.
- If backup: request it nowQuote, signature, payment and delivery take calendar time you do not control. Download within the link’s 1 to 7 day window.
- If API: cases, then posts and notesPage /cases.json with fields=+tags, then /posts.json and /notes.json per case.
- Send the export; we map itWe map statuses and tags with you and check counts per status and per month.
- Close the old doorKayako’s own migration checklist: close conversations, disable customer accounts, and disable the support email under Administration > Channels > Email once intake points at FlowTux.
- Run both for two weeksMany teams keep Kayako for customer conversations and move only the internal queue.
Run both. Decide with data.
The risk in switching helpdesks is not the import. It is committing before you know whether the AI actually closes your tickets. So keep Kayako running, send new tickets to FlowTux, and compare the two queues on live traffic for two weeks. If the numbers do not justify the move, you have lost two weeks and no data.
How long it takes
If you take the backup route, the calendar depends on Kayako’s quote and payment process, not on the import. The parallel run is two weeks.
Migration help is included: we do the import and the field mapping with you on a call, at no extra cost and on every plan. There is no self-serve importer, so nothing loads until you have seen the mapping.
Related
Kayako migration FAQ
Can I export my data from Kayako myself?
Not as a file from the UI. Kayako offers a full backup on request, for a fee, as a MySQL dump. The free alternative is the Kayako API, which returns cases, users and articles as JSON.
Does the Kayako backup come as CSV?
No. Kayako delivers MySQL dumps only and does not help convert them.
Is Kayako Classic end of life?
Kayako has not published an end-of-life date. Its help center lists 4.98.9 as the latest stable version, maintained for stability and security only.
Can we keep Kayako for customers?
Yes. Many teams keep Kayako for external conversations and run FlowTux for the internal queue.
Start with two weeks in parallel
Keep Kayako running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.