Atlassian ends Jira Service Management (JSM) Data Center.Switch to Zendesk.

JSM migration

Data Center goes read-only on March 28, 2029. L5 moves your service desks to Zendesk one team at a time, and connects them to engineering in Jira Cloud.

Plan your migration
Zendesk Preferred Partner

JSM Data Center goes read-only in 859 days

  1. New sales end
  2. Expansions end
  3. Read-only

Migrate to Zendesk before then.

The clock started in September 2025.

The countdown

Atlassian announced the end of Data Center on September 8, 2025. It is winding Data Center down in phases, for Jira Service Management, Jira Software and Confluence. Dates from Atlassian's end-of-life notice.

29 months until JSM Data Center goes read-only

  1. New sales ended
  2. Expansions end, in 17 months
  3. Read-only, no support
  • Employee · IT VPN drops after the update
  • Employee · HR How do I change my benefits?
  • Customer Where is my order?
  • AI agent Answered from your knowledge
  • Agent Handed off with the conversation
All of it runs in Zendesk's cloud

Service management that runs in Zendesk.

Moving to Zendesk

Zendesk was named a Leader in the 2026 Gartner® Magic Quadrant™ for CRM Customer Engagement Center, for the second consecutive year. Employees and customers get help in the same place, and Zendesk runs the servers.

  1. Nothing to host or patch

    Today your team runs the Data Center servers and their upgrades. Zendesk runs and updates the platform for you.

  2. SLAs, routing and approvals built in

    SLA policies, routing, approval steps and reporting are standard Zendesk features, so the desk runs without custom scripts.

  3. AI agents answer first

    The AI agent answers from your help center articles. When it cannot answer, an agent gets the ticket with the conversation.

  4. Employees and customers, one platform

    IT, HR and customer support run on the same Zendesk, each with its own help center.

Gartner, Magic Quadrant for the CRM Customer Engagement Center, by Pri Rathnayake, Drew Kraus, Francesco Vicchi, Jim Robinson, Devra Struzenberg, November 5. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally. MAGIC QUADRANT is a registered trademark of Gartner, Inc. and/or its affiliates and is used herein with permission. All rights reserved. Source: Zendesk press release.

Where each part of JSM goes.

What moves

Years of JSM leave behind request types, custom fields and portal apps that few people still use. L5 keeps what your team uses and rebuilds it the standard Zendesk way.

You walk away with

  • Ticket forms and roles mapped from Jira
  • A help center built from Confluence
  • Asset records linked to tickets
From JSM Data Center to Zendesk
In Jira Data CenterIn Zendesk
Request types and queuesTicket forms, groups and views
Confluence spacesHelp center articles
Jira AssetsCustom objects linked to tickets
Customer portalHelp center
Jira Software projectsWork in Jira Cloud, synced both ways

From first workshop to switch-off.

The package

Every JSM move follows the same five steps, under one SOW. L5 comes to each workshop with a proposed design for your team to approve, and each release ends with a team working in Zendesk.

Each release ends with

  • A team live in production
  • Migrated tickets checked against Jira
  • Agents and admins trained
The migration package
  1. Plan

    We go through your request types, workflows, Assets data, integrations and ticket history, and set the release dates.

  2. Foundation

    We set up Zendesk and the help center, then load sample tickets for your team to check.

  3. Pilot

    One team starts working in Zendesk. Escalations go to engineering in Jira Cloud and come back.

  4. Cutover

    The other teams move over, with ticket history from the cutoff date you pick.

  5. Retire

    You switch off Data Center and Confluence. Closed tickets from before the cutoff stay in a read-only archive.

Engineering works in Jira Cloud.

Where teams land

Your IT and customer support desks move to Zendesk. Engineering works in Jira Cloud, and escalations sync both ways. Jira Software Data Center ends on the same day as JSM, so teams still on it move to Jira Cloud too.

  • IT and customer support

    Zendesk

    Service desks with SLAs, asset records, a help center and AI agents answering first.

    Moves here: request types, portal, knowledge, Assets.

  • Engineering

    Jira Cloud

    Projects, boards and workflows live in Jira Cloud. Teams on Jira Software Data Center move there with Atlassian's cloud migration tools.

    Works in: engineering projects and boards.

  • Escalations reach engineering

    Two-way sync

    An agent escalates from Zendesk, a Jira issue opens, and its updates flow back to the ticket.

    Connects: Zendesk tickets and Jira issues.

Zendesk's own team brings us in.

Our CEO co-founded INRY, a Top 10 ServiceNow partner, and is an author on ITIL v3. L5 is a Zendesk Preferred Partner, and our forward deployed team can keep working inside your Zendesk after cutover, on the schedule you choose.

  • 600+ Customers in 2 years
  • Preferred Zendesk partner
  • Top 10 ServiceNow partner our CEO co-founded
  • SOC 2 And ISO 27001 certified

Customers aren't just buying Zendesk. They're buying L5. The pre-built workflows, the AI agents, the operational know-how. That's what gets them live and keeps them running.

Tony Pearson AI Specialist, Zendesk

What JSM teams ask before moving.

Common Questions

Plan your move before March 2028.

Atlassian stops Data Center expansions on March 30, 2028, a year before read-only. We start with workshops on your request types, workflows, Assets data and integrations, and you leave with a release plan and dates.

Plan your migration