# How to move existing volume to ES Cloud

**URL:** <https://discuss.elastic.co/t/how-to-move-existing-volume-to-es-cloud/107075>\
**Category:** Elasticsearch\
**Created:** [November 9, 2017, 5:25pm UTC](https://discuss.elastic.co/t/how-to-move-existing-volume-to-es-cloud/107075 "2017-11-09T17:25:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![suchitgupta](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@suchitgupta](https://discuss.elastic.co/u/suchitgupta)\
**Post date:** [November 9, 2017, 5:25pm UTC](https://discuss.elastic.co/t/how-to-move-existing-volume-to-es-cloud/107075/1 "2017-11-09T17:25:35Z")

</div>

We are thinking about moving from self hosted Docker ELK stack to ES cloud and have a question that how we can move our existing docker volume to ES Cloud

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 9, 2017, 8:04pm UTC](https://discuss.elastic.co/t/how-to-move-existing-volume-to-es-cloud/107075/2 "2017-11-09T20:04:18Z")

</div>

You can take a snapshot into S3 and then restore it. Or you can reindex from remote and refresh your mappings and data structures.

---

<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:** [November 23, 2017, 8:04pm UTC](https://discuss.elastic.co/t/how-to-move-existing-volume-to-es-cloud/107075/3 "2017-11-23T20:04:57Z")

</div>

Closed on November 23, 2017, 8:04pm UTC

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