# Migrating to ECK

**URL:** <https://discuss.elastic.co/t/migrating-to-eck/243591>\
**Category:** Beats\
**Tags:** filebeat, metricbeat\
**Created:** [August 3, 2020, 2:40pm UTC](https://discuss.elastic.co/t/migrating-to-eck/243591 "2020-08-03T14:40:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wadhah](https://avatars.discourse-cdn.com/v4/letter/w/bc8723/32.png) [@wadhah](https://discuss.elastic.co/u/wadhah)\
**Post date:** [August 3, 2020, 2:40pm UTC](https://discuss.elastic.co/t/migrating-to-eck/243591/1 "2020-08-03T14:40:20Z")

</div>

Hello,

I am running ELK stack on an azure kubernetes cluster. Furthermore, I have filebeat and metricbeat running as daemonsets as well.  
Now, we are trying to deploy ECK (and get rid of the old ES cluster) and I am looking for the best option to migrate the filebeat and metricbeat indices without losing data to the new ECK. I was thinking of pausing the daemonsets, reindex the existing indices to the new cluster, point filebeat/metricbeat to the new ES host and finally resume the ds.  
However, it seems pausing the ds is not supported.

So I was wondering if you could please help me on how to proceed with this.

---

<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:** [August 31, 2020, 4:40pm UTC](https://discuss.elastic.co/t/migrating-to-eck/243591/2 "2020-08-31T16:40:26Z")

</div>

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