# Upgrade Path for very old version **URL:** \ **Category:** Elasticsearch\ **Created:** [September 15, 2021, 4:18pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309 "2021-09-15T16:18:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![AlanM](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@AlanM](https://discuss.elastic.co/u/AlanM)\ **Post date:** [September 15, 2021, 4:18pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309/1 "2021-09-15T16:18:17Z")
Hi, I have recently inherited an ELK stack 1.3.2/1.4.2/3.01 which will be moved to new platforms and upgraded at the same time. Is there any documentation around upgrading something so old ? Also, I'd want to remove as much old data as possible, so is there a setting in the old versions of the software that will allow me to 'age-out' some data ? I've tried to find the documentation for these early versions but it seems to keep keeping to the latest version so I'm not sure if the information is correct. Thanks in advance, Alan ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [September 15, 2021, 4:59pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309/2 "2021-09-15T16:59:23Z")
I would say the easiest approach would be to spin up an entirely new cluster and migrate the data doing a reindex, you could use logstash to reindex your data from the old cluster to the new cluster. But a lot of things changed from these old versions, the mappings changed, you can't have multiple types in the same index anymore and a lot of other things. You will need to check the breaking changes for every major version since your current version to see what affects you. In the documentation page you can select to see the documentation of a specific version, for example these are the breaking changes for [version 2.0](https://www.elastic.co/guide/en/elasticsearch//reference/2.0/breaking-changes-2.0.html). ---
**Author:** ![AlanM](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@AlanM](https://discuss.elastic.co/u/AlanM)\ **Post date:** [September 15, 2021, 8:56pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309/3 "2021-09-15T20:56:36Z")
Thanks for your response Leandro. I suspected that this would not be simple and was thinking that we would need to build a new instance and just let the old one fade away as the data aged out. We only have a life of 2 or 3 months on the data anyway. ---
**Author:** ![TheDeveloper](https://avatars.discourse-cdn.com/v4/letter/t/439d5e/32.png) [@TheDeveloper](https://discuss.elastic.co/u/TheDeveloper)\ **Post date:** [September 16, 2021, 4:56pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309/4 "2021-09-16T16:56:57Z")
If you did decide to migrate, the Reindex API can help: [Reindex API | Elasticsearch Guide [7.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/docs-reindex.html#reindex-from-remote). You can use the "script" param to modify documents in transit (e.g. renaming fields) [Reindex API | Elasticsearch Guide [7.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/docs-reindex.html#docs-reindex-change-name) This has worked for me migrating from a cluster on 2.3. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 14, 2021, 4:57pm UTC](https://discuss.elastic.co/t/upgrade-path-for-very-old-version/284309/5 "2021-10-14T16:57:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.