Zendesk to Jira Migration 2026: What Moves, What Breaks, How to Plan
Zendesk to Jira in 2026: integrate or migrate, what moves to JSM, field mapping, export limits and a cutover checklist for IT teams. Plan your move.
Published Updated 13 min read

On this page
- Zendesk to Jira integration or migration? Decide first
- Why do teams move from Zendesk to Jira Service Management in 2026?
- What moves from Zendesk to JSM, and what gets rebuilt?
- How do Zendesk fields map to Jira Service Management?
- Export from Zendesk, import into Jira Service Management
- The Zendesk to Jira Service Management migration plan in phases
- Zendesk to Jira migration failure points
- Zendesk to Jira migration checklist
- Zendesk to Jira migration FAQ
A Zendesk to Jira migration moves your IT ticket history into Jira Service Management (JSM): tickets, public replies, internal notes, attachments, end users, organizations and Help Center articles. Triggers, automations, macros, views and SLA policies do not move. They are rebuilt in JSM.
If support and engineering only need to share work, Zendesk's Jira integration may be enough, so we start with that decision, then cover mapping, export and import limits, a phased cutover plan and a checklist for IT teams moving to the Atlassian stack.
Zendesk to Jira integration or migration? Decide first
An integration links Zendesk and Jira while both keep running. A migration moves the history and retires Zendesk.
Zendesk's Support for Jira integration lets agents link or create Jira issues from a ticket, on Jira Cloud or Data Center and on every Zendesk Suite and Support plan from Team up (Zendesk setup article, edited 30 Apr 2026, as of 20 Oct 2026). It moves no ticket history.
In an announcement edited 28 Apr 2026, Zendesk said "the current migration path to the new integration has been removed", that it will re-list the original app, and that V2 customers "should remain on V2 and will be supported by Zendesk for now" (as of 20 Oct 2026). If you are retiring Zendesk, the integration can still carry escalations during the overlap.
| Choose integration if | Choose migration if |
|---|---|
| Support stays on Zendesk and only escalations go to Jira | Zendesk is being retired, or IT support is consolidating into JSM |
| You need links between tickets and issues, not shared history | Audit or reporting owners need ticket history on one platform |
Why do teams move from Zendesk to Jira Service Management in 2026?
Teams move from Zendesk to Jira Service Management to consolidate onto engineering's tools, and in 2026 dated changes on both sides add pressure. Beyond consolidating onto engineering's tools, these dated triggers push IT teams to JSM.
| Trigger | Date | What the source says |
|---|---|---|
| Service Collection launched | 7 Oct 2025 | JSM, Customer Service Management and Assets in one offering, with Rovo agents (Atlassian blog); customers are free (Atlassian pricing page, as of 20 Oct 2026) |
| Zendesk's Jira integration rolled back | 28 Apr 2026 | Migration path to the new app removed; original re-listed (Zendesk) |
| Cloud is the only new Atlassian target | 30 Mar 2026; 28 Mar 2029 | No new Data Center customers since 30 Mar 2026; Data Center, JSM included, becomes read-only at end of life on 28 Mar 2029 (Atlassian) |
| New JSM IT features | 7 Oct 2026 | AI Change Risk Assessment workflows and Workforce Management generally available (Atlassian Team '26 Europe post) |
| Atlassian price change | 13 Oct 2026 | New list prices for new purchases, renewals and upgrades (Atlassian FAQ) |
List prices (Zendesk and Atlassian pricing pages, as of 20 Oct 2026):
| Plan | Per agent per month | Billing basis |
|---|---|---|
| Zendesk Employee Service Suite Team | $29 ($39 monthly) | Paid yearly |
| Zendesk Employee Service Suite Professional | $99 ($125 monthly) | Paid yearly |
| Service Collection (JSM) Standard | $21.50 | Monthly price shown |
| Service Collection (JSM) Premium | $55.28 | Monthly price shown |
The gap is not a like-for-like saving. Advanced incident, problem and change management have been Premium and Enterprise only since 16 Oct 2024 (Atlassian), so an IT team that runs change control should price Premium. Our Zendesk vs Jira Service Management comparison and Jira Service Management pricing guide go deeper.
What moves from Zendesk to JSM, and what gets rebuilt?
From Zendesk to JSM, tickets, comments, attachments, users, organizations and Help Center articles move as data. Triggers, automations, macros, views and SLA policies are rebuilt.
| What moves (as data) | What gets rebuilt (not migrated) | What's at risk |
|---|---|---|
| Tickets as JSM work items, with subject, description, status, priority and type | Triggers and automations, as JSM automation rules | Internal notes turning public on a CSV import |
| Public replies and internal notes, as comments | Macros, as JSM canned responses (Atlassian JSDCLOUD-631, fixed 15 Jun 2023) | Original comment dates and authors on an API load |
| Attachments and inline images | Views, as JSM queues and filters | Private attachments behind temporary links |
| End users as customers, agents as licensed agents, organizations | SLA policies, as JSM SLA goals and calendars | SLA clocks that keep counting on imported closed issues |
| Custom fields, tags as labels, ticket forms as request types | Form conditions, as request type forms | Requests hidden from the portal |
| Help Center articles, into the Confluence-based JSM knowledge base (Atlassian) | Explore reports and dashboards | Archived tickets missed by list endpoints |
| Incident-to-problem links, as linked work items | Side conversation workflows | Status history, which lives in Zendesk audits |
Zendesk SLA policies track seven metrics, from first reply time to total resolution time (Zendesk, as of 20 Oct 2026). No definition or running timer moves, so keep historical SLA results as data. Zendesk audits are "a read-only history of all updates to a ticket" (Zendesk developer docs); keep them if auditors need status timelines, because JSM history starts at import.
How do Zendesk fields map to Jira Service Management?
Zendesk to Jira mapping turns tickets, forms, statuses and comments into JSM work items, request types, workflow statuses and comments.
| Zendesk | Jira Service Management | Watch for (vendor limit, as of 20 Oct 2026) |
|---|---|---|
| Ticket form | Request type | On CSV import use the request type ID; by name, "request types may not map correctly, affecting portal visibility" (Atlassian KB, updated 28 Aug 2026) |
| Status: new, open, pending, hold, solved, closed, custom (Zendesk developer docs) | Workflow statuses | CSV import maps only to statuses that already exist (Atlassian) |
| Priority: urgent, high, normal, low | Priority | Align with your priority scheme and SLA goals |
| Type and problem_id | Work type and linked work items | Recreate incident-to-problem links as links, not text |
| Requester, CCs and followers | Reporter, participants and watchers | Customers need no license; watchers must already exist in Jira for CSV (Atlassian) |
| Groups, organizations, tags | Jira groups and queues, organizations, labels | Rebuild assignment rules; clean duplicate tags first |
| Custom fields | Custom fields | Zendesk's CSV export leaves out multi-line, multi-select and custom date fields (Zendesk) |
| Attachments | Attachments | Jira Cloud allows 1 GB per file by default, 2 GB at most (Atlassian) |
Status behavior differs
Zendesk moves Pending back to Open when the requester replies, and only the system sets Closed: four days after Solved by default, 28 days as a fallback (Zendesk, as of 20 Oct 2026). Rebuild what you rely on as JSM automation.
Public replies vs internal notes: the trade-off on both sides
Visibility is this pair's main trap. Zendesk's comment public flag is false for "an internal note" (Zendesk developer docs); JSM's is false for "private/internal" (JSM Cloud REST API, as of 20 Oct 2026). The two documented load paths keep different things:
- Jira CSV import carries each comment's date and author account ID, but in JSM spaces "all the comments from your import file will become public" (Atlassian).
- The JSM request comment API sets visibility, but its request body has only two properties, the text and the public flag (JSM Cloud REST API). There is no field for the original date or author.
Neither path keeps visibility, date and author together. Decide which loss you accept, write the original author and time into the comment text where the API can't set them, keep the Zendesk export as the record, and prove in testing that no internal note shows on the portal. We did not run hands-on tests, so this trade-off reflects documented API fields, not a tested load.
Attachments and Help Center articles
Zendesk has no full attachment export. On accounts created on or after 5 Dec 2024, or using messaging, private attachments need authentication and use temporary links, so download them at once (Zendesk, as of 20 Oct 2026). Jira's CSV importer fetches only from URLs your site can reach (Atlassian), so re-host anything behind sign-in. Help Center translations and attachments sit on separate endpoints (Zendesk developer docs).
Export from Zendesk, import into Jira Service Management
Your Zendesk plan decides how you extract history; your Jira load method decides what survives.
| Route | What the vendor documents (as of 20 Oct 2026) |
|---|---|
| Zendesk data export (JSON, CSV, XML) | Suite Growth and above, or Support Professional and above; not on Team plans; the account owner asks Zendesk Customer Support to enable it |
| Zendesk CSV / JSON / XML | CSV has no deleted tickets, comments or descriptions; JSON drops comments on tickets over 1 MB and downloads in 31-day increments above 1 million tickets; XML tops out at 500 MB, roughly 200,000 tickets |
| Zendesk REST API (all plans; rate limits) | Per minute: Team 200, Growth and Professional 400, Enterprise 700, Enterprise Plus 2,500; High Volume add-on 2,500 (Growth or Professional and up, 10 agent seats minimum) |
| Zendesk incremental export | Up to 1,000 items per page; 10 requests per minute, 30 with High Volume |
| Jira CSV import | About 1,500 work items per file, roughly an hour each; not recommended by Atlassian for migrations |
| Jira and JSM REST APIs (rate limits) | 65,000 points per hour global pool for Forge, Connect and OAuth 2.0 apps, reset each UTC hour; API tokens stay on burst limits; 20 writes per 2 seconds and 100 per 30 seconds per issue (page updated 20 Oct 2026) |
For full history, plan on the APIs on both sides.
Zendesk archives tickets 120 days after they close. Search, exports and most ticket endpoints still return them, but Listing Tickets, Listing Ticket Metrics and Listing Ticket Audits do not (Zendesk, edited 1 May 2026). Side conversations have their own endpoint (Zendesk developer docs), so extract them too.
The Zendesk to Jira Service Management migration plan in phases
A Zendesk to Jira migration runs as a controlled change in six phases, each with an owner and a go/no-go gate. Durations depend on volume, rate limits and test runs, so none are given here.
- Discover. Count every object per status, side conversations and CSAT included. List the configuration to rebuild. Agree the history scope with audit and reporting owners.
- Map. Map every object and pick the comment load method. Configure JSM request types, workflows and queues before data arrives.
- Test migration. Load a slice with every request type, archived tickets, long threads, attachments and internal notes. Check it as a customer.
- Cutover with delta sync. Load history in advance, freeze Zendesk briefly, then pick up changes with the incremental export (Zendesk developer docs). Keep the Zendesk Jira app running until the delta lands, then switch email channels and portal links.
- Reconcile. Compare counts per object and status. Sample tickets end to end: comment order, visibility, author, attachments, links. Record sign-off.
- Hypercare. Watch SLA goals and automation, and keep Zendesk read-only until audit owners sign off. For rollback, Zendesk's Ticket Import API sets created_at, solved_at and comment dates, takes up to 100 tickets per request, and does not support metrics or SLAs on imported tickets (Zendesk developer docs, as of 20 Oct 2026).
Fix SLAs on imported history
Closed issues imported by CSV have no history beyond creation, so their SLA keeps counting. Atlassian suggests a custom field that excludes them from SLA goals, or a bulk transition to the same Done status (Atlassian KB, updated 26 Sep 2025). Choose during mapping.
Zendesk to Jira migration failure points
Six failure points recur in Zendesk to Jira migrations. Each comes from documented vendor behavior, so a test migration can catch it before go/no-go.
| Failure point | Why it happens | How to catch it |
|---|---|---|
| Internal notes made public | CSV makes every comment public in JSM spaces | Open migrated tickets as a customer |
| Wrong comment dates or authors | The JSM comment API has no field for either | Compare long threads against Zendesk |
| SLA breaches on old tickets | Imported closed issues have no history | Check SLA fields before go-live |
| Archived tickets missed | Listing endpoints skip them | Reconcile archived counts separately |
| Comments missing | CSV omits them; JSON drops them over 1 MB | Compare comment counts per ticket |
| A slow delta pass | Incremental export at 10 requests per minute | Time the delta in a rehearsal |
Zendesk to Jira migration checklist
This Zendesk to Jira migration checklist has 12 steps, from choosing integration or migration to keeping Zendesk read-only through hypercare.
- Decide integration or migration, and who owns the Zendesk Jira app in the overlap.
- Get Zendesk data export enabled, or plan on the API.
- Count every object per status, archived tickets included, and agree the history scope.
- List triggers, automations, macros, views and SLA policies for rebuild.
- Price Premium if you run change management in JSM.
- Configure JSM request types, workflows, fields and queues first.
- Map forms to request type IDs and every status, custom ones included.
- Pick a comment load method and a rule for original dates and authors.
- Download private attachments and re-host anything behind sign-in.
- Pick your SLA fix for imported history.
- Run a test migration, check it from the portal, and size the freeze window from its timings.
- Reconcile, sign off go/no-go, and keep Zendesk read-only through hypercare.
Facts checked October 20, 2026 from Atlassian pricing, Atlassian CSV import docs, Atlassian rate limiting docs, Zendesk data export and Zendesk API rate limits. No vendor paid for this article. How we research
Zendesk to Jira migration FAQ
Can I migrate Zendesk to Jira with a CSV file?
Partly. Jira's CSV importer handles fields, comments with date and author, and attachments by URL, at about 1,500 work items per file, but Atlassian says it "isn't a recommended migration method" (as of 20 Oct 2026). Zendesk's CSV export leaves out comments, and in JSM spaces a CSV import makes every comment public, so CSV suits only small, public-only histories.
Do Zendesk internal notes stay internal in Jira Service Management?
Only if your load method sets comment visibility. Zendesk flags each comment as public or internal, and JSM's comment API has a matching public flag (vendor docs, as of 20 Oct 2026). A CSV import makes every comment public. The API keeps visibility but has no field for the original date or author, so record those in the comment text and check the result from a customer account.
Does the Zendesk Jira integration move ticket history?
No. Zendesk's Jira integration links or creates Jira issues from a ticket while both tools keep running (Zendesk, edited 30 Apr 2026), so it moves no history. In an announcement edited 28 Apr 2026, Zendesk also removed the migration path to its new V2 app and is re-listing the original. Use the integration for escalations and a migration to retire Zendesk.
How long does a Zendesk to Jira migration take?
There is no neutral public benchmark for Zendesk to Jira moves, and we don't quote one. Duration depends on ticket, comment and attachment volume, your Zendesk API limits (incremental exports run at 10 requests per minute as standard, Zendesk developer docs, as of 20 Oct 2026), the Jira limits for your load method, how many test migrations it takes to reconcile, and how much you rebuild.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


