EU, US and India data residency · a DPA you can sign

Trust Center →

Spiceworks Help Desk to FlowTux

Spiceworks Cloud Help Desk has two exports: Export as… on a report view, and the Exports page for tickets over a time period. Neither is documented as including comments or attachments, so send us a sample before you plan the cutover. Spiceworks’ live docs refuse automated fetches; the facts below come from archived copies of Spiceworks’ own help pages.

Getting your data out of Spiceworks

Each line below was checked against Spiceworks’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.

Report export
Reports > Export as… exports a CSV or JSON file of the current report view: the tickets in the table and the columns you selected. Reporting does not include custom attributes. Source: web.archive.org
Exports page
Exports > New Export > choose the variables > Create Report. Covers tickets or labor for a set time period; Spiceworks emails you when the file is ready. Pick JSON as the output for a migration. Source: web.archive.org
Who can export everything
Admins see reporting for the entire help desk; Techs see only their own statistics. Run the export as an Admin. Source: web.archive.org
On-prem end of life
Spiceworks ended the Desktop 7.5 app at the end of 2021 and took its supporting services offline on 1 December 2023. Its JSON exporter skips attachments larger than 5 MB and attachments on tickets inactive for more than a month. Source: web.archive.org

Not verified

We could not confirm these from Spiceworks’s documentation. Check them in your own account.

  • Whether either cloud export includes ticket comments or attachments.
  • Row limits on the cloud exports.
  • Any public Spiceworks Help Desk REST API. The cloud docs describe only a Power BI connector.
  • Knowledge base export.

Field mapping

What each Spiceworks field becomes in FlowTux. We confirm every row with you before loading.

SpiceworksFlowTuxNotes
Ticket numberOriginal ticket number, kept on the imported ticketSpiceworks field names not verified; match columns to these on the call.
Summary, descriptionTicket title and first message
StatusStatus: Open, In Progress, Resolved, Closed
PriorityPriority: Critical, High, Medium, Low
CategoryCategory, the starting taxonomy Tux AI triages against
CreatorRequester, matched by email address
AssigneeOwner: an Admin or Agent member
Public responsesComment on the ticket thread
Internal notesInternal note, never shown to the requester

What carries over

  • Whatever ticket fields your Spiceworks export contains, mapped to FlowTux values
  • Requesters and owners, matched by email

What does not

  • Inventory and network scan data
  • Help desk rules and custom attributes, unless present in the export
  • Anything the export does not contain, which is why you check first

The Spiceworks plan, step by step

  1. Confirm which Spiceworks you runCloud Help Desk, or the Desktop app that reached end of life in 2021. Desktop exports JSON from /data_migrations/helpdesk on your server.
  2. Inventory what you can get outAs an Admin, create a JSON export on the Exports page for All Time. Open it and check whether comments and attachments are in it.
  3. Send a sampleSend us 50 rows. We tell you what maps, what goes in the ticket body, and what stays in the archive.
  4. Import, verify, repointLoad the window you chose, check counts per status and per month, then point the help desk email at FlowTux.
  5. Run both for two weeksOpen Spiceworks tickets finish where they started.

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 Spiceworks 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

We give a date once we see what your export contains. The parallel run is two weeks either way.

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.

Spiceworks migration FAQ

How do I export tickets from Spiceworks?

In Cloud Help Desk, use Exports > New Export > Create Report and choose JSON, or Export as… on a report view for CSV or JSON. The Exports page emails you when the file is ready.

Is Spiceworks Help Desk still supported?

Cloud Help Desk is. The on-prem Desktop app reached end of life at the end of 2021, and its supporting services went offline on 1 December 2023.

What if the export has no comments?

Then the import carries ticket rows only, and the old system stays readable as the archive for the conversations.

Start with two weeks in parallel

Keep Spiceworks running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.