GLPI 11 is the biggest platform update since version 10. It brings structural changes that affect plugins, workflows, and the user experience. See what changed and what you need to adapt.
Main new features in GLPI 11
Modernized interface
GLPI 11 replaced the procedural PHP frontend with a modern stack using Symfony and Twig templates. The interface is cleaner, responsive, and accessible.
Native forms
The most anticipated feature: GLPI 11 incorporated customizable forms into the core. You create forms with conditional fields, sections, and display logic directly in the interface, without plugins.
This replaces the FormCreator plugin for most use cases. See our FormCreator vs native forms comparison.
Custom objects
GenericObject, one of the most popular plugins, was also incorporated into the core. You can now create custom object types directly in GLPI.
Native webhooks
GLPI 11 offers basic outbound webhook support, allowing you to notify external systems when events occur (ticket creation, status change, etc.).
Performance improvements
Reduced page load times, lower memory consumption, and SQL query optimization for databases with millions of records.
Plugins incorporated into the core
These plugins are no longer needed in GLPI 11:
- FormCreator – replaced by native forms
- GenericObject – replaced by native custom objects
Plugins compatible with GLPI 11
- NexTool – all modules compatible with GLPI 10 and 11
- Escalade – ticket escalation
- Fields – custom fields
- DataInjection – CSV import
- PDF – export items to PDF
- Tag – item labels
- ActualTime – real-time tracking
- MReporting – charts and visual reports
Incompatible or discontinued plugins
- FusionInventory – replaced by the native GLPI Agent since GLPI 10
- Dashboard – replaced by GLPI 10+ native dashboards
- Plugins not updated since 2023 – check case by case
What to adapt during migration
Forms
Forms created in FormCreator need to be recreated in GLPI 11 native forms. There is no automatic migration.
Themes and custom CSS
CSS applied via entity may need adjustments, since the HTML structure of GLPI 11 changed significantly.
API integrations
The GLPI REST API maintains compatibility, but verify whether specific endpoints from removed plugins are still being used by external integrations.
Should I migrate now?
If your plugins are compatible and you have a staging environment to test, yes. GLPI 11 is more modern, secure, and performant. If you heavily depend on incompatible plugins, wait for compatible versions or look for alternatives.
Next step
Consult our GLPI 10 → 11 migration guide for the complete technical walkthrough.
