How to Migrate from GLPI 10 to GLPI 11: Complete Guide

Step-by-step guide to safely migrate from GLPI 10.0.x to GLPI 11: backup, plugin compatibility, database upgrade and post-migration verification.

Migrating from GLPI 10 to GLPI 11 is an important step that brings a modernized interface, native forms and performance improvements. This guide covers the entire process safely.

Before you start: pre-migration checklist

  • Full database backup (mysqldump)
  • Backup of directories /etc/glpi, /var/lib/glpi and /var/www/glpi/plugins
  • Check current version: must be GLPI 10.0.x (latest minor release)
  • Check compatibility of each installed plugin with GLPI 11
  • Have a staging environment for testing
  • PHP 8.1 or higher installed

1. Plugins: what changes in GLPI 11

Incorporated into core (remove before migrating)

  • FormCreator – forms are now native to GLPI 11
  • GenericObject – custom objects are now native

Compatible (check version)

  • Escalade, Fields, DataInjection, PDF, Tag – have versions for GLPI 11
  • NexTool – compatible with GLPI 10 and 11

Incompatible or discontinued

  • FusionInventory – replaced by native inventory (GLPI Agent)
  • Plugins that have not been updated since 2023

2. Full backup

# Database
mysqldump -u root -p --single-transaction glpi > /backup/glpi_pre_migration.sql

# Files
tar -czf /backup/glpi_files_pre_migration.tar.gz /var/www/glpi /etc/glpi /var/lib/glpi

3. Disable incompatible plugins

In GLPI 10, go to Configuration > Plugins and disable all plugins that do not have a version for GLPI 11. Remove the directories of incompatible plugins.

4. Update GLPI files

cd /tmp
wget https://github.com/glpi-project/glpi/releases/download/11.0.0/glpi-11.0.0.tgz
tar -xzf glpi-11.0.0.tgz

# Replace files (preserve config and data)
rsync -av --delete /tmp/glpi/ /var/www/glpi/ --exclude plugins/ --exclude marketplace/
chown -R www-data:www-data /var/www/glpi

5. Run the database migration

php /var/www/glpi/bin/console db:update --no-interaction

This command applies all schema migrations from GLPI 10 to 11. Monitor the output – any error must be resolved before proceeding.

6. Clear cache and sessions

php /var/www/glpi/bin/console cache:clear
rm -rf /var/lib/glpi/_sessions/*

7. Post-migration verification

  • Access GLPI and verify that login works
  • Check the version in Configuration > General
  • Verify that tickets, assets and users are present
  • Test opening a new ticket
  • Check logs in /var/log/glpi/ for errors
  • Reactivate and update compatible plugins one by one

8. Common issues

Permission error

Ensure that www-data has write permission on the data directories.

Plugin not loading

Check whether the plugin version is compatible with GLPI 11. Old plugins can cause a 500 error.

FormCreator forms

FormCreator forms are not automatically migrated to the native forms in GLPI 11. They will need to be recreated manually.

Next step

After migration, explore the new features of GLPI 11 and configure the native forms.

Frequently Asked Questions

Yes, as long as you perform a full backup beforehand, check plugin compatibility and test in a staging environment. The migration is irreversible on the database.

It depends on the plugin. FormCreator and GenericObject have been incorporated into the core. Others like Escalade and Fields have compatible versions. Check the official page of each plugin.

The database migration takes 5 to 30 minutes depending on data volume. Planning and testing in staging can take 1 to 5 days.

No. The migration alters the database structure irreversibly. That is why it is essential to make a backup first and test in a staging environment.

Need help?