EU, US and India data residency · a DPA you can sign
Trust Center →Freshdesk to FlowTux: the export, the field map, the cutover
Freshdesk is built for customer support. Teams that ran an internal queue on it usually move that queue and leave the customer side alone. The trap is the ticket export: Freshdesk says it does not include conversations.
Getting your data out of Freshdesk
Each line below was checked against Freshdesk’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- Ticket export
- Tickets > All tickets > apply filters > Export > CSV or Excel. Admins and Supervisors only. Freshdesk: “This export will NOT give you the entire conversation from the ticket or historical data (archived tickets).” Source: support.freshdesk.com
- Account export
- Admin > Account > Account Details > Export data. Account Administrators only. Source: support.freshdesk.com
- Export API
- POST /api/v2/account/export with resources such as tickets (with notes and attachments), archive_tickets, contacts, companies, groups and solutions, then poll GET /api/v2/jobs/[id]. Source: developers.freshdesk.com
- List tickets
- GET /api/v2/tickets returns only the last 30 days by default (use updated_since) and stops at 300 pages, 30,000 tickets. Source: developers.freshdesk.com
- Archived tickets
- Closed tickets inactive for 120 days are archived. Read them from /api/v2/tickets/archived/[id] and /api/v2/tickets/archived/[id]/conversations. Source: developers.freshdesk.com
- Rate limits
- Per minute, account-wide: Growth 100, Pro 400, Enterprise 700. Ticket list calls have lower sub-limits of 40, 100 and 200. Source: developers.freshdesk.com
- Attachments
- Returned as objects with an attachment_url; a ticket’s attachments total at most 20 MB. Source: developers.freshdesk.com
- Solutions
- Knowledge base: /api/v2/solutions/categories, /categories/[id]/folders, /folders/[id]/articles. Source: developers.freshdesk.com
Not verified
We could not confirm these from Freshdesk’s documentation. Check them in your own account.
- The account export UI format today (an older Freshdesk article says XML; the API offers JSON).
- Whether attachment_url links expire or need authentication.
- Any row cap on the UI ticket export.
Field mapping
What each Freshdesk field becomes in FlowTux. We confirm every row with you before loading.
| Freshdesk | FlowTux | Notes |
|---|---|---|
| id | Original ticket number, kept on the imported ticket | |
| subject, description_text | Ticket title and first message | |
| status 2 Open / 3 Pending | Open / In Progress | |
| status 4 Resolved / 5 Closed | Resolved / Closed | |
| priority 1 Low to 4 Urgent | Priority: Critical, High, Medium, Low | 4 Urgent becomes Critical. |
| type, tags | Category, the starting taxonomy Tux AI triages against | |
| source (1 Email, 2 Portal, …) | Recorded on the ticket | |
| requester_id | Requester, matched by email address | |
| responder_id, group_id | Owner: an Admin or Agent member | |
| company_id | Recorded on the ticket | |
| conversation (private: false) | Comment on the ticket thread | incoming: true marks the requester’s messages. |
| conversation (private: true) | 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. |
| solution article | Knowledge base article in the Support Portal (write it, import a page by URL, or upload a file) |
What carries over
- Tickets in the window you choose, archived ones included, with conversations and private notes kept apart
- Status, priority and type, mapped as in the table
- Requesters and agents, matched by email
- Solution articles you choose to reload
What does not
- Automations, dispatch rules and scenario automations
- Canned responses as a feature; their text is worth keeping as knowledge base material
- SLA policies and CSAT survey history
- Forums and the customer portal configuration
- Attachments on closed tickets, unless you decide otherwise on the scoping call
The Freshdesk plan, step by step
- Decide which groups moveSplit by group: internal requests move, customer support stays. Export only the moving groups.
- Use the account export, not the ticket CSVRun POST /api/v2/account/export with tickets and archive_tickets, including notes, for your window. The ticket CSV has no conversations.
- Or page the API with updated_sinceIf you page /api/v2/tickets instead, set updated_since: without it you get 30 days. Fetch archived tickets through the archived endpoints.
- Send the export; we map itWe map statuses, priorities and groups with you, then check counts per status and per month against Freshdesk.
- Repoint intakeForward the internal support mailbox to FlowTux and connect Slack. Open Freshdesk tickets drain in place.
- Run both for two weeksThen remove the internal groups from Freshdesk.
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 Freshdesk 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
The account export runs as a background job you poll; Freshdesk does not publish how long it takes. 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
Freshdesk migration FAQ
Does the Freshdesk ticket export include conversations?
No. Freshdesk states the ticket export will not give you the entire conversation or archived tickets. Use the account export, or the API conversations endpoints.
Why does the Freshdesk API only return 30 days of tickets?
List Tickets defaults to tickets created in the last 30 days and stops at 300 pages. Pass updated_since to reach older tickets.
Can we keep Freshdesk for customers?
Yes. Most teams move only the internal queue and keep Freshdesk for customer support.
Who does the import?
We do, with you. You send the export; the FlowTux team maps and loads it on a call. There is no self-serve importer.
Start with two weeks in parallel
Keep Freshdesk running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.