Jira Service Management to Zendesk migration
We migrate Requests, comments, attachments, and SLA definitions from Jira Service Management into Zendesk Tickets with user-type reconciliation resolved during scoping, asset-to-organization linkage reconstructed from JSM's object schema export, and every JSM custom field mapped to a typed Zendesk custom field before cutover.
FlitStack AI migrates tickets, group + views, tag + view filters, sla policies and ticket comments from Jira Service Management to Zendesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Jira Service Management to Zendesk?
Moving from Jira Service Management to Zendesk is a migration from a developer-first ITSM platform to a customer-service-native help desk.
Read the full summary
Jira Service Management structures its data around Projects, Request Types, and Requests; Zendesk uses Tickets organized by Views with Triggers, Macros, and Automations managing routing and escalation. The primary technical challenge is that JSM's Request Type fields and custom field schemas are project-scoped and vary per service project, requiring a field-by-field discovery pass before mapping. We preserve SLA definitions (if the destination Suite tier supports them), reconstruct the link between Assets objects and originating Requests using JSM's issue-to-asset relationship API, and reconcile agent versus customer user types so that the destination does not bill portal-only users as agents. Workflows, Automation Rules, and Knowledge Base articles in Confluence do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild on Zendesk Guide and with Zendesk business rules.
Request → Ticket
JSM Requests map directly to Zendesk Tickets.
How it maps
The JSM Request summary becomes the Ticket subject, description migrates as the Ticket comment body, priority maps to Zendesk priority (urgent/high/normal/low), and status (Open, In Progress, Pending, Resolved, Closed) maps to Zendesk ticket status. Request key (e.g., JSM-1234) is stored in a custom Zendesk field for traceability. Custom fields on the JSM Request Type are discovered via the metadata API, typed, and created as Zendesk custom fields before import.
Service Project → Group + View
JSM Service Projects encapsulate Request Type lists, team permissions, portal settings, and SLA definitions.
How it maps
We split each Service Project into a Zendesk Group (for agent routing and permissions) and one or more Views that filter Tickets by the relevant Request Type tags we apply during import. Portal branding and allowed-domain settings from the JSM project are documented in the rebuild handoff for the customer's Zendesk admin to reconfigure in Guide settings.
Request Type → Tag + View filter
JSM Request Types define the intake form shown to customers.
How it maps
Zendesk has no direct Request Type equivalent; instead we apply a tag per Request Type (e.g., tag: hardware-request, password-reset) during import and create Views that filter by those tags to replicate the Request Type routing logic. If the customer needs mandatory fields per Request Type, we recommend Zendesk's Ticket Forms (available from Suite Growth) as the equivalent.
SLA Definition → SLA Policy
JSM SLA goals, starting conditions, and pause conditions (available in Premium and Enterprise) map to Zendesk SLA Policies (Suite Team and above includes limited SLA; Suite Growth and above includes full SLA goals with business hours configuration).
How it maps
We translate JSM's Calendar-based start conditions and pause conditions to Zendesk's first_reply_time and next_reply_time metric definitions, preserving the original goal hours in a custom field for audit. If the source JSM is Standard tier with no SLA data, this mapping step is skipped.
Comment and Internal Note → Ticket Comment
JSM public comments and internal notes both migrate to Zendesk ticket comments.
How it maps
Internal notes in JSM are flagged with a public: false attribute; we set the Zendesk comment visibility to internal by placing it in the comments array with author_id pointing to the agent. Public comments migrate as public Zendesk comments. The original author, timestamp, and body text are preserved. Attachments embedded in comments are handled in the attachment pass after the parent ticket is created.
Attachment → Ticket Attachment
File attachments on Requests and comments are downloaded from Atlassian's CDN and re-uploaded to Zendesk via the Zendesk Attachments API.
How it maps
Large attachment batches (exceeding 20 MB or 100 attachments per batch) are chunked to avoid timeout. Original filenames are preserved. If an attachment was attached to an internal note in JSM, it is re-attached to an internal comment on the Zendesk ticket to maintain visibility semantics.
- RequestTicket1:1
- Service ProjectGroupsplit
- Request TypeTagtransformed
- SLA DefinitionSLA Policytransformed
- Comment and Internal NoteTicket Comment1:1
- AttachmentTicket Attachment1:1
+ 6 more in the mapping below
How Jira Service Management and Zendesk differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Jira Service Management | Zendesk |
|---|---|---|
| Primary ticket object | Requests organized under Service Projects and Request Types | Tickets organized by Views with Tag-based routing |
| SLA availability | Premium and Enterprise only; Standard tier has no SLA | Suite Team and above: limited SLA; Suite Growth Professional Enterprise: full SLA goals with business hours configuration |
| Asset management | Native Jira Assets CMDB with object schemas and cross-object references | No native CMDB; asset data migrates as custom fields or requires a third-party asset management add-on |
| Knowledge base | Articles live in Confluence spaces linked to JSM projects | Zendesk Guide with article sections, translations, and community content native to the platform |
| Automation model | Automation rules with Jira-specific triggers, conditions, and actors | Triggers, Automations, and Macros with email and action-based conditions |
| API rate limiting | Points-based model introduced 2026 affecting Forge, Connect, and OAuth 2.0 apps | Per-minute and per-hour rate limits on Zendesk REST API, varying by endpoint and plan tier |
| User licensing | Per-agent billing; customer portal users are free | Per-agent on Suite Team; Suite Growth and above includes end-users without per-seat charges |
What to watch for in a Jira Service Management to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
JSM custom fields are project-scoped and require field-by-field discovery
JSM custom fields can vary per service project, meaning the same named field may exist in one project with a different data type in another.
How we handle it
The Jira metadata API returns a combined list of all custom fields across all projects, which does not reflect the per-project scope. We run a project-by-project field discovery pass before mapping, extract the field type and options per project, and create Zendesk custom fields per project-equivalent View. Skipping this pass results in type mismatches where a JSM multi-select in one project lands as a single-select in Zendesk, silently dropping values.
Asset-to-Request linkage is absent from JSM CSV export
JSM's Assets object schema CSV export captures object data but omits the connections between Assets objects and Jira Issues.
How we handle it
We query JSM's issue-to-asset relationship API before export to reconstruct which Assets are linked to which Requests, then store those references as Organization-level custom fields or a separate custom Zendesk object during import. Without this pre-pass, all asset data migrates but appears orphaned from the originating tickets, which breaks asset lookup workflows that support teams rely on for hardware and license tracking.
Automation rules and Jira-specific triggers do not migrate to Zendesk
JSM automation rules use Jira-specific constructs (JQL conditions, issue-link triggers, sprint-based conditions, and rule actors) that have no equivalent in Zendesk Triggers and Automations.
How we handle it
We export the rule logic and conditions as JSON for documentation but do not translate them to Zendesk syntax. The customer's admin must rebuild routing logic, escalation policies, and notification automations using Zendesk's Trigger and Automation builder. We deliver a written inventory of every active JSM automation with its trigger type, conditions, and recommended Zendesk Trigger or Automation equivalent.
Zendesk field syncing and Jira integration are being deprecated
Zendesk's legacy Jira field syncing integration is deprecated as of April 27, 2026 per Zendesk's documented migration path.
How we handle it
If the customer's migration scope includes a bidirectional Jira-Zendesk sync setup (where Zendesk tickets link to Jira issues for engineering handoff), the legacy field sync will stop functioning after the migration window. We document any active Jira-Zendesk integration endpoints in the scope discovery pass and flag them for the customer to reconfigure using the current Zendesk-Jira integration or a third-party sync tool post-migration.
Time zone and business hours must align between JSM and Zendesk
JSM stores SLA calendar definitions with a timezone reference that must match the Zendesk business hours configuration for SLA policies to calculate correctly.
How we handle it
If JSM's SLA calendar uses a timezone that differs from the Zendesk Schedule (business hours), SLA breaches and resolutions will be miscalculated post-migration. We extract the JSM SLA calendar timezone during discovery, configure a matching Zendesk Schedule, and flag any discrepancy larger than one hour for the customer's admin to resolve before production cutover.
How the migration runs
Discovery and field-by-field scoping
We audit every JSM service project via the REST API metadata endpoint, listing all Request Types, custom fields, SLA definitions, and automation rules per project.
What this step covers
We extract the asset object schema and query the issue-to-asset relationship API to capture linkage data. We identify active Jira-Zendesk integration endpoints if any exist. The discovery output is a written migration scope document that lists every JSM custom field with its project, type, and Zendesk custom field target, plus a flag for any SLA calendars and automation rules requiring rebuild.
Zendesk environment preparation
We configure the Zendesk destination: Groups per JSM service project, Views per Request Type, SLA Policies translated from JSM definitions (if the Suite tier supports them), Ticket Forms if the customer uses multiple intake types, and custom fields typed to match JSM's field-by-field discovery.
What this step covers
We set business hours and timezone to match JSM's SLA calendar configuration. We disable Triggers and Automations that would fire on incoming tickets during import to prevent notification spam during migration.
Asset linkage pre-pass and user reconciliation
Before any ticket migration, we run the JSM asset relationship pre-pass to capture every issue-to-asset link.
What this step covers
We reconcile JSM agents and portal users by email against the Zendesk user table, flagging any unmatched users for the customer's admin to provision. We set user_type explicitly on every imported user to prevent portal-only users from counting as billable agents. We create Organization records in Zendesk for any asset ownership mapping.
Sandbox validation and mapping sign-off
We run a full migration into a Zendesk staging environment using production-like data volume.
What this step covers
The customer's service desk lead reconciles record counts (Requests in, Tickets out, Comments in, Attachments in), spot-checks 25-50 tickets against JSM source records for field accuracy and SLA preservation, and reviews the asset linkage on sample tickets. Any mapping corrections happen in staging before production cutover.
Production migration in dependency order
We run production migration in record-dependency order: Organizations and Users first, then Tickets with Request Type tags and custom field values, then Comments and internal notes preserving audit trail, then Attachments linked to parent tickets, then Change History as internal audit comments, then Asset data as Organization-level custom fields or separate custom records.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We use Zendesk's REST API with batch chunking and exponential backoff on rate limit responses.
Cutover, delta sync, and automation rebuild handoff
We freeze JSM writes during the cutover window, run a final delta migration of any Requests modified during the migration, then point the customer portal and email routing to Zendesk.
What this step covers
We deliver the Automation and SLA inventory document listing every JSM rule and SLA with a recommended Zendesk Trigger, Automation, or SLA Policy equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild JSM automations or Confluence articles inside the migration scope; that work is handled by the customer's Zendesk admin or a Zendesk implementation partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, Request Type schema complexity, and whether SLA and asset data require preservation. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Jira Service Management to Zendesk →Why teams move from Jira Service Management to Zendesk
- Organizations outside of IT report that JSM's Jira-native interface creates adoption friction for HR, facilities, and finance teams. Reviewers on G2 and Reddit describe the platform as developer-first with a steep learning curve for non-technical requesters and agents. Zendesk's agent interface is designed for customer service workflows with less configuration overhead, which reduces the time from onboarding to first resolved ticket for teams that do not have a developer background.
- JSM's per-agent pricing with Premium-gated SLAs and advanced analytics creates bill shock as teams grow beyond proof-of-concept scale. Reviewers on Capterra and comparison blogs note that Standard tier excludes SLA goals entirely, while Premium starts at approximately $38 per agent per month annually. Zendesk's Suite Growth ($89/agent/mo) includes full SLA configuration and advanced reporting without requiring a separate enterprise tier, which reduces the per-seat cost for teams that need ITSM features outside of IT.
- JSM requires teams to build most ITSM processes from scratch, with reviewers noting that unlike competing platforms it provides limited out-of-the-box process templates. Multiple comparison articles cite the build-it-yourself nature of JSM as a time and resource sink for organizations without dedicated Jira administrators. Zendesk provides pre-built views, macros, and automation templates that reduce initial configuration before teams begin routing tickets.
- JSM's Automation execution caps (1,000 per user per month in Premium) constrain high-volume support operations and force teams to purchase Enterprise for unlimited automation. Zendesk's Suite tiers include Triggers and Automations without per-user execution caps, which removes the ceiling that forces organizations onto Enterprise pricing when automation volume increases.
Questions, answered
Jira Service Management to Zendesk migration questions
How long does a Jira Service Management to Zendesk migration take?
Migrations under 15,000 Requests, one service project, and no complex asset linkage requirements land between four and six weeks. Migrations with multiple service projects, project-scoped custom field schemas requiring a full field discovery pass, large asset datasets (over 5,000 asset objects with linkage reconstruction), or historical comment threads exceeding 200,000 entries move to eight to twelve weeks because of the field-by-field scoping, asset relationship pre-pass, and attachment chunking.
Do JSM Automation Rules, SLA policies, and Jira Assets migrate to Zendesk?
Automation Rules migrate as JSON documentation only, not as Zendesk Triggers or Automations. We deliver a written inventory of every active JSM automation with its trigger, conditions, and actions, and the customer's Zendesk admin rebuilds the routing logic using Zendesk's Trigger and Automation builder. SLA definitions migrate to Zendesk SLA Policies if the destination Suite tier supports them (Suite Team has limited SLA; Suite Growth and above includes full SLA goals). Jira Assets have no native Zendesk equivalent; we migrate asset data as Organization-level custom fields or a separate custom object, and reconstruct issue-to-asset linkage from JSM's relationship API before import.
Can we migrate JSM Knowledge Base articles from Confluence to Zendesk Guide?
Yes, we migrate JSM Knowledge Base articles from the linked Confluence space. We export articles via the Confluence REST API, transform the XHTML storage format to Zendesk Guide HTML, and import into Zendesk Guide sections. Confluence space permissions do not transfer; the customer re-applies article permissions in Zendesk Guide post-migration. If the source JSM has no linked Confluence space or the Knowledge Base lives in a separate Confluence instance, this step is skipped and documented as a Guide rebuild requirement. We do not rebuild Confluence macros, page templates, or nested page hierarchies inside the migration scope.
Do we preserve the full comment and audit history from JSM?
Yes. Public comments migrate as public Zendesk ticket comments. Internal notes from JSM migrate as internal Zendesk comments, preserving author, timestamp, and body text. The full JSM change history (field changes, status transitions, assignee updates) migrates as internal audit comments in a standardized format (field: old value > new value, timestamp, actor). Attachments embedded in comments are handled in a dedicated attachment pass after the parent ticket is created. Issue links (blocks, relates to, duplicate) are stored in a custom Zendesk field and referenced in a ticket comment for traceability.
What happens to our Jira-Zendesk integration during migration?
Zendesk's legacy Jira field syncing integration is deprecated as of April 27, 2026. Any active bidirectional Jira-Zendesk sync will stop functioning after the migration window unless reconfigured. We document all active Jira integration endpoints during the discovery pass and flag them for the customer's admin to rebuild using the current Zendesk-Jira integration or a third-party sync tool. If the migration is a full cutover (JSM decommissioned), the integration is replaced by Zendesk's native routing and the engineering handoff process moves to Zendesk's own workflow.
What user types and agent billing are preserved during migration?
JSM agents (licensed resolvers) migrate as Zendesk agents with the same role and Group membership. JSM customer portal users migrate as Zendesk end-users and do not count against the Zendesk agent seat billing. We set the user_type field explicitly on every imported user to prevent portal-only users from landing as billable agents. JSM users without email receive a generated placeholder email and are flagged in the reconciliation report for the customer's admin to link to a real Zendesk user account post-migration.
Does FlitStack AI also migrate JSM workflows and Confluence pages beyond the Knowledge Base?
No. JSM workflows and automation rules are Jira-specific constructs that do not translate to Zendesk Triggers and Automations. We document them as JSON but do not migrate them as code. Confluence pages that are not linked as Knowledge Base articles to a JSM service project are outside migration scope. We do not migrate Confluence spaces, page hierarchies, or Jira Software issues that are not linked to JSM service desk requests. Those remain in the Atlassian ecosystem if the customer retains Jira Software for development tracking.
Related migrations
Sources: official documentation
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
- Bulk importing user data with the data importer — Zendesk help
- How do I format the date field in Sell — Zendesk help
- About custom ticket fields — Zendesk help
- About lookup relationship fields — Zendesk help
Get a quote
Moving from Jira Service Management to Zendesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.
Get a quote