Help Scout keeps your customer conversations, your customer profiles and your help center articles. Getting them out is possible, but not all from inside the app: Help Scout's own documentation describes one export you can run yourself, one file you ask support for, and an API for everything else. This guide sets out the three, from Help Scout's documentation as read on 12 November 2026, and turns them into a plan for leaving with your history.
The short version
Help Scout's article "Data Export Options" divides it this way:
- In the app: report data from the All Channels, Email, Company and Happiness reports, as a CSV or XLSX file, "with the exception of conversation thread contents".
- On request: "On request, we're able to provide a .CSV file to Help Scout Account Owners containing the names and email addresses of all of your customers. This export does not include conversation history."
- Through the API: "All other data within your Help Scout account can be obtained as needed using one of our APIs. Exporting data via the API is currently the only means of obtaining data." Customer, user and conversation data come through the Inbox API, and help center articles through the Docs API.
So the conversations themselves, what your customers wrote and what you answered, come out only through the API. Plan for that first.
The report export, step by step
Help Scout's article "Export Reporting Data" gives the steps. You need the permission "Reports: Export reporting data".
- Open the Reports menu and choose the report: All Channels, Email, Company or User/Team, or Happiness.
- Set the date range, and a view if you want one, then click the Export/Print icon next to the date filter at the top right, and click Export.
- Check the date range in the window, choose CSV or XLSX, and click Export.
- An email arrives at the address you log in with, with the subject "Data export from Help Scout". Click Download in it. You must be logged in to Help Scout as the same user to finish the download.
Large exports take longer, and several requests are processed one at a time.
What the report export holds, and what it leaves out
For each conversation in range, the file has the conversation's ID and number, type, assignee, status and inbox; the customer's name, email address, phone number and profile URL; the thread count, subject, the dates it was created, last modified and closed, who closed it, its tags, saved replies, workflows, Cc and Bcc, and custom fields. It adds reporting columns such as first response time, replies sent, resolution time and ratings.
What it does not hold, in the article's words: "the conversation thread contents and satisfaction rating comments". Totals and averages are not included, and neither is data on conversations that are still open. Which conversations appear depends on the report. All Channels includes every conversation that had activity in the period, excluding spam and deleted ones; Email includes email conversations resolved in the period.
Two practical notes from the same article. Times in an XLSX file are in UTC, while a CSV uses the time zone your administrators set for the company. And on the Plus plan, custom field values for all inboxes appear in the export.
The report export is therefore an index of your conversations, not the conversations. It is worth having, because it lists every conversation with its customer and dates, but it is not an archive on its own.
The customer list, by request
Inside the app, Customers > Contacts lists your customers, searchable by name, phone, job title, company and email, according to Help Scout's article on the Customers list. That article does not describe an export button. The export route is the one in "Data Export Options": the Account Owner asks Help Scout's support team for the CSV of customer names and email addresses. It has names and email addresses only, and no conversation history. Ask early, since it depends on a reply.
The conversations, through the API
For the conversation threads, the customer profiles in full, and your help center articles, Help Scout points to its APIs: the Inbox API for customers, users and conversations, the Docs API for articles. That is work for a developer, or for a migration service that already speaks Help Scout's API. If you do not have either, find one before you set a date to leave, not after.
A sensible order for an API export is: users and inboxes first, then customers, then conversations with their threads and any attachments you need, then help center articles. Save the raw responses as they come, even if you also convert them; the raw files are the most faithful copy.
A plan for leaving
- Ask for the customer list from support, as the Account Owner.
- Run the report export from the All Channels report, for the whole life of the account, as both CSV and XLSX. This is your index.
- Arrange the API export of conversations with their threads, customers and help center articles, with a developer or a migration service.
- Check the result against the index: the number of conversations, and a few old ones opened side by side with the original.
- Keep everything in two places you control, with the date.
- Only then change plan or cancel.
Your saved replies, workflows and inbox settings are configuration rather than data. The articles above do not describe an export for them, so copy the text of saved replies you want to keep and note how your workflows are set up.
What to look for in the next tool
The test for the next help desk is the one this guide has just walked through: can you get the full conversations out yourself, without a developer and without asking anyone? Look for an export of whole conversations, not only their fields, and a documented import. Software you run on your own computer or server gives you that by design, because the conversations sit in a database you hold.
Sources
- Help Scout docs, Data Export Options, read 12 November 2026.
- Help Scout docs, Export Reporting Data, read 12 November 2026.
- Help Scout docs, Customers List, read 12 November 2026.
Ownware makes software you buy once and run on your own computer or server, including help desk software.
Try the Helpora demo ↗Live, on sample data, no sign-up.