# Migrate data from current production Elasticsearch nodes to a new hardware

**URL:** <https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682>\
**Category:** Elasticsearch\
**Created:** [June 18, 2020, 5:33pm UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682 "2020-06-18T17:33:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaushalshriyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaushalshriyan/32/44563_2.png) [@kaushalshriyan](https://discuss.elastic.co/u/kaushalshriyan)\
**Post date:** [June 18, 2020, 5:33pm UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682/1 "2020-06-18T17:33:59Z")

</div>

Hi,

I am currently running ES (version 7.5.1) three nodes in the cluster mode.

```
ES Node1:- 192.168.0.10
ES Node2 :- 192.168.0.11
ES Node3 :- 192.168.0.12

```

I want to migrate the data from the above running production cluster to new hardware in cluster mode whose IP details are as below.

```
ES Node1:- 172.16.1.10
ES Node2 :- 172.16.1.11
ES Node3:- 172.16.1.12

```

Is there an elegant and efficient way to copy the data from the current production ES Cluster ( 3 nodes) to the new hardware based ES Cluster ( 3 nodes). Any help will be highly appreciated and I look forward to hearing from you. Thanks in advance.

Best Regards,

Kaushal

---

<div class="post-metadata">

**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\
**Post date:** [June 18, 2020, 5:40pm UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682/2 "2020-06-18T17:40:07Z")

</div>

Some questions:

1. Is the new cluster in the same premise?
2. Do you need the same cluster name or different name?

---

<div class="post-metadata">

**Author:** ![kaushalshriyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaushalshriyan/32/44563_2.png) [@kaushalshriyan](https://discuss.elastic.co/u/kaushalshriyan)\
**Post date:** [June 19, 2020, 12:39am UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682/3 "2020-06-19T00:39:25Z")

</div>

Hi Fadjar,

1. Is the new cluster in the same premise?  
Answer:- No

2. Do you need the same cluster name or different name?  
Answer:- same cluster name.

Best Regards,

Kaushal

---

<div class="post-metadata">

**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\
**Post date:** [June 19, 2020, 3:35am UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682/4 "2020-06-19T03:35:42Z")

</div>

Because no 1 in No, it means you need to have big pipe if want to use the solution that I ever done.  
what I've done is add one by one the new server into existing cluster, modify the node type then after all new nodes as a member of the cluster, the old one will fade one by one.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 17, 2020, 3:35am UTC](https://discuss.elastic.co/t/migrate-data-from-current-production-elasticsearch-nodes-to-a-new-hardware/237682/5 "2020-07-17T03:35:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.