EU, US and India data residency · a DPA you can sign
Trust Center →Freshservice to FlowTux: the export, the field map, the cutover
Freshservice teams have more than a queue to think about: assets, SLA policies, a service catalog. The ticket queue moves. The CMDB does not, and this page says so up front.
Getting your data out of Freshservice
Each line below was checked against Freshservice’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- UI export
- Tickets > apply filters > Export > CSV or Excel > choose fields. Maximum 10,000 tickets per export, delivered by email. Source: support.freshservice.com
- Conversations in the export
- Tick Agent interaction and Customer interaction to include conversation content stored on the ticket. Service request item fields are not in the ticket export. For the full thread, including private notes, use the conversations API. Source: support.freshservice.com
- Account export
- Admin > Account > Export produces XML, emailed to the account’s registered agent email. Source: support.freshservice.com
- API
- GET /api/v2/tickets returns only tickets created in the last 30 days unless you pass updated_since, and only the primary workspace unless you pass workspace_id. per_page maxes out at 100. Source: api.freshservice.com
- Threads
- GET /api/v2/tickets/[id]/conversations returns replies plus public and private notes. Source: api.freshservice.com
- Rate limits
- Per minute, Starter / Growth / Pro / Enterprise: 100 / 200 / 400 / 500 overall, and 40 / 70 / 120 / 140 for List All Tickets (accounts created on or after 2020-09-01). Source: api.freshservice.com
- Attachments
- Returned as objects with an attachment_url. A ticket’s attachments total at most 40 MB. Source: api.freshservice.com
- Assets
- Exporting “All Assets” gives default fields only; type-specific fields need one export per asset type. The API has /api/v2/assets and /api/v2/relationships. Source: support.freshservice.com
- Solutions
- Knowledge base articles: GET /api/v2/solutions/articles?folder_id={id}, then GET /api/v2/solutions/articles/{id}. Source: api.freshservice.com
Not verified
We could not confirm these from Freshservice’s documentation. Check them in your own account.
- Which modules the account XML export contains (problems, changes, assets, attachments).
- Whether attachment_url links expire or need authentication.
- A UI export path for solution articles.
Field mapping
What each Freshservice field becomes in FlowTux. We confirm every row with you before loading.
| Freshservice | 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. |
| urgency, impact | Context on the ticket | Tux AI sets priority from stated impact on new tickets. |
| category, sub_category, item_category | Category, the starting taxonomy Tux AI triages against | The three-level tree flattens into one category list. |
| 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. |
| requester_id | Requester, matched by email address | Pull /api/v2/requesters so ids resolve to emails. |
| responder_id, group_id | Owner: an Admin or Agent member | |
| department_id | Recorded on the ticket | |
| conversation (private: false) | Comment on the ticket thread | |
| conversation (private: true) | Internal note, never shown to the requester | |
| assets, relationships | Stay in Freshservice | Asset names can be written onto tickets as context. |
| 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, with replies and private notes kept apart
- Status, priority and the category tree, mapped as in the table
- Requesters and responders, matched by email
- Solution articles you choose to reload into the knowledge base
What does not
- The CMDB, assets and relationships. FlowTux is not a CMDB; keep Freshservice for ITAM or export assets separately
- Workflow Automator rules, replaced by Tux AI triage rather than ported
- SLA policy objects and their history. Restate the targets in FlowTux
- Service catalog items, approvals, and the problem, change and release modules
- Attachments on closed tickets, unless you decide otherwise on the scoping call
The Freshservice plan, step by step
- Decide where assets liveIf you rely on Freshservice for asset management, keep it for that and move only the ticket queue. If not, export assets per asset type so type fields come with them.
- Pull every workspace, every monthCall /api/v2/tickets with updated_since set to the start of your window, once per workspace_id. Leaving either out silently returns 30 days of one workspace.
- Fetch conversations per ticketOne call per ticket to /conversations. At 400 requests a minute on Pro, that is about 400 tickets a minute, shared with anyone else using the API.
- Send the export; we map itWe flatten the category tree with you, map statuses and priorities, and check counts per status and per month against Freshservice.
- Repoint intakeForward the service desk mailbox and connect Slack. Portal links point to FlowTux; open Freshservice tickets drain in place.
- Run both for two weeksCompare the two queues on real traffic, then reduce Freshservice to the modules you still use, or to read-only.
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 Freshservice 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 UI export is capped at 10,000 tickets per file, so larger instances go through the API, where speed depends on your plan’s limit. Add time if assets need exporting per type. 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
Freshservice migration FAQ
Why does the Freshservice API only return recent tickets?
GET /api/v2/tickets defaults to tickets created in the last 30 days and to the primary workspace. Pass updated_since for older tickets and workspace_id for other workspaces.
Does the Freshservice ticket export include conversations?
The standard CSV or Excel export carries ticket-level fields and is capped at 10,000 tickets. For conversations and notes, Freshservice points to the API or the account XML export.
What happens to our Freshservice CMDB?
It stays where it is. FlowTux handles the ticket queue and triage, not configuration management. Keep Freshservice for assets, or export them per asset type for your records.
Do SLA policies come across?
The targets do, restated in FlowTux. The policy objects and breach history stay in Freshservice.
Is there an automatic Freshservice importer?
No. Imports are assisted: you send the export and the FlowTux team maps and loads it with you.
Start with two weeks in parallel
Keep Freshservice running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.