# Migrating to a new cluster?

**URL:** <https://discuss.elastic.co/t/migrating-to-a-new-cluster/26161>\
**Category:** Elasticsearch\
**Created:** [July 23, 2015, 1:39pm UTC](https://discuss.elastic.co/t/migrating-to-a-new-cluster/26161 "2015-07-23T13:39:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![apawl](https://avatars.discourse-cdn.com/v4/letter/a/df705f/32.png) [@apawl](https://discuss.elastic.co/u/apawl)\
**Post date:** [July 23, 2015, 1:39pm UTC](https://discuss.elastic.co/t/migrating-to-a-new-cluster/26161/1 "2015-07-23T13:39:42Z")

</div>

I have an elasticsearch index on a VM that needs an image upgrade. For most upgrades, we do blue-green deployments (ie, spin up a totally new instance, switch traffic over, and kill the old one).

It seems easy to replicate shards within an existing cluster, But i'd like to move everything to a new cluster completely. Is there an easy way to do this with Elasticsearch?

---

<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:** [July 23, 2015, 9:28pm UTC](https://discuss.elastic.co/t/migrating-to-a-new-cluster/26161/2 "2015-07-23T21:28:52Z")

</div>

You can do the blue-green method, have a look at leveraging `cluster.routing.allocation.exclude._ip` with it.

---

<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 5, 2017, 11:59pm UTC](https://discuss.elastic.co/t/migrating-to-a-new-cluster/26161/3 "2017-07-05T23:59:24Z")

</div>