GLPI 10 end of support: should you upgrade to GLPI 11 or GLPI 12?

In 30 seconds

• GLPI 10 still works, but it no longer gets security patches.
• You can move to GLPI 11 or straight to GLPI 12, depending on your plugins and your server.
• Before upgrading, check requirements, plugins, integrations and backups, and test on a copy.

Your GLPI 10 will keep working. Users can still open tickets, technicians can keep working and the inventory stays available. What changed is that GLPI 10 no longer receives security updates as part of the regular support cycle.

GLPI 12.0.0 was released on October 7, 2026. With it, GLPI 10 dropped out of the two major versions the project officially maintains.

If you’re still on GLPI 10, it’s time to plan the upgrade. The question is which version to move to and what to check first.

GLPI 10 has reached end of support. What does that mean?

GLPI 10.0.28, released on September 30, 2026, was the last update in that branch.

That doesn’t mean your installation stops working, or that you have to upgrade overnight. It means that when new vulnerabilities or bugs appear, there will be no official fixes for GLPI 10, and GLPI Network subscription support doesn’t cover it either.

In June 2026, GLPI released updates that fixed 16 vulnerabilities, including SQL injection and privilege escalation flaws. Nine of them also affected GLPI 10. In September, GLPI 11.0.10 fixed eight more; six of them also affected GLPI 10 and were fixed in 10.0.28, the last release of that branch. Until then, both branches received patches. From now on, new flaws found in GLPI 10 will stay open.

Consider what a GLPI installation usually holds: users, internal requests, attached documents, the equipment inventory, customer data and integration credentials.

If you’re running a version older than GLPI 10.0.28, start by moving to that last patch while you prepare the upgrade. It’s a stopgap, not a fix for the end of support.

Should you move to GLPI 11 or straight to GLPI 12?

GLPI 11: the more mature option

GLPI 11 was released in September 2025, and version 11.0.11 has been available since October 1, 2026.

It introduced native forms, custom assets, a new self-service portal, two-factor authentication and webhooks. It also brought into the core features that used to depend on plugins, such as Formcreator and Generic Objects.

It’s worth considering if your installation runs several plugins, integrations or processes that have already been tested on GLPI 11. Its advantage is the time it has been available and the fixes it has received since launch. You still need to test, especially if you use custom development.

GLPI 12: the latest version, with more changes

GLPI 12 is now stable. Its changes include a reworked knowledge base, active session management, new security measures and OLAs that can now be linked to the groups doing the work. It also adds a new version of the API. We cover these changes in GLPI 12: what changes for technicians and administrators.

GLPI 12 requires at least PHP 8.3 and MariaDB 10.11 or MySQL 8.0. It also introduces changes that can affect existing plugins, integrations and settings. For example, knowledge base categories become part of a new structure, and access permissions need to be reviewed after the upgrade.

So which one should you choose?

If your installation has many plugins or critical integrations that are already compatible with GLPI 11, that may be the more sensible choice, because it reduces the number of changes at once.

If your infrastructure meets the new requirements, your plugins are ready and your tests pass, you can consider upgrading straight to GLPI 12.

If your installation is exposed to the internet, holds sensitive information or receives requests from customers, don’t put off the planning. Even when GLPI is only reachable from an internal network, the end of support still matters.

What to check before upgrading GLPI

An upgrade can be simple or quite complex. The difference usually lies in the plugins, customizations and integrations added over the years. Before upgrading, review these points.

1. Server requirements

Version	Status	Minimum PHP	Minimum database
GLPI 10	Unsupported since 10.0.28	7.4	MySQL 5.7 or MariaDB 10.2
GLPI 11	Supported	8.2	MySQL 8.0 or MariaDB 10.6
GLPI 12	Supported, latest version	8.3	MySQL 8.0 or MariaDB 10.11

Also check the PHP extensions and the web server configuration. In Apache or Nginx, for example, the document root must point to GLPI’s public directory.

2. Plugin compatibility

Make an inventory of every installed plugin, including the ones you developed or modified in-house. Checking that a new version exists isn’t enough: you need to confirm that the features your team uses still work.

Since GLPI 11, after a major upgrade, plugin execution is suspended until you resume it from the administration panel or with the command php bin/console plugin:resume_execution.

3. Formcreator, Generic Objects and Fields

GLPI 11 brought forms and custom assets into the core, but existing data doesn’t carry over just by copying files.

The official documentation sets out a specific procedure and recommends updating these first:

• Generic Objects to version 2.14.14 or later.
• Formcreator to version 2.13.10 or later.
• Fields to a compatible version, if you use it with Formcreator.

After upgrading GLPI, run the corresponding migrations in the documented order: Generic Objects first, then Formcreator, with Fields installed and enabled where applicable. The commands are migration:genericobject_plugin_to_core and migration:formcreator_plugin_to_core.

Some saved searches and display preferences from Generic Objects also have to be rebuilt by hand. See the official plugin migration procedure.

4. Integrations and automation

If you use LDAP or Active Directory, mail collectors, OAuth, the REST API, GLPI Agent, notifications or integrations with other systems, test them in the target environment. Also review automatic actions and any processes that depend on external scripts.

A login screen that works doesn’t mean the whole installation upgraded correctly.

5. Data integrity and backups

Before upgrading, run php bin/console db:check to catch inconsistencies in the database structure. You also need a full backup of the database, documents, configuration files and plugins.

Pay special attention to the glpi.key, glpicrypt.key, oauth.pem and oauth.pub keys, where they apply to your installation.

Losing the encryption files can prevent GLPI from recovering securely stored information.

A backup isn’t a recovery plan until you’ve confirmed you can restore it.

Don’t run your first test in production

The safest way to approach a major upgrade is to set up an isolated copy of your current installation. There you can find problems without affecting the people who use GLPI every day.

In that environment, check that users can log in, tickets get created, assignment rules work, forms behave as before and notifications go out correctly. Check the inventory, integrations and permissions too.

Once everything checks out, you can schedule the production upgrade, set a maintenance window and have a rollback procedure ready. It’s more work up front, but it saves you from finding out mid-workday that a form stopped creating tickets or an integration no longer responds.

Can you go straight from GLPI 10 to GLPI 12?

Yes. You don’t have to install GLPI 11 as an intermediate step. The documentation covers upgrades across major versions and procedures for migrating plugin data such as Formcreator and Generic Objects.

What matters is checking the target version’s requirements and testing the full process before running it in production.

How we can help with the upgrade

We handle upgrades as part of our GLPI consulting and support service. First we review the version, plugins, integrations and server. Then we set up a test copy with your data, validate it with your team and plan the production cutover with a rollback plan in case something fails.