# Migrate of specific plugins from GLPI 10 to GLPI 11 🆕

{% embed url="<https://www.youtube.com/watch?v=TR-NRIErTP8>" %}

This procedure is based on the installation described in this article:

<a href="/pages/yQNUFtGH9OtbZ4XGhoDW" class="button secondary">Updating GLPI</a>

It must, of course, be adapted to your own environment.

Here you will find the procedure to migrate GLPI 10 to GLPI 11, as well as the following plugins:

* **Generic Objects** (now included in the core)
* **Fields** (required if you use Fields with FormCreator)
* **FormCreator** (now included in the core)

{% hint style="warning" %}
We recommend updating these three plugins before beginning your migration. This will save you from having to install the plugins on your new instance in order to prepare for their migration. Fields, however, must be installed in all cases.
{% endhint %}

{% hint style="warning" %}
If you have two or more of the plugins listed above, migrate them in the order indicated.
{% endhint %}

{% hint style="success" %}
If you are using a [Cloud version](https://www.glpi-project.org/en/pricing/), plugin migration will be automatic. Migration from GLPI 10 to GLPI 11 will be available upon request only (coming soon).
{% endhint %}

***

## Plugin migration

### Generic Objects

* **If your plugin was not up to date before the migration (version prior to 2.14.14)**, please download and activate the plugin from the marketplace. Otherwise, proceed to the section ‘Enter the following command’.

<div align="left"><figure><img src="/files/wqTvZ5k9x5ZcbfkLwgdy" alt=""><figcaption><p>Generic Object plugin installed and activated</p></figcaption></figure></div>

Generic Objects plugin enabled

{% hint style="warning" %}
If you are migrating to a new instance, remember to copy the plugin files from the `/files/_plugins/genericobject` directory to the new `files/_plugins/` directory of your new instance.
{% endhint %}

By clicking on the wrench icon, you can view the items detected by the plugin that will be migrated.

<figure><img src="/files/OYUa9saWQ4AM2epVPXgl" alt=""><figcaption><p>Steps to migrate </p></figcaption></figure>

<figure><img src="/files/ylDsmZAsEHQ2hHyo6gEu" alt=""><figcaption><p>Assets to migrate to assets definitions</p></figcaption></figure>

* Run the following command

For Ubuntu and similar systems:

```
sudo -u www-data php bin/console migration:genericobject_plugin_to_core
```

For CentOS and similar systems:

```
sudo -u apache php bin/console migration:genericobject_plugin_to_core
```

The process may take some time if you have a large amount of data to migrate.\
You should get a result similar to the following:

```php
[============================] 100%
> 2 custom assets imported successfully.
> 1 "server" object imported successfully.
> 1 "videoprojector" object imported successfully.
Migration is complete.
🛈 Display preferences and saved searches related to a `genericobject` type must be 
recreated manually.
✓ 6 items created.
```

The migrated elements will be visible from the park as well as from the Generic Objects plugins.

<figure><img src="/files/oWjlbyc6VQzfvffpSphb" alt=""><figcaption><p>Post-migration verification of Generic objects</p></figcaption></figure>

***

### Fields

{% hint style="info" %}
This step is required if you use Fields with FormCreator.
{% endhint %}

{% hint style="warning" %}
If you are migrating to a new instance, remember to copy the plugin files from the `/files/_plugins/fields` directory to the new `files/_plugins/` directory of your new instance.<br>
{% endhint %}

This is not a migration per se, but you must ensure that the plugin is present and enabled.

<div align="left"><figure><img src="/files/HZ5JlCBfHCD29sYfgwLF" alt=""><figcaption><p>Fields plugin installed and enabled</p></figcaption></figure></div>

***

### FormCreator

* **If your plugin was not up to date before the migration (version prior to 2.13.10)**, please install and activate the FormCreator plugin. Otherwise, proceed to the section ‘Enter the following command’.

<div align="left"><figure><img src="/files/YWs6kSHjN4XdA4x44BtB" alt=""><figcaption><p>FormCreator plugin isntalled and enabled</p></figcaption></figure></div>

* From **`Tools`** > **`Formcreator EOL Info`**, you can view the number of forms to be migrated and those natively present in GLPI (2 by default).

<figure><img src="/files/kB86JEfjhY5TCec8oW4P" alt=""><figcaption><p>Steps to migrate </p></figcaption></figure>

<figure><img src="/files/pV66t3Z9Lk02VZb8kBoW" alt=""><figcaption><p>Number of forms to migrate</p></figcaption></figure>

* Then run the following command

For Ubuntu and similar systems:

```
sudo -u www-data php bin/console migration:formcreator_plugin_to_core
```

For CentOS and similar systems:

```
sudo -u apache php bin/console migration:formcreator_plugin_to_core
```

The process may take some time if you have a large amount of data to migrate.\
You should get a result similar to the following:

```php
[============================] 100%
Migration is complete.
✓ 51 items created.
✓ 21 items reused.
```

You can view the result from the migration status via **`Tools`** > **`Formcreator EOL Info`**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.glpi-project.org/tutorials/procedures/migrate-of-specific-plugins-from-glpi-10-to-glpi-11.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.