Migrate saved objects
editMigrate saved objects
editEach time you upgrade Kibana, an upgrade migration is performed to ensure that all saved objects are compatible with the new version.
Kibana includes an Upgrade Assistant to help you prepare for an upgrade. To access the assistant, go to Stack Management > Upgrade Assistant.
Kibana 7.12.0 and later uses a new migration process and index naming scheme. Before you upgrade, read the documentation for your version of Kibana.
The following instructions assumes Kibana is using the default index names. If the kibana.index or xpack.tasks.index configuration settings are different from the default, adapt the instructions accordingly.
How saved objects migrations work
editSaved objects are stored in two indices:
-
.kibana_{kibana_version}_001, e.g. for Kibana 7.12.0.kibana_7.12.0_001. -
.kibana_task_manager_{kibana_version}_001, e.g. for Kibana 7.12.0.kibana_task_manager_7.12.0_001.
The index aliases .kibana and .kibana_task_manager always point to
the most up-to-date saved object indices.
When you start a new Kibana installation, an upgrade migration is performed before starting plugins or serving HTTP traffic. Before you upgrade, shut down old nodes to prevent losing acknowledged writes. To reduce the likelihood of old nodes losing acknowledged writes, Kibana 7.12.0 and later adds a write block to the outdated index.
The following tables lists the saved objects indices used by previous Kibana versions.
Table 1. Saved object indices and aliases per Kibana version
| Upgrading from version | Outdated index (alias) |
|---|---|
6.5.0 through 7.3.x |
|
7.4.0 through 7.11.x |
|