EU, US and India data residency · a DPA you can sign
Trust Center →Switching helpdesks
Leave your helpdesk without losing the history
For IT, ops and engineering teams running an internal queue on a tool built for something else. Pick your current tool for the export path, a field-by-field map to FlowTux, and the order to do it in.
How a move to FlowTux works
- 01
Nothing gets switched off
Your current helpdesk keeps running. Open tickets finish where they started; nobody re-keys them.
- 02
You export, we import
You pull the export using the steps on your tool’s page. We map the fields with you on a call and load it. Included on every plan.
- 03
Two weeks in parallel
New tickets land in FlowTux while the old queue drains. You cut over on numbers from your own traffic, or you do not cut over.
Pick the tool you are leaving
ITSM suites
- FreshserviceUI export stops at 10,000 tickets. The API returns 30 days unless told otherwise.Migration guide →
- Jira Service ManagementJira stays. The service desk in front of it moves, and the link back survives.Migration guide →
- ServiceNowMove the incident and request queue. The CMDB and change stay put.Migration guide →
- ManageEngine ServiceDesk PlusCloud uses Zoho OAuth; on-prem uses a technician key. Different export paths.Migration guide →
Helpdesks
- ZendeskUI export needs Zendesk to switch it on. The API works on every plan.Migration guide →
- FreshdeskThe ticket export has no conversations. The account export does.Migration guide →
- Zoho DeskModule export has no threads. Data Backup does, and only the primary contact can run it.Migration guide →
- Help ScoutNo conversation export in the UI. The API is the only way out.Migration guide →
- KayakoNo self-serve export. A full backup is a paid request, delivered as MySQL.Migration guide →
- SpiceworksCloud Help Desk exports tickets as CSV, JSON or XLSX. The on-prem Desktop app reached end of life in 2021.Migration guide →
Not listed? The same model applies to any tool that can export tickets. Tell us what you run.
The checklist every migration needs
- Export threads, not just ticket rows. Several tools’ default exports drop comments.
- Pick the window: open tickets plus 6 to 12 months of closed ones is the usual answer.
- Map people by email address before importing anything.
- Decide on attachments early. Default: open tickets only, the rest stay in the archive.
- Verify by counts per status and per month, then read 20 tickets end to end.
- Redirect intake at the source (mailbox, Slack, portal links), not by asking requesters to change.
The reasoning behind each item is in the ticket history import checklist.
Switching FAQ
Does FlowTux have a self-serve importer?
No. Imports are assisted: you export from your current tool, and the FlowTux team maps the fields with you on a call and loads the data. It is included on every plan.
Do we have to stop using our current helpdesk?
Not to start. Run both for two weeks: new tickets go to FlowTux, open tickets finish in the old tool. Many teams keep their customer-facing helpdesk and move only the internal queue.
How much ticket history should we bring?
Usually all open tickets plus 6 to 12 months of closed ones. That is enough for Tux AI to learn your categories and duplicates. Older history stays readable in the old tool or the export file.
Do automations, macros and SLA policies come across?
No. Routing and priority rules are replaced by Tux AI triage rather than translated. SLA targets are restated in FlowTux. Macro and canned-response text is worth keeping as knowledge base material.
How current are the export instructions?
Every export fact on these pages was checked against the vendor's own documentation on 2026-11-16 and links to it. Anything we could not confirm is marked as not verified.