Migrating from GLPI 10 to GLPI 11 – what you need to know

GLPI 10 remains under Long-Term Support until 2027, but active development has shifted entirely to the 11.x branch. The current stable release is 11.0.7. If your organisation still runs GLPI 10, now is the right time to plan the transition – while there is room for thorough testing, well before support ends.

System requirements for GLPI 11

Before starting the migration, verify that your infrastructure meets the new minimum requirements:

• PHP: 8.2 or later (8.3 recommended)
• MySQL: 8.0 or later
• MariaDB: 10.6 or later
• Web server: Apache 2+, Nginx, lighttpd, or IIS
• New mandatory PHP extensions: bcmath, mbstring, openssl (compared to GLPI 10)

Organisations still running PHP 7.x or MySQL 5.7 must upgrade the server platform first.

Plugins absorbed into core

GLPI 11 integrates three widely-used plugins directly into its core:

• FormCreator – end-user request forms are now a native GLPI feature
• Generic Objects – custom asset types are defined through Asset Definitions
• Fields – custom fields remain a plugin but require an update for compatibility

These plugins must be migrated in strict order: Generic Objects first, then Fields, then FormCreator. Before migrating, update Generic Objects to at least version 2.14.14 and FormCreator to at least version 2.13.10.

Step-by-step migration procedure

1. Back up the database and files – including config/, files/, and plugins/ directories. If the server is virtualised, take a snapshot.
2. Check database integrity – run php bin/console db:check and resolve any schema inconsistencies.
3. Migrate plugins – run the migration scripts for Generic Objects, Fields, and FormCreator in that order.
4. Install GLPI 11 – download the archive from GitHub releases, extract to a fresh directory, and restore configuration files (glpi.key, glpicrypt.key, oauth.pem, oauth.pub, downstream.php).
5. Run the update – execute php bin/console db:update or use the web interface.
6. Resume plugins – run php bin/console plugin:resume_execution or re-enable through the administration panel.

Common pitfalls

• Once GLPI detects new version files, the application becomes unavailable until the update finishes – plan a maintenance window.
• Display preferences and saved searches for custom types from Generic Objects must be recreated manually.
• Never restore a database backup into a different GLPI version without running the update scripts.
• Test the migration in a staging environment first to minimise production downtime.

Timeline and recommendations

GLPI 10 continues to receive security patches (currently at 10.0.25), but new features are developed exclusively for the 11.x branch. LTS for GLPI 10 ends in 2027. We recommend scheduling the migration for the second half of 2026 – giving your team time for thorough testing and training before support ends.