Conversation history from an export file
Bring help desk history into Response Desk
Export your history from Help Scout, Zendesk or Freshdesk, check the file, map the agents to your team and import. Nobody is emailed and no reply clock starts.
Response Desk is included with Scale.
What carries over
- Conversations with their messages, in their original order and with their original dates
- Private comments, kept as internal notes only your team sees
- Status, mapped to open, pending, resolved or spam
- Agents, matched to teammates by email address or mapped by you
What does not carry over
- Attachment files: names and sizes are kept as references, the files are not downloaded
- Custom fields and custom statuses: reported as not carried over
- A Zendesk or Freshdesk CSV carries only the first message of each ticket, and the check says history is missing
- Intercom: no file layout is supported
What you need
- Export your history from the old help desk yourself. Formspring never signs in to it. Unzip archives first; ZIP files are not accepted.
- A workspace owner or admin, because only they can import.
- A Formspring workspace with Response Desk, which is included with Scale.
How it maps
| In your file or old tool | In Formspring | Note |
|---|---|---|
| Help Scout | JSON export | Conversations with their threads |
| Zendesk | JSON or CSV export | JSON carries every comment; CSV only the first message |
| Freshdesk | JSON or CSV export | Same as Zendesk |
| Agents in the export | Teammates who can open the project | Matched by email, or mapped by you when someone has left |
Addresses and domains
- Imported history does not change where customers write. Point your support address at a Response Desk email channel when you are ready.
- The parsers are tested on sample files written from each vendor's documented layout, not on a real customer export, so read the check carefully.
Check before you commit
Check the file first. Nothing is written; you see the counts, what an import would do, what will not carry over and who handled the conversations.
- File size
- Up to 10 MB; export a date range at a time for a bigger history
Steps
- Export your history from Help Scout, Zendesk or Freshdesk as JSON (or CSV for Zendesk and Freshdesk).
- In Desk settings choose Import, pick the help desk, the project and the file, then check the file.
- Map each outside agent to a teammate, or leave them as names without a login.
- Import. It runs in the background and reports a summary when it finishes.
Reconcile the result
- Compare the number of conversations in the check with the export.
- Open three imported conversations and compare messages, notes and dates.
- Import the same export again: nothing is added twice, and only new messages are appended.
- Read the list of what did not carry over and decide what to do by hand.
What the check reports
The check reads the file you upload and counts it before anything is written.
Sample data
The check lists conversations, messages, private notes, attachments and tags, what an import would create, and what will not carry over. The numbers depend on your file; none are promised here.
Switching over
Import the history, then move new mail to Response Desk. Keep the old help desk read-only until agents have found what they need in the imported history.
Other guides
- Canny - Import a file, with a dry run
- Another link shortener - Import a CSV, row by row
- Hosted form endpoints - Swap the form action; past submissions are a separate file import
- A form tool - Import a CSV or JSON file, with a dry run
- A link-in-bio page - Import a CSV or JSON link list, with a preview
- Calendly - Recreate the page; there is no importer
