How to Export Tickets from Freshdesk Before You Migrate

By the end of this tutorial you will have a verified, safely stored export of your Freshdesk tickets, contacts and companies, ready to import into a new helpdesk or keep as an archive. You need three things first: admin access to your Freshdesk account, a spreadsheet tool that can open CSV files, and a few hours when no one is mid-way through a big support push.

Freshdesk's menus, export limits and available formats can differ by plan and change over time, so treat the steps below as a general workflow and confirm exact details in Freshdesk's current help documentation.

Step 1: Decide what you actually need to move

Before you export anything, write down what the new setup needs. Many teams assume they need everything, then find that most old tickets are never looked at again.

A practical way to split it:

• Must have: contacts (names and email addresses), open and pending tickets, and any tickets tied to ongoing customer issues.
• Nice to have: closed tickets from the last year or so, useful as reference when a returning customer writes in.
• Archive only: older resolved tickets. These can live in a spreadsheet or file store rather than in your new tool.

This matters because the scope decides which export options you use and how much cleanup you need. Smaller scope means fewer places for errors to creep in.

Step 2: Check your permissions and plan

Exporting is usually restricted to account admins. If you can't find the export option, ask the account owner to grant access or run the export for you. Also check whether your plan limits how much data you can export at once, or how often.

Do this early. Finding out on cutover day that you lack permission is a common and avoidable delay.

Step 3: Clean up before you export

Export data reflects whatever is in your account today. Cleaning first saves you from carrying clutter into a new system.

1. Close or resolve tickets that are genuinely finished.
2. Delete or mark spam tickets so they don't pad your export.
3. Merge obvious duplicate contacts (the same person under two email addresses, for example).
4. Note any custom ticket fields, tags and statuses you rely on. You will want to map these later.

If you want a record of how things looked before cleanup, take your first export before you start deleting, then export again afterward.

Step 4: Export your tickets

In Freshdesk, the data export tools are generally found in the admin settings, under an area labeled something like "Export data" or similar. The wording may differ by version.

1. Open the admin settings and look for the ticket export option.
2. Choose a date range. For large accounts, exporting in chunks (by year or quarter) is usually safer than one huge file.
3. Select the fields to include. Pick more than you think you need: ticket ID, subject, status, priority, requester email, assigned agent, created and resolved dates, tags and any custom fields.
4. Choose the file format offered (CSV is the most portable) and start the export.
5. Download the file when it is ready. Exports are often delivered by email or as a download link, so check your inbox if nothing appears right away.

Why fields matter: you can't add a field to a finished export. If you leave out requester email, for example, you won't be able to connect tickets to customers later.

Step 5: Export contacts and companies separately

Tickets and contacts are typically separate exports. Run the contact export (and the company export if you use companies) and keep the files together with your ticket files.

This step is easy to forget, and it is important because the requester email is what links a ticket to a person in almost any system you move to.

Step 6: Check what the export leaves out

A ticket export file often contains ticket-level fields but may not include the full back-and-forth conversation or attachments, depending on the method and your plan. Check this directly rather than assuming:

• Open a ticket in Freshdesk that has a long thread and an attachment.
• Find the same ticket in your export file.
• See whether the full conversation text and attachment files are present.

If they are missing and you need them, look at what else Freshdesk offers: other export options, reporting exports, or its API (which usually needs a developer or a technical teammate and has rate limits). If you only need conversations for a small set of important tickets, saving those individually as PDFs or forwarding the key threads may be simpler than a full technical extraction.

Step 7: Verify the export

Never trust a file just because it downloaded. Spend ten minutes checking it:

1. Count rows. Compare the number of tickets in the file against the count in Freshdesk for the same date range.
2. Spot-check five to ten tickets. Pick a mix: old, new, closed, open, one with custom fields. Compare each against the live ticket.
3. Check special characters. Open the file and look at names or subjects containing accents, non-Latin characters or emoji. If they look garbled, the file may need to be opened as UTF-8.
4. Check dates and time zones. Confirm that created and resolved timestamps match what you see in Freshdesk, and note which time zone the export uses.
5. Look for blanks. Empty requester emails or missing statuses can cause problems on import.

Step 8: Store the export securely

Your export contains customer personal data, often in plain text. Treat it accordingly:

• Store it in a restricted location, not a shared desktop or a public folder.
• Share it only with people who need it.
• Keep a clearly named backup copy (for example, with the export date in the filename).
• Check your own data retention and privacy obligations for how long you may or must keep it. This varies by country and industry, so confirm details for your situation.

Step 9: Plan the cutover before you cancel

A good export is only half a migration. Before shutting anything down:

• Keep your Freshdesk account active until you have confirmed your data in the new system or your archive.
• Decide when customer email starts flowing to the new tool. Many teams run both in parallel for a short period, with new conversations going to the new inbox while old ones finish in Freshdesk.
• Check your billing cycle. Freshdesk pricing starts at $15 per agent per month, though prices change, so check current pricing and your renewal date to avoid paying for an extra cycle by accident.

If you are considering NeuraDesk as the destination, it is free to start with no credit card, so you can set up a shared inbox and try it with new email while Freshdesk is still running. Whether you move old tickets in or keep them as a searchable archive is a decision for your team, and for many small teams an archive of recent history is enough.

Common mistakes to avoid

• Exporting once and cancelling immediately. If something is missing, you can't go back. Keep the old account until you've verified the data.
• Skipping contacts. Tickets without matching contact records are hard to reconnect.
• Not checking for conversations and attachments. The export may not include them, and you'll only find out when you need them.
• Forgetting custom fields, tags and statuses. Document them before you leave, since their names may not exist in the new tool.
• Leaving the file unprotected. A CSV of customer emails and issues is sensitive data.
• Exporting everything in one giant file. Large files are harder to open, check and troubleshoot. Split by date range.

A quick checklist

1. Define scope: must have, nice to have, archive.
2. Confirm admin access and plan limits.
3. Clean up tickets and contacts.
4. Export tickets with all relevant fields, in date chunks.
5. Export contacts and companies.
6. Check whether conversations and attachments are included.
7. Verify row counts and spot-check records.
8. Store files securely.
9. Run both systems in parallel, then cancel Freshdesk only after confirming everything.

Done carefully, the export is a one-afternoon job for most small teams, and the files you end up with are useful whichever helpdesk you choose next. When you’re ready for a free shared inbox to handle new tickets while you keep your archive, try NeuraDesk free.