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

  1. 01

    Nothing gets switched off

    Your current helpdesk keeps running. Open tickets finish where they started; nobody re-keys them.

  2. 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.

  3. 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

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.