Can open-source alternatives to ServiceNow replace your ITSM platform?
For many ITSM workloads, the answer is yes, with conditions. GLPI covers ITIL incident, problem, change and service level management, plus asset inventory, configuration management, knowledge base and contract management. Zammad fits agent ticketing for teams that mainly need a shared request queue. Organizations with several teams often run both: GLPI as the record for assets and configuration items, and Zammad as the front-line queue, joined by an integration you design and test yourself. Whether one tool is enough depends on how much custom workflow and orchestration you have built on ServiceNow, so inventory those flows before you decide.
Teams usually start looking when a renewal, a licensing change, a data residency rule or lock-in makes the current platform harder to justify. ServiceNow's own self-hosted route, Private Stack, is worth understanding before you assume it removes the operating load. In Private Stack, the customer or a partner owns and operates the load balancer, application server and database tiers, while ServiceNow supplies the application software, upgrade packages, deployment guidance and support. Customers start through their account team and should expect to buy a workshop on architecture, hardware sizing, database selection and operational readiness. Residency control is a genuine gain, but so is the operating burden you take on.
Before comparing costs, separate what you pay for from what you operate. Open-source licenses carry no acquisition fee, so recurring spend moves to infrastructure, internal staff, backup, upgrades and any implementation or support partner. Ask every bidder for a written scope covering the modules in use, integrations, data migration, hardening and handover, and ask ServiceNow for the equivalent breakdown of Private Stack. Confirm with Teclib', the company that maintains GLPI, which hosting and support options it offers, and check whether GLPI 12.0.0, published October 7, 2026, is the version you will validate against. Zammad offers self-hosted support contracts named Business, Enterprise and Corporation, so decide early whether you need one.
Which open-source option fits which part of ServiceNow ITSM?
ServiceNow ITSM bundles ticketing, service management, asset tracking and a configuration database on one platform. Open-source replacements split these jobs across tools, so the question is which component covers which workflow. The cards below map each part to GLPI or Zammad and name the trade-off you accept with each choice.
GLPI for ITIL service management
GLPI is free asset and IT management software under GPL-3.0. It covers ITIL incident, problem, change and service level management, so the processes you run in ServiceNow ITSM have a direct counterpart. The trade-off is that its workflows are configured rather than built as a general application platform, so map your approval chains and SLA rules before you commit. Confirm each process against the current GLPI documentation in your own test instance.
GLPI asset inventory and CMDB
GLPI keeps an asset inventory and configuration management records, which is the foundation most teams use for the configuration database they run in ServiceNow. The trade-off is that the relationships and data quality of your CMDB depend on discovery and import work you own. Plan the data sources (directory, endpoint agents, spreadsheets) and decide which configuration items must be accurate before go-live.
GLPI knowledge base and contracts
GLPI includes a knowledge base and contract management, letting agents answer repeat requests and track software and service contracts next to the assets they cover. The trade-off is that articles, contract terms and renewal dates are migrated and maintained by your team. Assign owners for both before users start relying on them.
Zammad for agent ticketing
Zammad is licensed under AGPLv3 and focuses on agent ticketing for help desks and support teams. Its source code is owned by the Zammad Foundation, which is independent of Zammad GmbH, the company that develops it with the community and sells hosted plans and support contracts. The trade-off is that Zammad is strongest at conversations and tickets, so pair it with GLPI when you need ITIL change and asset records.
Hosting and support choices
Both products can run in your own infrastructure, and Zammad GmbH sells support contracts for self-hosted installations named Business, Enterprise and Corporation. GLPI Network is the hosted option from Teclib', which edits GLPI. The trade-off is that self-hosting moves patching, backup, upgrades and on-call duties to your team, while a support contract or hosted plan moves some of that cost to a vendor. Ask each vendor what support covers and who handles security fixes.
Where neither tool replaces ServiceNow
Neither GLPI nor Zammad is a full ServiceNow workflow platform. Custom application development, low-code workflows across many departments, and the broad module catalogue are outside what these tools were built to do. The trade-off is that a leaner stack reduces licence cost and lock-in, but you may need custom integration or separate tools for the workflows you cannot map. Inventory those workflows first.
How ServiceNow ITSM capabilities map to GLPI and Zammad
This table compares the main ServiceNow ITSM capabilities with what GLPI and Zammad cover, since this page evaluates them together. GLPI carries most of the ITIL process, asset and configuration scope, while Zammad handles agent-facing ticket work. The last column lists what to test in a proof of concept before assuming parity.
| Capability | GLPI coverage | Zammad coverage | Confirm in a proof of concept |
|---|---|---|---|
| Incident and problem | Incident and problem records under ITIL process scope, linked to assets and configuration items. | Ticket queues, SLAs, macros and agent collaboration for incident handling. No native problem record is assumed. | Whether problem records link to incidents and changes the way your process requires. |
| Change management | Change records under ITIL change scope. Confirm the approval steps against your change board model. | No dedicated change module is assumed. Changes are typically modeled as tickets with triggers and approvals. | Approval routing, change calendars and change advisory board reporting. |
| Service catalog | Request forms and templates. Confirm whether catalog items, variables and approvals meet your needs. | Ticket templates and forms for requesters. Multi-step catalog approvals are not a core feature. | Catalog items with approvals, fulfillment tasks and a requester self-service portal. |
| Asset management | Asset inventory, lifecycle and contract management. Confirm inventory methods for your estate. | Not an asset inventory. Assets can be referenced from tickets only where integrated. | Discovery coverage for endpoints, network devices and cloud resources. |
| CMDB | Configuration management that links items, relations and assets. Review model depth against your CMDB design. | No CMDB is assumed. Configuration data would come from GLPI or another source. | Relationship model, reconciliation rules and data quality against your service map. |
| Knowledge | Knowledge base for articles linked to tickets and FAQs. | Knowledge base feature is available. Confirm version, article workflow and access controls. | Article approval, review cycles and search quality at your content volume. |
| SLA management | Service level management with definitions and calendars. Verify against your own targets. | SLA rules and escalation through ticket triggers. Confirm business hours and escalation paths. | Breach reporting, calendar exceptions and escalation to on-call tools. |
| Reporting | Built-in statistics and dashboards. Confirm whether custom reports meet your needs. | Reporting and dashboards for agents and managers. Confirm export options and report depth. | Executive dashboards, ITSM key metrics and retention of historical data. |
| Integrations and workflow automation | REST API, mail collection and a rules engine. Connectors to monitoring and directory tools may need building. | REST API, triggers, schedulers and webhooks. Confirm connectors for your identity and monitoring tools. | Identity sync, monitoring alerts and end-to-end automation with your change pipeline. |
How running GLPI and Zammad yourself compares with ServiceNow Private Stack
Under ServiceNow Private Stack, the customer or a partner owns and operates the load balancer, application server and database tiers, while ServiceNow supplies the application software, upgrade packages, deployment guidance and support. That split is the right starting point for comparing it with self-hosting GLPI and Zammad, because the same infrastructure responsibilities exist in both models. The difference is who authored the application and who you depend on for it. With ServiceNow, the vendor owns the application roadmap and upgrade packages, and you own the platform beneath it. With GLPI and Zammad, you also take on the upgrade planning, the patch decisions and the support contract choice that the vendor would otherwise make for you.
Private Stack deployments start through a ServiceNow account team, and customers should expect a workshop covering architecture planning, hardware sizing, database selection and operational readiness. Ask whether that workshop is a paid engagement, what it produces in writing, and whether its output is reusable if you later move to another platform. For a self-hosted GLPI or Zammad deployment, the same questions map to decisions your own team or implementation partner must document: the application and database tiers, the sizing for your ticket and asset volumes, backup and restore procedures, and the upgrade calendar. Zammad GmbH offers Business, Enterprise and Corporation support contracts for self-hosted installations, and GLPI's editor Teclib' offers a hosted option, so you can choose between paid support for the application and running everything yourself.
Cost follows responsibility. Private Stack costs are paid to ServiceNow for the platform and its services, plus your own infrastructure and staff. Self-hosting GLPI or Zammad removes the vendor's platform licence fee, but the one-time work (planning, installation, data migration, integration with identity and monitoring) and the recurring work (patching, backups, capacity, on-call coverage) move to your budget. Ask any provider, including DeployOpen, for a quote that separates these items, states what is one-time and what recurs, and names who holds the on-call duty. Confirm the support level you need for the application and the database before you commit, since that gap is where self-hosted programs most often stall.
What a multi-year ServiceNow exit and self-hosted run really costs
This table breaks the total cost of leaving ServiceNow and running GLPI and Zammad yourself into its components, showing who is paid, what recurs and what drives each cost. Use it to build a like-for-like comparison and to write the questions you put to each vendor and integrator before you commit.
| Cost component | Who is paid, one-time or recurring | What drives it, and what to request in the quote |
|---|---|---|
| ServiceNow subscription or Private Stack fees | ServiceNow. Recurring. Private Stack deployments start through the account team and include a paid workshop on architecture, sizing, database selection and readiness. | Module count, user volume and deployment model. Request the full recurring schedule, renewal uplift terms, the workshop fee and what is excluded from the subscription. |
| Infrastructure (load balancer, application, database tiers) | Your cloud provider or data center vendor. Recurring for compute and storage, one-time for initial sizing and build. | Sizing for production, staging and disaster recovery copies, plus backup storage. Ask the integrator to state the assumed node counts and retention. |
| GLPI licensing | No license fee, GPL-3.0. Hosting and staff time are the real costs. | Free software. Optional paid services from Teclib' (GLPI Network, support) should be quoted separately and marked recurring if chosen. |
| Zammad licensing and support | Zammad GmbH for optional support contracts. Recurring when chosen. The software is AGPLv3 with no license fee. | Support tiers named Business, Enterprise and Corporation, and hosted plans run in German data centers are separate options. Compare each tier's response scope, hours and included services. |
| Implementation and configuration | Integrator or internal team. One-time, with ongoing change work after go-live. | Scope of ITIL workflows, approvals, SLAs and portals. Request a fixed-scope written plan with deliverables and acceptance criteria. |
| Data migration and history | Integrator for extraction, mapping and validation. One-time. | Source export format and volume. Zammad's built-in migrators are all or nothing and run on a new instance, so ask how rollback and reconciliation are priced. |
| Integrations (identity, monitoring, HR, email) | Integrator and internal owners. One-time to build, recurring to maintain. | Number of connected systems and API changes. Ask who owns each connector after handover. |
| Support retainers, upgrades and security testing | DeployOpen or another provider. Recurring when contracted. | Upgrade frequency, hardening scope, and testing cadence. Ask for named response expectations in writing rather than assumed availability. |
| Internal skills and staffing | Your payroll or contractors. Recurring. | Database, platform and ITSM administration skills. Ask which roles are needed in steady state and what training is included. |
What you give up when you leave ServiceNow ITSM
Moving from ServiceNow ITSM to GLPI and Zammad trades a vendor-built platform for components you assemble and run yourself. The cards below cover the capabilities most likely to shrink or shift during that move, with the workaround teams usually choose and what to validate before cutover.
Workflow and low-code depth
ServiceNow's workflow designer and scripting let teams model approvals, routing and task chains without code outside the platform. GLPI covers ITIL workflows through its own rules and forms, and Zammad uses triggers, schedules and macros for ticket automation. Expect some multi-step processes to be rebuilt as simpler rules or as scripts you maintain. Validate each critical workflow end to end with real ticket volumes before retiring the old one.
Native integrations and app ecosystem
ServiceNow's store offers prebuilt connectors for HR, security, development and finance tools. Self-hosted alternatives rely on their own APIs, plugins and webhooks, so each integration you depend on becomes a custom build or a community plugin you must review. Inventory every inbound and outbound integration, confirm the target system has a documented API, and budget for maintenance of each connector after go-live.
Vendor-run upgrades and patching
Under ServiceNow, the vendor ships application upgrades and most operational changes. With self-hosting, your team or your implementation partner schedules upgrades, tests customizations against each new release, and applies security fixes to the database, web and application tiers. Agree on an upgrade cadence, a rollback plan and who owns patch testing before you cut over.
CMDB discovery depth
ServiceNow pairs its CMDB with discovery and service mapping that continuously reconcile configuration items. GLPI provides asset inventory, configuration management and a CMDB-style model, but its discovery coverage depends on the agents and connectors you deploy and how often they run. Test discovery against a sample of your estate, measure the accuracy of relationships, and confirm which device classes you must track manually.
Reporting and dashboards
Operational and executive dashboards in ServiceNow draw on the same data model as the workflows, so reports stay consistent with the process. In GLPI and Zammad, reporting depends on built-in statistics, saved searches or an external BI layer connected to the database. Define the exact KPIs leadership uses, such as mean time to resolve or change success rate, and verify each one matches the figures from the old platform during a parallel run.
SLA, approval and change control
Entitlements, SLA timers and multi-level change approvals are central to ServiceNow ITSM for regulated teams. GLPI includes service level management and change workflows aligned with ITIL, while Zammad handles SLA policies for ticket response and escalation. Confirm how breach warnings, approval delegation and emergency change paths behave in your environment, and keep an audit trail for each approval decision.
Staff familiarity and training
Agents, administrators and approvers already know ServiceNow navigation, forms and terminology. Moving to new interfaces means retraining, rewriting runbooks and a period of lower productivity while people adjust. Plan role-based training, keep old and new procedures side by side during a parallel run, and measure ticket handling times during the first weeks after cutover.
Migrating off ServiceNow ITSM step by step
This sequence moves ServiceNow ITSM records, workflows and integrations into GLPI and Zammad in controlled stages, so each team proves the new process before the old platform is switched off. The output is a documented cutover with verified data, a tested rollback path and a retired ServiceNow instance.
Inventory processes, forms, workflows and integrations
Your ITSM lead and process owners list every active ServiceNow process (incident, problem, change, request, asset and CMDB), the forms and fields each one uses, the workflows and business rules that drive them, and every integration that sends or receives data, such as monitoring, identity, HR feeds and email. Mark each item as keep, rebuild or retire. The check is a signed inventory where every integration has a named owner and a decision, so nothing is found for the first time during cutover.
Export ServiceNow data and confirm completeness
The ServiceNow administrator and your platform engineers export the tables in scope, including incidents, problems, changes, configuration items, users, groups, knowledge articles and attachments, in a format both your team and the target tools can read. Confirm the export method and any row or attachment limits with your ServiceNow administrator or partner before you start, since these depend on your instance and configuration. Record row counts per table and store the exports in a controlled location. The check is a reconciliation sheet where counts match the source for every table.
Map fields to GLPI assets and Zammad tickets
Architects and data owners map each ServiceNow table to its target: configuration items and hardware to GLPI asset and CMDB types, incidents, problems and changes to GLPI ITIL objects, and customer-facing or simple request queues to Zammad tickets. Document value translations for states, priorities, categories and assignment groups, and decide how relationships between records are kept. Zammad's built-in migrators cover Freshdesk, Kayako, OTRS and Zendesk, not ServiceNow, so ServiceNow data needs a custom import script or an integration built by your engineers or implementation partner. Confirm GLPI import and migration options for your target version before committing to a route. The output is a signed mapping specification.
Build and test the custom import
Engineers write the import scripts from the mapping specification and load the data into a non-production GLPI and Zammad environment. They run the import repeatedly from a clean state, log every rejected record and fix mapping errors until a full run is clean. Spot-check a sample of records per table against the source, including attachments, comments and linked assets. The check is a passing test run with a documented error log and sign-off from the data owners.
Pilot with a single team
Select one team with a contained workload, such as a single service desk queue or one IT support group, and run it on GLPI or Zammad in production while the rest of the organization stays on ServiceNow. Agents, approvers and requesters use the new forms, notifications and approval paths, and the team logs every gap they find. Set up the integrations for this team first. The check is a pilot report listing defects, workarounds and usability issues, with each item closed or accepted by the process owner.
Run ServiceNow and the new platform in parallel
For a defined period agreed by the steering group, both platforms stay live. New work goes to the new platform for migrated teams, while ServiceNow remains the system of record for everyone else. Reconcile record counts and open items between the two systems each week, and confirm that integrations deliver to the right platform. The output is a reconciliation log showing no unexplained differences and an agreed list of blockers for cutover.
Cut over all teams and retire ServiceNow
Freeze changes in ServiceNow, run a final delta import of records created since the last extraction, switch integrations and email routing to the new platform, and announce the new service desk to all users. Keep ServiceNow in read-only mode for a retention period set by your legal and records team. After that, archive the final exports, retire the instance and cancel the subscription in line with your contract terms. The check is a signed cutover record, verified integrations and a documented decommissioning certificate from the data owner.
What moves cleanly and what must be rebuilt in ServiceNow exits
Historical tickets are the easiest part of a ServiceNow exit to carry over, and everything that makes those tickets behave a certain way is the hardest. Ticket records, comments, attachments, users and groups can usually be exported and loaded into a new platform. Workflows, approval chains, business rules, SLA definitions, assignment logic, catalog items and the integrations that push events into and pull data out of ServiceNow are configuration, not data. In GLPI and Zammad they have to be designed again on the new platform, and each one should be listed with an owner before any import starts. Ask the team that maintains the instance to inventory active flows, scheduled jobs and integrations, since many of them are undocumented.
Treat any importer as a test of your data model rather than a finished migration. Zammad's built-in migrator, for example, is all or nothing, works only on a new instance and accepts one source system per migration, so a run that fails partway cannot be patched in place and a second source cannot be merged in afterwards. The Zendesk path shows the other checks you need. It requires an API token created by a full administrator, does not migrate user passwords, and does not support differential runs, so every cutover needs a full re-run and users need a password reset plan. Rate limits depend on the source plan, which affects how long a large import takes. Confirm each of these with the source vendor and the importer documentation before you commit to a date.
Before cutover, run a reconciliation on a copy of the data. Compare ticket counts by status, state and year, sample attachments and linked assets, and check that assignment groups and priorities map to the new platform's equivalents. Plan for the period when old and new systems both receive requests, and decide which one is authoritative for each queue. Your quote should include the rebuild of workflows and integrations as a separate line from the data load, because that rebuild is where most of the effort sits and where scope tends to grow.
Which option fits your situation: residency, cost, customization or regulation
When the main driver is where data is stored and who can administer it, self-hosting is the direct answer. GLPI and Zammad both run on infrastructure you choose, so the database, attachments and logs stay in your own cloud account, data center or air-gapped network. ServiceNow Private Stack also keeps the platform on your infrastructure, but the load balancer, application server and database tiers are owned and operated by you or a partner, so the operating burden remains yours. The likely fit is GLPI for assets and ITIL records, with Zammad for requester tickets, if both must stay in the same jurisdiction.
- Hosting location: Confirm whether the requirement is a country, a region or a specific facility, and whether backups and log shipping must follow the same rule.
- Vendor access: Ask who can reach the database and application tiers for upgrades or support, and whether remote access is allowed.
- Zammad hosting: Zammad GmbH sells hosted plans in German data centers, which fits only if that location satisfies your rule. Otherwise self-host.
- Attachments and exports: Check where ticket attachments and CMDB extracts are written, since they often sit outside the main database.
- Staff skills: Confirm you can run the database, patching and backups in-house or through a partner.
Check these answers against your data classification policy before choosing between self-hosting and ServiceNow Private Stack.
Cost-driven decisions compare the license line with the total cost of running the platform. GLPI is free software under GPL-3.0, and Zammad is licensed under AGPLv3, so the software itself has no license fee. The recurring costs move to infrastructure, staff time for upgrades and backups, and optional support contracts. ServiceNow Private Stack shifts the operating work to you while keeping a subscription, and it begins with a workshop sold through your account team. Model both options with the same workload, not the list price.
- One-time costs: Migration design, data mapping, integration rebuilds, a hardening pass and initial staff training.
- Recurring costs: Servers or cloud capacity, database administration, patching, backups, monitoring and on-call coverage.
- Support contracts: Zammad publishes Business, Enterprise and Corporation support tiers for self-hosted installations, and Teclib' offers GLPI Network as a hosted option, so price both paths.
- Cost drivers: Ticket volume, number of assets, integrations and the number of administrators you need on staff.
- Quote request: Ask for the subscription price, the workshop fee, the required infrastructure sizing, and the expected admin hours per month, in writing.
Write the comparison as a three-year total using your own sizing, and treat any vendor figure as something to verify in writing.
If your workflows depend on heavily customized forms, approvals, catalog items or deep CMDB relationships, the replacement must support that depth. GLPI covers ITIL incident, problem, change and service level management, along with asset inventory, configuration management, knowledge base and contract management, so it is the stronger fit for ITSM structure. Zammad focuses on agent ticketing, channels and automation for requests. ServiceNow offers a large application ecosystem, which you may need to replicate with custom development or drop.
- Process mapping: List each custom workflow and decide whether GLPI, Zammad or custom code will carry it.
- CMDB depth: Confirm the relationship types, discovery sources and asset classes you rely on are supported by GLPI's configuration management.
- Automation rules: Zammad supports triggers and automations for tickets; test each rule you use today before accepting a gap.
- Integrations: Inventory APIs, directory sync and monitoring connections, and assess whether each needs a connector or new code.
- Ownership: Decide who maintains custom code after go-live, since upgrades will touch it.
Use a proof of concept with your three most complex workflows before committing to a migration plan.
Banks, healthcare providers and public sector bodies need evidence that access, change and incident records are controlled, retained and reviewable. Self-hosting gives you control of those systems, but it does not produce an audit result by itself. DeployOpen prepares systems, controls and evidence for assessments, while independent auditors and certification bodies issue any report. Expect GLPI to hold change and incident evidence and Zammad to hold ticket records, with both likely needed for a complete picture.
- Change control: Confirm that GLPI's change module can enforce the approval steps your change policy requires.
- Access control: Check single sign-on, role-based permissions, administrator separation and audit logging in each product.
- Retention: Define how long tickets, asset histories and attachments must be kept, and test deletion and export.
- Recovery: Plan backups and restore tests, since you own them in both self-hosted options.
- Assessor input: Ask your independent auditor which controls they expect to see before design begins.
Bring the auditor and the security team into the design review early, because the evidence they need shapes the architecture.
A small internal IT team usually needs one tool to handle requests, a register of devices and software, and a simple change record. For a team of this size, GLPI alone often covers the service desk and asset inventory, so Zammad is only worth adding if you also run a separate requester ticketing queue. ServiceNow typically suits larger organizations with dedicated platform staff, so a small team should weigh whether it can carry the operating load of either self-hosted option.
- Single tool: GLPI can handle incidents, requests, assets and a knowledge base in one place.
- Separate queue: Add Zammad only if email-based support from staff or customers needs its own agent interface.
- Operations: Assign one named owner for upgrades, backups and certificate renewals before go-live.
- Inventory feeds: Confirm how devices and software will be discovered and kept current.
- Staffing: Decide whether the team can cover patching and restores without a partner.
If no one on the team can run a database restore, plan for a support contract or a partner before migrating.
How much effort, time and skill does moving off ServiceNow take?
Is running GLPI and Zammad yourself cheaper than staying on ServiceNow?
The software itself is free, so the comparison comes down to the people, infrastructure and support you pay for. GLPI is free asset and IT management software under GPL-3.0, and Zammad is licensed under GNU AGPLv3, so neither carries a per-seat licence fee. Your recurring costs are servers, databases, backups, staff time for upgrades and administration, and any support contract you choose to buy. ServiceNow's costs are subscription and implementation, and its Private Stack model still has you operating the load balancer, application server and database tiers. Ask every vendor and integrator for a written breakdown of one-time and recurring costs, with the same user count, data volume and hosting assumptions on each side.
How long does a ServiceNow to open-source migration take?
No fixed duration can be given without knowing your scope, and the main drivers are the number of workflows, integrations, custom catalog items, approval paths, data volume and how much history you must keep. Migrating ticket data is usually the smaller part. Rebuilding ITIL process flows, change approvals, CMDB relationships and integrations with monitoring or identity systems takes the most time. Zammad's built-in migrators cover Freshdesk, Kayako, OTRS and Zendesk, but not ServiceNow, so a ServiceNow move generally relies on exports and custom import work. Ask for a timeline in writing that lists each workstream and its dependencies.
Can an internal IT team run this migration without outside help?
A capable internal team can run the migration if it has Linux and database administration skills, experience with ITSM process design and a clear owner for each workflow. Plan for skills in web application hosting, PostgreSQL or MySQL administration, reverse proxies, identity integration, email routing and scripted data transformation. Process design matters as much as technology, because GLPI and Zammad will not reproduce ServiceNow's workflows automatically. If those skills are thin, you can buy a fixed-scope engagement from DeployOpen, which plans, implements, integrates, hardens and documents self-hosted platforms in your own infrastructure. Agree on scope, deliverables and timelines in writing before work starts.
What does ServiceNow's Private Stack workshop cover?
ServiceNow's launch post says customers starting a Private Stack deployment go through their account team and should expect to buy a workshop covering architecture planning, hardware sizing, database selection and operational readiness. Private Stack keeps ServiceNow as the supplier of application software, upgrade packages, deployment guidance and support, while the customer or a partner owns and operates the load balancer, application server and database tiers. The workshop is the vendor's entry point for that model. If you consider a self-hosted open-source path, you will need equivalent planning work, so ask what the workshop includes, what it costs and whether its outputs can be reused for an open-source design.
Does GLPI cover CMDB and change approvals?
GLPI covers the core ITIL areas that most teams need, including incident, problem, change and service level management, asset inventory, configuration management, knowledge base and contract management. That makes it a credible base for a CMDB and change process, but it does not replace every ServiceNow feature. Confirm in a proof of concept that its change approval routing, relationship mapping and reporting meet your rules, and check whether you need extra plugins or custom development. Also verify the GLPI version you plan to run, since GLPI 12.0.0 was published on October 7, 2026, and test upgrade paths before committing.
What do Zammad's support tiers add for self-hosted installations?
Zammad's software is open source, and Zammad GmbH sells support contracts for self-hosted installations named Business, Enterprise and Corporation, alongside hosted plans run in German data centers. The software licence is free, so support is the main purchased service for self-hosting. Compare the tiers on response expectations, escalation paths, upgrade assistance and whether named contacts are included, using Zammad's pricing page as the starting point. Zammad's source code is owned by the Zammad Foundation, independent of Zammad GmbH, which means you are not dependent on one company for the code itself. Ask whether a third-party partner can provide equivalent support if you prefer.
How are upgrades and backups handled when you self-host?
When you self-host, you own upgrades and backups, and that work recurs for as long as you run the platform. Test each GLPI and Zammad release in a staging environment that matches production, then back up the database, attachments and configuration before each change. Schedule restore tests, not just backups, and record the results as evidence for your compliance team. For comparison, Jira Cloud's backup manager excludes automation rules, third-party apps and Assets, which shows why you should check exactly what any backup covers. Write down who approves upgrades, how long a rollback takes and who is on call.
How DeployOpen scopes, migrates and supports the move
DeployOpen is a Chainscore Labs company that plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a move off ServiceNow, that means scoping the GLPI and Zammad deployment against your actual ITSM processes and data before any work starts.
How we scope
- Inventory which ServiceNow ITSM processes, catalogs, approvals and integrations your teams depend on today
- Agree in writing which GLPI modules and Zammad channels are in scope, and which gaps need custom work
- Confirm with your team the hosting model, data residency needs and any Private Stack exit timeline before committing
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts
How we build
- Deploy GLPI and Zammad in your own infrastructure, with the database, application and load balancer tiers documented
- Configure ITIL incident, problem, change and asset workflows to match the processes you agreed to keep
- Plan and test data extraction from ServiceNow, checking which records, attachments and configuration items carry over
- Test integrations, access controls and hardening settings before any production cutover
How we hand over
- Document architecture, configuration, runbooks and the data mapping used for the migration
- Deliver backup and restore procedures and verify that a restore works in your environment
- Provide a list of what did not migrate, such as custom scripts or workflow logic, so you can plan rebuilds
- Prepare operational evidence and control documentation for your own compliance assessors, who issue any formal opinion
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- Upgrade planning covers GLPI and Zammad release cycles, so your team is not left to track them alone
- Ask any proposal to name who maintains patches, backups and security testing after go-live
- A quote follows from the written scope, so request line items for build, migration, testing and retainer separately
