Jira Service Management cost vs GLPI and Zammad

Does self-hosting Jira Service Management alternatives cost less over several years?

A renewal notice, a Data Center end-of-sale date or a residency requirement is usually what forces a cost review, and the core product is not where the money goes. Self-hosted GLPI is distributed under GPL-3.0 and Zammad is licensed under AGPLv3, and neither carries a license fee for the software itself. The comparison therefore turns on infrastructure, migration, optional vendor support and the internal hours needed to run the platform. No Jira Service Management price is supplied here, so take the per-agent figure from your Atlassian quote or contract and build the comparison from that document, not from list prices or estimates.

Atlassian's Data Center dates set the timeline for that review. New Data Center subscriptions end for new customers on March 30, 2026, existing customers can buy licenses or expansions until March 30, 2028, and Data Center licenses expire and become read-only on March 28, 2029. Any cost model should run the recurring Atlassian spend up to those dates, then show the one-time migration and parallel-running costs against it. Ask your Atlassian account team which of these dates applies to your contract and whether your renewal term crosses them. Support is the optional line. Zammad sells self-hosted support named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to its pricing page, while GLPI Network self-hosted subscriptions run from 100 EUR per month to 4,500 EUR per month, according to the GLPI Network subscriptions page. Decide whether you need a vendor contract at all, and if so, compare the tier that matches your agent count and support hours.

Which cost components change when you move from Jira Service Management

This table compares each cost component of Jira Service Management with the matching component of a self-hosted GLPI or Zammad deployment. Read it row by row to see who is paid, whether the cost is one-time or recurring, and what you still pay for after leaving Atlassian. The main takeaway is that license fees drop out, but hosting, migration, upgrades and staff time move onto your own budget.

Cost component	Jira Service Management (Cloud or Data Center)	Self-hosted GLPI or Zammad	One-time or recurring
Subscription or license	Per-agent subscription for Cloud, or a Data Center license with its own renewal terms	No license fee for GLPI (GPL-3.0) or Zammad (AGPLv3); optional vendor support subscriptions	Recurring
Infrastructure	Atlassian-managed hosting on Cloud, or your own servers and database for Data Center	Your servers, storage, load balancer, database and cache, sized to agent count and asset volume	Recurring
Implementation and configuration	Queues, request types, workflows and SLAs configured in the Atlassian admin tools	Service catalog, ITIL modules or Zammad groups, SLAs and roles built by your team or a partner	One-time
Data migration	Export through Jira Cloud backup and CSV; Assets and automation rules need separate extraction	Zammad has no built-in Jira migrator, so import runs through its API; GLPI needs its own import scripts	One-time
Vendor support	Included in the Atlassian subscription	Optional Zammad support tiers (Business, Enterprise, Corporation) or GLPI Network subscriptions; confirm scope in each quote	Recurring, optional
Upgrades and patching	Handled by Atlassian on Cloud; your team runs Data Center upgrades	Your team applies GLPI and Zammad releases, including database updates and plugin reactivation for GLPI	Recurring
Backup and recovery	Cloud backup manager; excludes automation rules, third-party apps and Assets	Your backup tooling for database, files and GLPI config keys; test restores on a schedule	Recurring
Internal skills and staff time	Administrators for Atlassian configuration and app management	Staff for Linux, PHP or Ruby stack, database, web server and security hardening	Recurring

What moves the cost comparison most

Self-hosted GLPI and Zammad have no license fee for the core product, so the comparison turns on who you pay for hosting, support and in-house skills, and how those costs grow with your users, data and uptime needs. The cards below set out the drivers to model before you put a number next to a Jira Service Management renewal.

Agent and user count

GLPI Network prices its hosted service per user, at 19 euros per user per month for public cloud and 21 euros per user per month for private cloud, with a 25-user minimum on private cloud. That pricing shows how a per-user model scales, so a small team and a large one can end up with very different totals. Ask every vendor whether it counts agents, requesters or both, and model the count you expect in three years. Self-hosted GLPI and Zammad do not charge per seat, so this driver mainly affects support tiers and capacity planning.

Data volume and attachments

Ticket history, attachments and email content grow every year, and they drive storage, backup time and search performance. Zammad documents Elasticsearch as optional but strongly recommended for faster search, reporting and searching attachment content. Plan for an index that needs its own host resources, and confirm how long your retention policy keeps attachments online. Jira Cloud backups also require 48 hours between backups when attachments are included, so check that schedule against your recovery targets.

Availability and caching design

A single Zammad installation can use the file system cache, while multi-instance deployments such as containers or cluster nodes need Memcached. Adding instances adds components to patch, monitor and back up, and it adds failover planning that a single server does not need. Decide early whether you need more than one application node, because that choice changes both hosting cost and the skills your team must hold.

Support subscription tier

Zammad sells self-hosted support subscriptions named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year. These are optional, recurring costs on top of hosting and labor, and they replace some of the response you would otherwise build in-house. Compare each tier with the response and escalation terms you need, and ask the vendor what is included in writing. GLPI's self-hosted subscriptions run from 100 euros per month for the Basic tier up to 4,500 euros per month for Enterprise, so the tier you pick can outweigh the software itself.

In-house skills for operations

Self-hosting moves the work of running the platform to your team or to a partner. GLPI requires PHP 8.3 or later with MariaDB or MySQL, and its updates involve backing up the database and config keys before running a console update. Zammad runs on PostgreSQL and Redis, and on Kubernetes its support covers only the application. Rate each skill you lack, then price the training, hiring or partner hours needed to close those gaps.

How GLPI and Zammad support options change the recurring line

The GLPI core is distributed under GPL-3.0 and carries no licence fee. The recurring cost sits in the infrastructure beneath it and in the people who operate it. The GLPI README lists PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later on the main branch, while the installation docs list PHP 8.2 with MySQL 8.0 or MariaDB 10.6 for GLPI 11.0, so confirm the exact requirements for the version you plan to run.

Licence cost: The core has no licence fee under GPL-3.0, so the first line in a comparison is zero.
Servers and database: The web server, PHP runtime and MariaDB or MySQL instance run in your cloud account or data center and recur every month.
Upgrade procedure: The installation docs require a backup of the database, the files and the config directory, including glpi.key and glpicrypt.key, followed by php bin/console db:update. Since GLPI 11.0, plugins are suspended after a new version is detected and must be reactivated after major updates.
Staff time: Patching, backups and upgrade testing recur with each release. GLPI 12.0.0 was published on October 7, 2026.

Before budgeting, ask your platform team to estimate the hours for each upgrade cycle and the plugins you depend on, since those hours are the main variable in the free core.

How to build the five-year comparison with your own numbers

This sequence turns vendor quotes, your agent and asset counts and your hosting plan into one five-year model that compares one-time and recurring costs on the same basis.

Pull your current Jira Service Management quote
Ask your Atlassian account team or reseller for the written per-agent price for Jira Service Management Cloud or Data Center, including the tier, the agent count and any add-ons you run. Confirm the Data Center dates that apply to your contract: Atlassian ends sales of new Data Center subscriptions to new customers on March 30, 2026, sets March 30, 2028 as the last date for existing customers to buy licenses or expansions, and Data Center licenses expire and become read-only on March 28, 2029. Note which of these dates applies to your renewal. You are done when the quote, its term and the applicable dates sit in one document owned by finance or procurement.
Count named agents, requesters and assets
Export the current agent list, the number of customer or employee requesters who need access, and the configuration items you want to keep in a CMDB. Jira Cloud's backup excludes Assets, so the Assets count must come from a separate export. Separate agents who work tickets daily from occasional approvers, because the self-hosted options price and license them differently. You are done when you have one agent count, one requester count and one asset count with the date each was taken.
Size hosting for GLPI or Zammad
For GLPI, confirm the platform requirements in the installation docs: PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 for GLPI 11.0, and PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later on the current main branch. For Zammad, plan for PostgreSQL 15 or newer and Redis 7 or newer, plus Nginx or Apache as a reverse proxy. Decide whether you need Elasticsearch, which Zammad describes as optional but strongly recommended, and Memcached if you run several instances. Ask your platform team or hosting provider for the server, storage, backup and monitoring cost in your own cloud account or data center. You are done when each option has a documented server layout and a monthly infrastructure line in your model.
Request written implementation and migration scopes
Ask each candidate vendor or implementation partner for a written scope that lists installation, configuration, data migration, integrations such as identity sign-in, testing, training and handover. For Zammad, ask whether the quote covers the API-based import from Jira, since Zammad has no built-in Jira migrator. For GLPI, ask how Assets and automation rules are extracted and rebuilt. Ask whether a support subscription is part of the quote and which tier it is. Zammad's published self-hosted support tiers are Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, and GLPI Network's self-hosted subscriptions start at 100 euros per month for Basic. Treat both as list prices from their own pages and confirm them in writing. You are done when each option has a fixed-scope quote with its assumptions listed.
Add internal hours for upgrades and operations
Estimate the hours your team spends each year on patching, upgrades, backups, monitoring and user administration. For GLPI, include the update procedure: back up the database, the files and the config directory with glpi.key and glpicrypt.key, replace the application files, and run php bin/console db:update. Since GLPI 11.0, plugins are suspended after a new version is detected and must be reactivated after major updates, so add time for plugin review. GLPI 12.0.0 was published on October 7, 2026, so schedule the upgrade test cycle against it. For Zammad, add time for the release cadence in its releases page, which published 7.2 on September 23, 2026 and security releases on both the 6.5 and 7.x lines. Use your own hourly rates and label them as internal estimates. You are done when every recurring internal task has an hours figure and an owner.
Compare one-time and recurring totals side by side
Put the Jira Service Management subscription, the GLPI or Zammad implementation, migration, hosting, support subscriptions and internal hours into the same spreadsheet. Use the same five calendar years for every option, and split each line into one-time costs such as migration and integration work, and recurring costs such as licenses, hosting, support and staff time. Mark the cost drivers that move the totals most, such as agent count, asset count and hosting region. Add a separate line for a parallel run period if you plan one. You are done when each option has a five-year total with one-time and recurring subtotals that a reviewer can trace back to a source line.
Keep the model current and re-run it on each quote
Store the spreadsheet with its source documents, the date of each quote and the owner of each assumption. Re-run the model whenever a vendor sends a revised quote, your agent or asset counts change, a Data Center date moves in your contract, or a new GLPI or Zammad release changes the upgrade effort. Record what changed in a short log so the decision remains explainable at renewal. You are done when the model is shared with procurement and the platform team and the next review date is set.

Costs teams forget on each side

Licence lines are only part of the comparison. The costs that surprise teams sit in backup gaps, rebuild work, plugin upkeep, migration constraints and the platform skills needed to run a self-hosted tool. Each card names one of these items and the check to make before comparing totals.

Jira Cloud backups leave gaps

Jira Cloud's backup manager covers work items, comments, users, groups and project configuration, but it excludes automation rules, third-party apps and Assets. Anything outside the backup has to be extracted or rebuilt by hand, and that effort belongs in the Jira side of the cost model. Ask which automation rules, app data and Assets objects your team depends on, and estimate the rebuild time before you treat the export as a complete copy.

Backup scheduling with attachments

When attachments are included in a Jira Cloud backup, Atlassian requires 48 hours between backups. For a service desk that needs a recent copy before a cutover, this limits how often you can take a full export during the parallel run. Plan the cutover window and the final delta export around that interval, and confirm the current limits in your own tenant.

GLPI plugin reactivation after upgrades

Since GLPI 11.0, plugins are suspended when a new version is detected and must be reactivated after major updates. Each plugin your team uses for workflows, reporting or integrations needs a compatibility check and a test run before the upgrade window. Budget internal or partner time for this review on every major release, because a suspended plugin can stop a process your agents rely on.

All-or-nothing Zammad migrations

Zammad's built-in migrators are all or nothing, work only on a new instance and accept one source system per migration. If a migration fails or the data needs correction, the team typically reruns it on a fresh instance rather than patching the existing one. Plan for test loads, clean source data and a rehearsal cycle, because each attempt consumes staff time and environment capacity.

API token and rate limit work

Migrating from Zendesk to Zammad requires an API token created by a full administrator, passwords are not migrated, and differential migrations are not supported. Rate limits depend on the Zendesk plan, so large histories can take longer than expected. Confirm who holds administrator rights for the token, how long the import will run on your plan and who validates users after the import.

Platform team time for Zammad on Kubernetes

Zammad documents Docker Compose and a Kubernetes Helm chart, but on Kubernetes its support covers only the Zammad application, not Kubernetes-specific issues. Running the cluster, storage, ingress and upgrades becomes an internal responsibility or a separate contract. Ask who will own the cluster, whether you need Memcached and Elasticsearch for your deployment size, and how much platform engineering time that adds each year.

What to ask for in a quote so the numbers are comparable

Every quote, whether from a vendor, a partner or DeployOpen, should state the written scope before it states a total. Ask for the applications in scope (GLPI or Zammad, plus any Elasticsearch, Redis, Memcached or reverse proxy components), the number of agents and end users, the migration method and what is excluded from it. Migration exclusions matter most: Zammad's built-in migrators cover Freshdesk, Kayako, OTRS and Zendesk but not Jira Service Management, so a Jira migration usually means an API-based build, and its estimate should say which of automation rules, Assets, apps, SLAs and queues are rebuilt and which are left to your team. DeployOpen works to a written fixed scope agreed before work starts and does not publish a price list, so a quote follows from that scope. Ask any vendor to do the same.

On the self-hosted side, ask who carries each recurring duty. Hosting assumptions should name the cloud account or data center, the database platform (PostgreSQL 15 or newer for Zammad, MariaDB or MySQL for GLPI), backup frequency, and the upgrade path, including how GLPI plugins are handled after an update, since they are suspended until reactivated. Backup and upgrade responsibilities should be written down as either your staff's or the provider's, with a retainer or support tier named for each. Vendor support subscriptions are optional line items: Zammad lists Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, and GLPI Network lists self-hosted tiers from 100 EUR per month. Compare these separately from the core software, which costs nothing to license under either project's open-source terms.

The Jira Service Management figure should come from your own Atlassian order, not from a list price or a peer's invoice. Pull the current agent count, the edition (Cloud or Data Center), the term and any discounts from your order form, and confirm with Atlassian which dates apply to your Data Center renewal, since new Data Center sales end on March 30, 2026 and licenses become read-only on March 28, 2029. Then model the same number of years for each option, with one-time costs (migration, integration, cutover) and recurring costs (hosting, support, staff time, upgrades) in separate columns. A comparison that puts a full multi-year total against a single year of hosting is not comparable, and neither is one that leaves out internal time.

Questions buyers ask about cost, effort and time

Is GLPI or Zammad free to run on our own servers?

Yes, the core software carries no license fee. GLPI is distributed under the GPL-3.0 license and Zammad under the AGPLv3, so you can install, run and modify them without paying the authors. The costs move elsewhere: servers or virtual machines, a database, backups, monitoring, email and storage, plus the internal staff who install, patch, upgrade and support the platform. Those components recur every year, and they are usually larger than the software line item you are replacing. Before you commit, list each component, name who pays for it, and confirm the hosting and staffing model with your finance and security teams.

How much does a Zammad or GLPI support subscription cost?

Support is optional, and the published figures differ by vendor. Zammad sells self-hosted support subscriptions named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to the Zammad pricing page. GLPI Network sells self-hosted subscriptions from 100 EUR per month for the Basic tier, which covers up to 10 agents and 500 assets, to 4,500 EUR per month for Enterprise, which includes level 3 support and marketplace plugins, according to the GLPI Network subscriptions page. GLPI Network's hosted option is priced at 19 EUR per user per month for public cloud and 21 EUR per user per month for private cloud with a 25-user minimum. Compare these with the tier that matches your agent count and support hours, and check whether the price is per year or per month.

How long does a move from Jira Service Management take?

The duration depends on scope, and no timeline figure is supplied for this comparison. The main drivers are the number of request types, workflows, queues, SLAs and automation rules you must rebuild, the volume of tickets and attachments to migrate, how many integrations sit behind the service desk, and how many business units must test and sign off. A move that covers only one support team with few integrations takes far less work than a move that includes Assets, change management and single sign-on. Ask any implementation partner for a written scope with deliverables and dates before work starts, and treat any duration without that scope as unverified.

Can our own team run GLPI or Zammad without outside help?

Yes, if your team already has the skills the platform needs. Zammad requires PostgreSQL 15 or newer, Redis 7 or newer, and Nginx or Apache as a reverse proxy, and it uses Elasticsearch as an optional search engine. GLPI runs on PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later, according to its README, while its installation docs list PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 for GLPI 11.0. Operators need Linux administration, database backup and restore, web server configuration and patch discipline. If those skills are missing, or nobody has time to cover on-call hours, a fixed-scope implementation partner can plan, build and document the platform while your team learns to operate it.

What does our side need to provide during the migration?

Your organization carries the decisions and the access, so name these owners before the work starts. Assign a product owner who can approve the process design, a technical owner for the servers and identity integration, and a service owner for each queue or team. Provide read access to the current Jira Service Management instance, Assets and any automation or app configuration, and a test window in which agents can check migrated tickets without disrupting live work. The final sign-off should be written and cover data completeness, SLA behavior, notifications and reporting. Expect to put this time in on your calendar, because a migration stalls when these owners are unavailable.

Is a Jira export enough to move our service desk?

No. A Jira export carries the core work items, but it does not carry everything the service desk depends on. Atlassian's Jira Cloud backup manager covers work items, comments, users and groups, and project configuration, yet it excludes automation rules, third-party apps and Assets. Those gaps are where routing, approvals, SLA logic and the configuration management database often live, so they need their own extraction, mapping and rebuild. Attachments also require a separate decision because, with them included, Atlassian requires 48 hours between backups. Inventory your automation rules, apps and Assets schema before choosing a target platform, and confirm what each export format covers in your own tenant.

How DeployOpen scopes a fixed-price implementation and what it hands over

DeployOpen plans and implements self-hosted open-source service desks inside your own cloud accounts, data centers or air-gapped networks. For a Jira Service Management cost comparison, the work starts with a written scope that sets the components, hosting, migration and support terms, so the cost model you review matches what gets built.

How we scope

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
The written scope names which Jira Service Management features move to GLPI or Zammad and which are retired.
We list the hosting, database, cache and search components your team will run, so each cost line is visible.
Ongoing support, upgrades and continuous testing are available as retainers, priced separately from the build.

How we build

We deploy GLPI or Zammad on your infrastructure using your chosen database, reverse proxy and backup tooling.
Authentication is wired to your directory or identity provider so agent accounts follow your existing controls.
Migration runs from a Jira Service Management export into a new instance, with a test cycle before cutover.
Security testing of the deployed application and its APIs can be included in the written scope if you request it.

How we hand over

You receive installation, configuration and update documentation that your own team can follow after handover.
Backup and restore procedures cover the database, files and configuration keys, with restore tests recorded.
Migration reports list what was moved, what was rebuilt by hand, and what was excluded, including automation and apps.
Evidence for compliance assessments is prepared, while independent auditors and certification bodies issue any reports.

How we support

Support after handover is available as a retainer covering upgrades, patching and incident response for your instance.
Upgrade work follows the vendor's documented update steps, with a backup taken before each change.
Ask for the retainer scope in writing, including response expectations, before you choose between support tiers.
Vendor support subscriptions from GLPI Network or Zammad are separate contracts that you buy directly from those vendors.

Jira Service Management cost vs self-hosted GLPI and Zammad