EU, US and India data residency · a DPA you can sign
Trust Center →Help Scout to FlowTux: the export, the field map, the cutover
Help Scout is clear about this: exporting through the API is the only way to get conversations out. Report exports leave out the threads. Plan on an API pull from the start.
Getting your data out of Help Scout
Each line below was checked against Help Scout’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- UI export
- There is none for conversations. “Exporting data via the API is currently the only means of obtaining data.” Source: docs.helpscout.com
- Report export
- Reports export as CSV or XLSX but exclude thread contents and still-open conversations. Source: docs.helpscout.com
- Plans
- Inbox API limits: Standard 200 calls a minute, Plus 400, Pro 800. The Free plan has no API access. Source: docs.helpscout.com
- Conversations
- GET /v2/conversations returns only active conversations unless you pass status=all. embed=threads includes threads, but chat threads come back truncated. Source: developer.helpscout.com
- Threads
- GET /v2/conversations/{id}/threads. Types include customer, message (agent reply), note, chat, phone and lineitem (system event). Source: developer.helpscout.com
- Rate limiting
- The limit is shared by every user on the account; writes count double. Throttled calls return HTTP 429 with X-RateLimit-Retry-After. Source: developer.helpscout.com
- Attachments
- GET /v2/conversations/{id}/attachments/{attachmentId}/data returns the file as base64. Source: developer.helpscout.com
- Docs
- The Docs API (docsapi.helpscout.net/v1) uses a per-user API key and allows 2,000 requests per 10 minutes for one site. List calls return references; GET /v1/articles/{id} returns the body. Source: developer.helpscout.com
Not verified
We could not confirm these from Help Scout’s documentation. Check them in your own account.
- The maximum page size on the Inbox API.
- Whether Docs article text is returned as HTML.
Field mapping
What each Help Scout field becomes in FlowTux. We confirm every row with you before loading.
| Help Scout | FlowTux | Notes |
|---|---|---|
| number | Original ticket number, kept on the imported ticket | |
| subject, first customer thread | Ticket title and first message | |
| status | Status: Open, In Progress, Resolved, Closed | Map active, pending and closed on the call. |
| mailboxId | Routing input | Export only the mailboxes that move. |
| tags | Category, the starting taxonomy Tux AI triages against | |
| primaryCustomer | Requester, matched by email address | |
| assignee | Owner: an Admin or Agent member | |
| thread type customer / message | Comment on the ticket thread | |
| thread type note | Internal note, never shown to the requester | |
| thread type lineitem | Dropped | System events with no body. |
| customFields | 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. |
| Docs article | Knowledge base article in the Support Portal (write it, import a page by URL, or upload a file) |
What carries over
- Conversations in the window you choose, with notes kept internal
- Customers and users, matched by email
- Tags, as the starting category list
- Docs articles you choose to reload
What does not
- Workflows and saved replies as features; saved reply text is worth keeping as knowledge base material
- Happiness ratings and reports
- Beacon configuration
- Attachments on closed conversations, unless you decide otherwise on the scoping call
The Help Scout plan, step by step
- Check your plan has API accessFree has none. On Standard you share 200 calls a minute with everyone else using the API, so run the pull out of hours.
- Pull with status=allPage /v2/conversations per moving mailbox with status=all and modifiedSince. Without status=all you get only active conversations.
- Fetch threads per conversationUse /threads rather than embed=threads if you take chat, because embedded chat threads are truncated.
- Pull Docs separatelyWith a Docs API key: list articles per collection, then fetch each article for its body.
- Send the export; we map itWe map statuses and tags with you, keep notes internal, and check counts per mailbox and per month.
- Repoint the mailbox and run bothForward the internal mailbox address to FlowTux and run both for two weeks.
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 Help Scout 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
API throughput is your plan’s per-minute limit, shared with your other integrations. 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
Help Scout migration FAQ
Can I export conversations from Help Scout without the API?
No. Help Scout states that the API is currently the only means of exporting conversation data. Report exports exclude thread contents.
Why does the Help Scout API miss closed conversations?
GET /v2/conversations defaults to active conversations. Pass status=all.
How fast can we export from Help Scout?
As fast as your plan allows: 200 calls a minute on Standard, 400 on Plus, 800 on Pro, shared across all users. The Free plan has no API access.
Who does the import?
We do, with you. You send the API export; the FlowTux team maps and loads it on a call.
Start with two weeks in parallel
Keep Help Scout running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.