+++
title = "Upgrading to ES 5"
weight = 25
updated = 2023-06-17

aliases = ["/docs/upgrading-to-es-5.html", "/docs/managed-search/elasticsearch-and-opensearch/cluster-management/version-upgrades/guides/upgrading-to-elasticsearch-version-5/"]

[extra]
nav_title = "Upgrading to ES 5"
weight = 30
+++

{% admonition(title="Info") %}
This document serves to highlight key breaking changes for our customers. It does not represent the [full list of breaking changes](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/breaking-changes-5.0.html). As always, we recommend you [test your searches](@/docs/cluster-management/version-upgrades/upgrading-major-versions/index.md) on the new version of Elasticsearch before moving forward.
{% end %}

Elasticsearch 5 brings with it the removal of the `string` type and has been replaced with `text` and `keyword`.

## General Solutions

Analyze your mappings and look for `string` mapping types. You will want to review how you use those fields to determine if you should use `text` or `keyword` going forward.

`text`: you want full text search analysis on

`keyword`: you want to search for the value exactly as is, a PO Number, or url for example

### From 2.x

There are no specific tricks for this upgrade process, outside of the General Solution listed above. We would simply recommend you follow our [traditional process for testing](@/docs/cluster-management/version-upgrades/upgrading-major-versions/index.md) your searches on a new version of Elasticsearch.

### From 1.x

There are no specific tricks for this upgrade process, outside of the General Solution listed above. We would simply recommend you follow our [traditional process for testing](@/docs/cluster-management/version-upgrades/upgrading-major-versions/index.md) your searches on a new version of Elasticsearch.