Freshdesk CSV: Import Tickets and Contacts Without Duplicate Chaos

Freshdesk Runs on Tickets — CSV Moves History and People

Support and success teams in the US, UK, Australia, Canada, and Europe use Freshdesk (and related Freshworks products) for ticket queues. CSV is how you migrate from Zendesk/Intercom, bulk-load contacts, and export ticket lists for QA or leadership. Agent emails, status names, and custom fields must match the destination portal — close is not enough.

Export vs Import

Clarify the goal.

Step-by-Step: Export Tickets for Analysis

Reporting path.

• Build a filtered ticket view (group, status, date range).
• Export CSV/Excel per Freshdesk’s UI.
• Archive raw as freshdesk-tickets-YYYY-MM-DD.csv.
• Open in Online CSV Editor; keep ticket IDs as text.
• Convert to Excel for stakeholders if needed.
• Document the filter — exports are not “all tickets ever.”

Ticket ID,Subject,Status,Priority,Agent,Created At,Contact Email
18421,Cannot reset password,Open,High,alex@acme.example,2026-05-03T10:22:00Z,user@client.example

Step-by-Step: Import Tickets or Contacts

Migration path.

• Create groups, statuses, priorities, and custom fields in Freshdesk first.
• Download Freshdesk’s import template when available.
• Map source columns (Zendesk, etc.) to Freshdesk fields.
• Use agent emails that already exist in the portal.
• Prefer ISO timestamps for created/resolved fields.
• Clean in Online CSV Editor; dedupe contacts on email.
• Import a 20-row pilot; verify assignment and fields; then full load.

Custom Fields and Separators

Where migrations look fine in the CSV preview and wrong in the UI.

• Dropdown custom fields: values must match allowed options.
• Multi-select fields may need a documented delimiter.
• Company/contact association: import order matters (companies before contacts before tickets).
• Tags: confirm whether CSV creates new tags or rejects unknowns.

Freshdesk vs Zendesk / Intercom CSV

Related playbooks, different schemas.

• Zendesk exports use different status and custom-field shapes — see Zendesk CSV guide.
• Intercom is conversation-centric — remap threads carefully — see Intercom CSV guide.
• Do not expect attachment binaries inside CSV; plan file migrations separately.

Privacy and Locale

Ticket CSVs are personal data.

• Limit who receives full exports (bodies can contain secrets).
• Redact before agency QA when possible.
• UTF-8 for non-English subjects.
• EU/UK GDPR: align retention and access with your DPA.

Common Mistakes

Support ops foot-guns.

• Importing tickets before agents/groups exist.
• Re-running imports without an external id → duplicate tickets.
• Excel destroying ticket IDs.
• Assuming CSV preserves full conversation HTML and private notes perfectly.
• Exporting PII to unrestricted Slack channels.

Best Practices

Migrations deserve change control.

• Version every import file with source system + date.
• Keep a field-map spreadsheet.
• Pilot in a sandbox/trial when available.
• Freeze the old helpdesk after cutover.
• Cleanse CSVs in-browser before upload.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Prep Freshdesk migration sheets in the Online CSV Editor, protect ticket IDs, and convert exports to Excel for ops reviews — useful for US, UK, AU, CA, and EU support teams.

Conclusion

Freshdesk CSV imports succeed when agents, statuses, and custom fields already exist and emails match. Export from intentional filters, pilot migrations, and treat ticket CSVs as sensitive personal data.