EU, US and India data residency · a DPA you can sign
Trust Center →osTicket to FlowTux: export from the database
osTicket’s ticket export is metadata only, and its API can create tickets but not read them. The full history is in MySQL. This page lists the tables that hold it.
Getting your data out of osTicket
Each line below was checked against osTicket’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- CSV export
- Agent Panel > Tickets > Export, filtered by queue or search. It includes only metadata such as ticket id, status, creation date and assignee. Source: docs.osticket.com
- No threads
- An osTicket contributor on the project’s GitHub: you cannot export the issue details or any subsequent messages or responses; export columns are set per queue. Source: github.com
- API
- Only ticket creation is supported (POST /api/tickets.json). There is no read API. Source: docs.osticket.com
- Threads
- thread_entry.type: M is a user message, R an agent response, N an internal note. Source: raw.githubusercontent.com
- Schema
- Tables (prefix ost_ by default): ticket, thread, thread_entry, user, user_email, form_entry_values, help_topic, department, sla, staff, team, file, file_chunk, attachment, faq. Source: raw.githubusercontent.com
- Attachments
- file.bk is the storage backend: D means stored in the database (file_chunk.filedata). Filesystem and S3 storage are plugins. Source: raw.githubusercontent.com
- Agents
- Admin Panel > Agents > More > Export gives a CSV of agents with their department roles. Source: docs.osticket.com
- Knowledge base
- osTicket documents no FAQ export. FAQs live in the faq and faq_category tables. Source: docs.osticket.com
Not verified
We could not confirm these from osTicket’s documentation. Check them in your own account.
- Where subject and priority are stored per ticket (the ticket table has neither column; they appear to live in form values or a runtime ticket__cdata table).
- Which versions cap the CSV export at 25 fields.
Field mapping
What each osTicket field becomes in FlowTux. We confirm every row with you before loading.
| osTicket | FlowTux | Notes |
|---|---|---|
| ticket.number | Original ticket number, kept on the imported ticket | |
| subject (form values) | Ticket title | Not a column on ost_ticket; read it from the ticket details form. |
| status_id (ticket_status) | Status: Open, In Progress, Resolved, Closed | |
| priority (form values) | Priority: Critical, High, Medium, Low | |
| topic_id (help_topic) | Category, the starting taxonomy Tux AI triages against | Help topics are the closest thing to a taxonomy. |
| dept_id, team_id | Routing input | |
| user_id (user_email) | Requester, matched by email address | |
| staff_id | Owner: an Admin or Agent member | |
| thread_entry type M, R | Comment on the ticket thread | M from the requester, R from an agent. |
| thread_entry type N | Internal note, never shown to the requester | |
| sla_id | SLA targets, restated | |
| file, file_chunk, attachment | Attachment, open tickets only | Not copied by default. Open tickets can bring files across; closed tickets keep theirs in the read-only archive. |
| faq | 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 messages, responses and internal notes kept apart
- Help topics, as categories
- Users and agents, matched by email
- FAQs you choose to reload
What does not
- Filters, help-topic routing rules and auto-responders
- SLA plans; targets are restated in FlowTux
- Plugins and custom code
- Attachments on closed tickets, unless you decide otherwise on the scoping call
The osTicket plan, step by step
- Dump and restore a copymysqldump the osTicket database and restore it somewhere private. Export from the copy, not production.
- Join tickets to threadsticket to thread (object_id) to thread_entry. Keep the type column: M, R and N decide comment or internal note.
- Resolve form valuesSubject, priority and custom form fields live in form_entry and form_entry_values, not on the ticket row.
- Locate attachmentsCheck file.bk. D means the bytes are in file_chunk; anything else points to a filesystem or S3 plugin.
- Send the export; we map itWe map help topics to categories and statuses to FlowTux values with you, then check counts per status and per month.
- Repoint email and set a decommission dateMove the support mailbox to FlowTux, run both for two weeks, then take osTicket off the network and keep the dump as the archive.
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 osTicket 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
Most of the work is the SQL extract, which your team or ours writes against your copy of the database. 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
osTicket migration FAQ
Can I export osTicket ticket threads to CSV?
No. osTicket documents that its CSV export includes only metadata such as ticket id, status, creation date and assignee. Threads are in the thread_entry table.
Can I use the osTicket API to export tickets?
No. The osTicket API only supports creating tickets. Export from the MySQL database instead.
How do I tell internal notes apart in osTicket?
In thread_entry, type N is an internal note, M is a message from the user, and R is an agent response.
Where are osTicket attachments stored?
By default in the database, in file_chunk, when file.bk is D. Installs using the filesystem or S3 plugins store them elsewhere.
Start with two weeks in parallel
Keep osTicket running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.