Skip to content
Get a quote

How do I migrate tickets and related data from CSV into Zendesk?

Short answer

Zendesk has no CSV ticket import in its interface. Its own article says to use the Ticket Import API. Load organizations and users from CSV with the data importer first, then turn each ticket row and its comments into API calls. The import endpoint sets created_at, updated_at and solved_at and accepts up to 100 tickets per batch.

By

The two-part path

DataNative routeNotes
OrganizationsData importer (CSV)Load first
Users (requesters, agents)Data importer (CSV); agents created with rolesUse skip_verify_email to suppress emails
Tickets and commentsTicket Import API (/api/v2/imports/tickets, create_many for up to 100)No UI import
AttachmentsUpload through the API, then reference the token in a commentFiles can’t be referenced from CSV
Custom fields, tagsSet in the ticket payloadFields must exist first

Steps

  1. Create custom ticket fields and the tags you’ll use. Add a field for the legacy ticket ID.
  2. Import organizations, then users, keeping each one’s source ID in a user field.
  3. Build a lookup from source user IDs to Zendesk user IDs, and from organizations to organization IDs.
  4. Turn each CSV ticket into JSON: requester, assignee, subject, status, tags, custom fields, created_at, updated_at, solved_at, and a comments array. Each comment gets an author_id, body, public flag and its original created_at.
  5. Upload attachments and add their tokens to the right comments.
  6. Post in batches of up to 100 with create_many, and use archive_immediately for closed tickets.
  7. Reconcile: compare ticket counts by status, and spot-check threads and dates.

What the native tool does / where it stops

The Ticket Import API is built for history. It keeps timestamps, accepts several comments with their authors and skips triggers for imported tickets that aren’t closed. What it won’t do is read a CSV. One CSV row per ticket rarely holds the whole conversation either. Most exports put comments in a separate file, or leave them out: Freshdesk’s ticket export, for example, doesn’t include the entire conversation. Check that your source export includes comments before you plan around it.

Where FlitStack AI fits

FlitStack AI loads tickets through the import API with full threads, attachments and original timestamps. It keeps the legacy ticket ID in a custom field and produces a 301 redirect map. See the Zendesk migration page.

Questions, answered

A few useful answers.

Will imported tickets fire triggers and send emails?

Zendesk says triggers won't run on imported tickets with a status other than closed, and people CC'd on imported tickets aren't notified. Check your own triggers on a sample anyway.

Do SLAs apply to imported tickets?

No. Zendesk says metrics and SLAs aren't supported for imported tickets, so historical tickets won't skew SLA reports.

Can I send closed tickets straight to the archive?

Yes. Use archive_immediately for closed tickets. They skip the normal ticket lifecycle and go straight to the archive, which keeps active views clean.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote