Jira Service ManagementZendesk

Jira Service Management to Zendesk migration

ITSM specialists move your work items, public comments and internal comments into Zendesk, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 13 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Jira Service Management to Zendesk at a glance

Moving from Jira Service Management to Zendesk turns each work item and its comments into one Zendesk ticket, imported with its original created, updated and solved dates. Internal comments arrive as internal notes, customers as end users and Confluence knowledge pages as Help Center articles. Jira keeps running until cutover, and a delta pass re-imports what changed.

Objects mapped
13
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Teams that ran customer requests in Jira Service Management and are moving them to Zendesk, often while engineering stays on Jira.
What does not move
Automation rules, workflows, SLA goals, queues and portal forms are configuration. We list each one, with what it does, for your Zendesk admin to rebuild.
What sets the scope
Work item and comment volume, attachments, the number of request types and spaces, the Confluence pages behind the knowledge base, and whether Assets data is needed on tickets.

What moves

What moves from Jira Service Management to Zendesk

Work items become tickets with their whole comment thread, internal comments become internal notes, customers become end users, teams become groups, labels become tags and Confluence knowledge pages become Help Center articles.

  • 13 included
Jira Service ManagementZendesk
  • OrganizationsOrganizations

    Created first, 100 to a call. On new sites they may sit in the Customer Service Management app, which scoping checks.

  • CustomersEnd users

    Created without verification emails once Zendesk has enabled bulk user import.

  • Licensed agentsAgents

    Matched by email to the Zendesk seats you have bought.

  • Teams and assignee groupsGroups

    Each agent keeps the groups they worked in Jira.

  • Work itemsTickets

    Imported with original created, updated and solved dates, and the Jira key in external_id and a searchable field.

  • Request typesTicket forms

    Built in Zendesk first, or kept as a custom field value when one form is enough.

  • Public commentsPublic comments

    Original author and time on each, in thread order.

  • Internal commentsInternal notes

    Imported with public set to false, so end users never see them.

  • AttachmentsAttachments

    Uploaded first and attached to the comment they belong to, read through an agent account so internal files are included.

  • Request participantsCCs

    Copied users get no notification about the import itself.

  • Labels and custom fieldsTags and ticket fields

    Ticket fields and their drop-down values are created before the load.

  • SLA recordsTicket fields

    Met or breached, with target and actual time, for reporting on history.

  • Confluence knowledge base pagesHelp Center categories, sections and articles

    The page tree becomes categories and sections. Authors are kept; the import date becomes the article date.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Jira Service Management to Zendesk as-is

Automation rules, workflow transitions, SLA goals, queues and request type portal forms are Jira configuration, so the Zendesk admin rebuilds them as triggers, SLA policies, views and ticket forms.

ChangelogOn request
In Zendesk: Internal note summaryZendesk writes its own audits, so Jira field history is summarised in one internal note when you want it kept.
Satisfaction feedbackOn request
In Zendesk: Ticket fields or tagsOnly the requester can create a Zendesk satisfaction rating, so past scores are kept as data on the ticket.
Automation rules and workflow transitionsNot migrated
In Zendesk: Triggers and automationsConfiguration, rebuilt by your Zendesk admin from the list we hand over.
SLA goals and calendarsNot migrated
In Zendesk: SLA policies and schedulesSet up again in Zendesk. They apply to tickets created after go-live, not to imported ones.
QueuesNot migrated
In Zendesk: ViewsEach queue's JQL is listed so the matching view can be built.
Knowledge base view permissionsNot migrated
In Zendesk: Help Center visibilityJira Service Management inherits them from the Confluence space, so they are listed and set again in Zendesk.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Jira Service Management to Zendesk migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We agree which service spaces, request types and Confluence spaces move, how request types map to ticket forms, and where Assets and change data go.

    • Access and the user import request

      You0.5 day

      You give us a Jira agent account with access to every space in scope and a Zendesk admin token, and ask Zendesk support to enable bulk user import.

    • Forms, fields and triggers

      Both1 day

      Ticket forms and fields are created in Zendesk, and your admin marks the triggers that email requesters for review before cutover.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, picked for long threads, internal comments, attachments and open requests, imported into Zendesk end to end.

    • You review the sample

      You1 day

      Your team checks comment order and dates, internal notes as an end user, organizations and the SLA fields on closed tickets.

    • Full import

      MigrateX2-3 days

      Organizations and users first, then tickets with their whole thread through the Ticket Import API, then Help Center sections and articles.

    • Delta pass

      MigrateX0.5 day

      Work items changed in Jira since the full import are re-imported as whole tickets, never appended to.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Work items against tickets per space, request type, status and year, comments and attachments per ticket, and every thread that was summarised.

    • Sign-off

      You1-2 days

      Your leads spot-check a random sample, the reviewed triggers go live, and Jira stays read-only until you agree.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 1 solved
  • 5 handled
  • 1 on request
  1. 01SolvedMost critical

    Every comment has to arrive with its ticket

    The problem

    The Ticket Import API takes a whole thread in one call. Comments added afterwards through Update Ticket are limited to 30 updates per 10 minutes per user per ticket, and they count as updates, so triggers run on them again.

    How we handle it

    Each Jira work item is assembled with all of its comments and attachments before it is imported. The delta pass re-imports work items that changed rather than appending comments to tickets already in Zendesk.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  2. 02HandledMost critical

    Open Jira requests can email customers on their first Zendesk update

    The problem

    Zendesk skips triggers on an imported ticket whose status is not closed, but triggers resume as soon as that ticket is next updated. An agent's first touch on a migrated open request can send the customer an email about it.

    How we handle it

    Before cutover your admin and our engineer list every trigger that emails requesters and agree which ones are paused, edited or kept. Open requests are tagged on import, so a trigger condition can leave them out for the first days.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  3. 03Handled

    Response and resolution reporting restarts at go-live

    The problem

    Zendesk does not support metrics or SLAs on imported tickets. Years of Jira history arrive with no first reply time, resolution time or SLA result in Zendesk's own reports.

    How we handle it

    Each work item's Jira SLA outcome (met or breached, target and actual time) is written to ticket fields, and every imported ticket carries a migration tag so reports and views can exclude or include it on purpose.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  4. 04Handled

    Bulk user import is off until Zendesk switches it on

    The problem

    Zendesk's create_many endpoint for users takes 100 users a call, but bulk user imports are off by default and return 403 until the account owner or an admin asks Zendesk Customer Support to enable them.

    How we handle it

    You raise the request with Zendesk Customer Support on day one, before any mapping is final. Customers are then created with skip_verify_email, so none of them receives a verification email from the load.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  5. 05Handled

    Confluence page dates reset in the Help Center

    The problem

    Zendesk Help Center articles accept an author_id on create, but created_at is read-only, so every migrated Confluence page shows the import date. Article subscribers are also emailed about each new article unless notify_subscribers is set to false.

    How we handle it

    Articles are created with the original author and with notify_subscribers set to false. Where the original Confluence date matters, it goes into the article body or a label.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  6. 06Handled

    Zendesk stops a ticket at 5,000 comments

    The problem

    A Zendesk ticket can hold 5,000 comments in total, public and private together, and the API returns a 422 error past that. Jira work items fed by monitoring or automation can carry longer trails.

    How we handle it

    Work items near the limit are found in the export counts. With your agreement, system and automation comments on them are summarised into one internal note, so every human comment still fits.

    Source: Zendesk developer documentation, checked 15 Nov 2026

  7. 07On request

    Assets and change records have no Zendesk object to land in

    The problem

    Jira Service Management keeps CMDB data in Assets and changes as their own work type. None of the Zendesk objects this route writes to (tickets, comments, users, organizations and Help Center articles) is a CMDB or a change record, and Atlassian leaves Assets out of the Jira Cloud backup, so it is exported on its own.

    How we handle it

    Assets attributes your agents need on a ticket become ticket fields, change work items become tickets with a type value, and the rest stays in a dated export file you keep. This is agreed before mapping sign-off.

    Source: Atlassian Support, checked 15 Nov 2026

Technical profile

What makes this route technical

Jira pages the export at 100 comments a read, and Zendesk takes each ticket with its full thread in one Ticket Import call, up to 100 tickets at a time.

Exporting from Jira: threads and history 100 items a page
Jira Cloud's comment and changelog endpoints return 100 items a page by default, so a work item with a long thread or a busy history takes several reads.

Source: Atlassian developer documentation, checked 15 Nov 2026

Exporting from Jira: field history for 1,000 work items at once
Jira Cloud's bulk changelog fetch returns the change history of up to 1,000 work items in one request, filtered to at most 10 field IDs.

Source: Atlassian developer documentation, checked 15 Nov 2026

Exporting from Jira: hourly points apply to apps
Since 2 March 2026 Jira Cloud enforces points-based hourly quotas on Forge, Connect and OAuth 2.0 apps. Traffic sent with an API token is still governed by burst limits alone.

Source: Atlassian developer documentation, checked 15 Nov 2026

Exporting from Jira: customers may sit in another app
Since Service Collection launched in October 2025, customer service features are no longer in Jira Service Management on new sites; Atlassian moved them to the Customer Service Management app.

Source: Atlassian Support, checked 15 Nov 2026

Importing into Zendesk: 100 tickets a call, admins only
Zendesk's Ticket Import API takes one ticket at /api/v2/imports/tickets or up to 100 at /api/v2/imports/tickets/create_many, which runs as a background job. Only admins can call it.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: every comment keeps its own time
Each comment sent through Zendesk's Ticket Import API can carry its own created_at, as long as the time is not before 1970 and not in the future, along with its author_id and public flag.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: copied users are not told
Zendesk sends no notification to users copied on an imported ticket. They hear only about updates made after the import.

Source: Zendesk developer documentation, checked 15 Nov 2026

Importing into Zendesk: closed history can go straight to the archive
With archive_immediately set, a ticket imported as closed skips the normal ticket lifecycle and is created directly in the Zendesk archive. Zendesk suggests it for historical imports of 750,000 tickets or more.

Source: Zendesk developer documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Atlassian and Zendesk documentation. Each fact links its source.

Jira Service Management to Zendesk questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do we migrate from Jira Service Management to Zendesk with full history?

Through the APIs on both sides, not a CSV. MigrateX reads each work item with every comment, attachment and SLA record, then imports it into Zendesk as one ticket with its whole thread through the Ticket Import API. Users and organizations go in first, Help Center articles last, and a delta pass picks up late changes.

Do original request dates and comment dates survive in Zendesk?

Yes. Zendesk's Ticket Import API sets each ticket's created, updated and solved time, and each comment carries its own created time, as long as no date is before 1970 or in the future. Help Center articles are the exception: their created date is read-only, so migrated Confluence pages show the import date.

Will Jira internal comments stay internal notes in Zendesk?

Yes. Every Jira comment marked internal is imported with public set to false, which makes it an internal note that end users cannot see. Attachments are read through an agent account, so files on internal comments come across with them. Your team checks a sample of tickets signed in as an end user before the full import.

Will customers get emails from Zendesk during or after the import?

Not from the import itself: Zendesk skips triggers on imported tickets that are not closed and sends nothing to copied users. The risk comes later, because triggers resume on an open ticket's next update. Your admin reviews every trigger that emails requesters before cutover, and open requests carry a tag those triggers can check.

Will Zendesk SLAs and reports include the migrated tickets?

No. Zendesk does not support metrics or SLAs on imported tickets, so its response and resolution reports start with tickets created after go-live. MigrateX writes each Jira SLA outcome to ticket fields and tags every imported ticket, so you can still report on history and keep it out of live SLA views.

Does the Confluence knowledge base move into the Zendesk Help Center?

Yes. The Confluence pages behind your Jira knowledge base become Help Center articles, with the page tree mapped to categories and sections. Each article keeps its original author, and subscriber emails are switched off for the load. Confluence view permissions are listed so your admin can set Help Center visibility again.

What happens to Jira Assets and change requests in Zendesk?

They need a decision, because none of the Zendesk objects this route writes to is a CMDB or a change record. Assets attributes your agents use on tickets become ticket fields, change work items become tickets with a type value, and anything else stays in an export file you keep. Assets is not in a Jira Cloud backup, so it is exported on its own.

Do Jira request types become Zendesk ticket forms?

Usually, yes. Each request type that customers pick on the portal becomes a Zendesk ticket form with the matching fields, built before the import. Where several request types share the same fields, one form with a custom field for the old request type is often simpler, and we agree that on the scoping call.

Can we keep working in Jira until the switch?

Yes. The export only reads from Jira, so agents keep working requests while the full import runs. At cutover a delta pass re-imports every work item changed since, as a whole ticket rather than added comments, and then customer email and portal links move to Zendesk in one planned window.

What does a Jira Service Management to Zendesk migration cost?

Cost depends on the number of work items, the comments and attachments on them, how many request types and spaces map to forms and groups, and the Confluence pages in your knowledge base. A free sample migration of 100 of your records comes first, and your fixed quote follows within 24 hours.

How it compares

Four ways to run Jira Service Management to Zendesk

The same data, moved four different ways. This is what changes between them.

Object coverage (incidents, problems, changes, requests, KB)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Problems, changes and request items often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Work notes vs comments fidelity

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the Zendesk cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Jira Service Management to Zendesk migration

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your Zendesk move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.