GLPI 10 End of Support: Upgrade to GLPI 11 or Switch Tools?

GLPI® released version 12 in October 2026 and, with it, GLPI 10 lost official support. For an IT team still running GLPI 10, this means operating without bug fixes, security updates, or assistance from the GLPI Network subscription. Below, you'll find the dates for each version, what changes in GLPI 11 and GLPI 12, how to upgrade step by step, and when it makes sense to switch tools.

Is GLPI 10 still supported?

No. With the release of GLPI 12, GLPI 10 stopped receiving bug fixes, security updates, and assistance from the GLPI Network subscription, according to the official announcement of the GLPI 10 end of support. Version 10.0.28, released on September 30, 2026, was the last one in the 10 branch. The only exception is customers who purchased GLPI Network Extended Support, who remain covered according to the GLPI 12 announcement.

GLPI version timeline

GLPI currently has three major versions in circulation, and only two of them are supported. The table shows when each one was released, according to the official blog, and its status as of October 2026.

GLPI's support model always covers the two latest major versions. That's why each new major version ends support for the oldest one.

What happens if you stay on GLPI 10

GLPI 10 keeps working after the end of support, but every flaw discovered from now on goes unpatched. The risk grows quickly because GLPI itself started releasing security versions every two weeks in September 2026, due to the rise in vulnerability reports. These fixes reach GLPI 11 and GLPI 12, not version 10.

In practice, staying on GLPI 10 has four consequences:

• Unpatched vulnerabilities: flaws that show up in upcoming security versions remain open in your instance.
• Outdated plugins: plugin developers follow the supported versions, and compatibility with GLPI 10 tends to fall behind.
• No official assistance: anyone relying on GLPI support through the GLPI Network subscription loses that coverage, except under Extended Support.
• Regulatory exposure: a system that stores user and ticket data without security updates makes it harder to comply with data protection laws such as the GDPR (General Data Protection Regulation) in the European Union and the CCPA (California Consumer Privacy Act) in the United States, which require security measures to protect personal data.

What's new in GLPI 11

GLPI 11 was released on September 30, 2025, and brought five main new features, according to the official GLPI 11 announcement.

Native custom assets. You can create any type of asset, add it to the main menu, and adapt its behaviors and fields.

Built-in forms. A new interactive editor lets you build forms for technicians and end users inside GLPI itself.

New self-service portal. The portal was redesigned to help users find the services the IT team offers.

2FA (two-factor authentication). Access to GLPI gained an extra layer of verification on top of the password.

Webhooks. GLPI now triggers HTTP calls to external applications when an event occurs, which makes integrations easier without additional development.

The full list of changes is available in the project's official changelog.

GLPI 11 or GLPI 12: which version should you upgrade to?

GLPI recommends that anyone on GLPI 10 migrate to GLPI 11 or GLPI 12. The choice depends on the team's infrastructure and plugins, because GLPI 12 brings structural changes and higher technical requirements, according to the official GLPI 12 announcement.

These are the main changes in GLPI 12:

• Redesigned knowledge base: reading and editing now happen on the same screen, and categories no longer exist as a separate structure. During the upgrade, each category becomes an article, and visibility permissions need to be configured again.
• Session control: administrators can see who is logged in and end any active session with one click, which helps in cases such as a lost laptop or a leaked password.
• OLA (Operational Level Agreement) per team: each team involved in resolving a ticket has its own deadline and its own overdue status, instead of a single timer per ticket.
• API v3: the new version of the high-level API works alongside the previous ones, and existing integrations keep running.

Jumping straight to GLPI 12 makes sense when the server already runs PHP 8.3 and MariaDB 10.11 (or MySQL 8.0) and the plugins used day to day are already compatible with the new version. Since support covers the two latest major versions, GLPI 12 stays covered longer than GLPI 11. GLPI 11 can be the intermediate step when a critical plugin hasn't been adapted to GLPI 12 yet or when the infrastructure doesn't meet the new requirements.

How to upgrade GLPI 10 step by step

To upgrade GLPI 10 without disrupting service, GLPI itself recommends testing everything first in a separate environment and only then migrating production. The steps below follow the guidance in the official GLPI 12 announcement.

1. Take inventory of your plugins. List every installed plugin and check with each developer whether a version compatible with the target version is already available. GLPI Network plugins are adapted by GLPI itself; community and in-house plugins need to be checked one by one.
2. Check the technical requirements. Make sure the server meets the minimum PHP and database versions for the chosen version (see the table in the previous section).
3. Make a full backup. Save the database and the installation files before making any changes.
4. Set up a test environment. Use a copy of production and test the processes the team uses most, such as ticket creation, approvals, and reports.
5. Review the eight points GLPI flags for the migration to GLPI 12:

1. Knowledge base: existing categories stay hidden until an administrator grants access again.
2. Plugins: each plugin must be compatible with GLPI 12.
3. Monitoring: tools that monitor automatic actions need to be updated to the new format.
4. Requirements: PHP 8.3 and MariaDB 10.11 (or MySQL 8.0), at minimum.
5. Reverse proxy: an extra directive must be added to the configuration.
6. Internal feeds: RSS feeds, calendars, and webhooks pointing to internal servers are blocked by default and need to be authorized.
7. Inventory: enabling inventory now requires choosing an authentication method.
8. OLA reports: custom reports that use OLA data need to be rebuilt.

1. Schedule a maintenance window. Migrate production at an agreed time, with the full backup at hand and a tested rollback procedure.
2. Reassign knowledge base permissions. Right after migrating to GLPI 12, grant access again to the former categories, which are now articles.

Upgrade or switch tools?

The end of support forces the team to migrate either way, which makes it a good time to assess whether GLPI still meets the operation's needs. Staying on GLPI and upgrading makes sense when the organization has a technical team dedicated to maintaining the server, the database, and the plugins, and when it can apply the security versions that now come out every two weeks.

Switching tools becomes the more logical option in three situations:

• No team to maintain the installation: each upgrade requires reviewing requirements, plugins, permissions, and integrations, as the eight points of the migration to GLPI 12 show.
• Pace of security fixes: with biweekly releases, the team needs to set aside fixed time just to test and apply updates.
• Need for vendor support: official GLPI assistance depends on a GLPI Network subscription, and those who need direct support included in the service may prefer another platform.

Those who decide to switch can compare the best GLPI alternatives by deployment model, included support, and maintenance effort. In the GLPI vs. InvGate comparison, the central difference lies between maintaining the platform on your own and using a no-code solution with vendor support.

Why consider InvGate Service Management

For those who decide to switch tools instead of upgrading, InvGate Service Management is a no-code ITSM (IT Service Management) platform designed for enterprise organizations moving away from legacy tools. Two points make a difference in this transition:

• Configuration without developers: with InvGate Service Management, the IT team builds workflows, forms, and approvals without coding, and deploys the platform in the cloud or on-premise.
• Certified security: InvGate holds ISO 27001:2022 certification and SOC 2 Type II audits, which independently validate how we protect products and data.

Frequently asked questions about the GLPI 10 end of support

How long is GLPI 10 supported?

GLPI 10 was supported until the release of GLPI 12, on October 7, 2026. Since then, only GLPI Network Extended Support customers remain covered.

What is the latest version of GLPI 10?

The latest version is 10.0.28, released on September 30, 2026. It won't receive any new bug fixes.

Can you skip from GLPI 10 straight to GLPI 12?

Yes. GLPI recommends migrating to GLPI 11 or GLPI 12, as long as the server has PHP 8.3 and MariaDB 10.11 (or MySQL 8.0) and the plugins are compatible.

How long is GLPI 11 supported?

GLPI 11 remains supported until the release of the next major version after GLPI 12. GLPI hasn't announced a date for that version yet.

The GLPI 10 end of support is the time to decide between continuing to maintain the tool or moving to a no-code platform with fast deployment and vendor support. Try InvGate Service Management for 30 days with the free trial or talk to our Sales team to find the licensing model that best fits your company.

The information about GLPI was obtained from the project's official website on October 30, 2026, and may change. GLPI is a registered trademark of its respective owners.