# Safely upgrade from Elasticsearch 1.7.3 to 7.x **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2019, 5:52am UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973 "2019-10-17T05:52:12Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![deltafarce](https://avatars.discourse-cdn.com/v4/letter/d/ccd318/32.png) [@deltafarce](https://discuss.elastic.co/u/deltafarce)\ **Post date:** [October 17, 2019, 5:52am UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973/1 "2019-10-17T05:52:13Z")
Hello, this might be too basic a question for the forums, but I'm in the process of upgrading our infrastructure and we run the really outdated version of Elasticsearch 1.7.3. It badly needs an upgrade to a service supported release (I'd prefer the latest 7.x to take full advantage). I've been researching the Elasticsearch documentation, and from what I see I have to perform a triple migration - from 1.7.3 to 2.x, then to 5.x, and finally to 7.x (in order to accommodate for breaking changes to the index architecture). Is this the correct way to do it, or am I missing something? And is there a better, less messier way to perform this upgrade and not mess with our existing infrastructure or data? Thanks in advance! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 17, 2019, 7:15am UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973/2 "2019-10-17T07:15:53Z")
Welcome! What is your use case ? Logs? Search? Something else? ---
**Author:** ![deltafarce](https://avatars.discourse-cdn.com/v4/letter/d/ccd318/32.png) [@deltafarce](https://discuss.elastic.co/u/deltafarce)\ **Post date:** [October 17, 2019, 9:53am UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973/3 "2019-10-17T09:53:11Z")
Hi, thanks for responding! We use it for search purposes strictly, around 20000 records in our index. Elasticsearch 1.7.3 on CentOS. No other ELK products used in conjunction. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 17, 2019, 12:21pm UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973/4 "2019-10-17T12:21:21Z")
20000 documents is super low. I'd just reindex all data in a new cluster. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 14, 2019, 12:21pm UTC](https://discuss.elastic.co/t/safely-upgrade-from-elasticsearch-1-7-3-to-7-x/203973/5 "2019-11-14T12:21:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.