The GLPI 10 to 11 move and the plugin data migrations it requires, since forms and generic assets moved into the core.
Planning the move from GLPI 10 to 11: PHP and database prerequisites, plugin compatibility and reactivation, migrating Generic Objects, Fields and FormCreator in order, removed XML-RPC API, and testing on a copy of the GLPI 10 database.
Moving self-service forms built with the Formcreator plugin into GLPI 11 native forms: the migration tool version of the plugin, the core console command, Fields dependencies, checking question types and targets, and retiring the plugin afterward.
Converting asset types built with the Generic Objects plugin into GLPI 11 asset definitions: updating the plugin first, copying plugin files to a new instance, running the core migration command, and re-checking rights, capacities and integrations that used the old types.
Moving data from the old Racks and Domains plugins into GLPI core tables with the console migration commands, and checking what the Racks migration ignores.
Cleaning up older GLPI databases with the console: MyISAM to InnoDB, dynamic row format, utf8 to utf8mb4 and unsigned keys, and using Percona tools when tables are large.
Converting GLPI datetime columns to timestamps and granting MySQL timezone access so multi-country service desks see correct times, with the console commands involved.
Why GLPI suspends plugins after a new version is detected, checking plugin compatibility before major updates, and reactivating or replacing plugins whose features moved into the core.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.