# Migrating from old elastic stack cluster to higher subscription of new Elastic stack cluster

**URL:** <https://discuss.elastic.co/t/migrating-from-old-elastic-stack-cluster-to-higher-subscription-of-new-elastic-stack-cluster/232877>\
**Category:** Elasticsearch\
**Created:** [May 15, 2020, 7:32pm UTC](https://discuss.elastic.co/t/migrating-from-old-elastic-stack-cluster-to-higher-subscription-of-new-elastic-stack-cluster/232877 "2020-05-15T19:32:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bharat1](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@bharat1](https://discuss.elastic.co/u/bharat1)\
**Post date:** [May 15, 2020, 7:32pm UTC](https://discuss.elastic.co/t/migrating-from-old-elastic-stack-cluster-to-higher-subscription-of-new-elastic-stack-cluster/232877/1 "2020-05-15T19:32:23Z")

</div>

Dear Team,

I am tasked to do a migration from an existing Elastic Stack cluster to a new latest version of new Elastic stack cluster. I did went through the theoretical documents [https://www.elastic.co/guide/en/cloud/current/ec-migrate-data.html](https://www.elastic.co/guide/en/cloud/current/ec-migrate-data.html)  
but somehow felt like this really do not give me scenario based technical steps to get through this phase of migration. The total data size is 15 TB

The new cluster will have more capacity as well as latest version with higher subscription. The problem I do not know what

- prerequisite to be taken care
- any skeleton to be created at new cluster
  - If yes then how do I define those skeleton for larger indexes that are already available

- what or how the mappings, index, templates or any other stuffs that I should bring it in new cluster?
- Can I use Kafka to buffer the transmission of data from source to destination? Is kafka going to add value to whatever best solution/practice that is already available
- When we move index will it also move its entire skeleton, data, mappings, types, templates and whatever other stuffs that I mentioned

I have more questions basically as this is completely new, but unable to decide top 3 best strategy/practice and steps to follow to move everything from old to new cluster uninterrupted and less downtime.

Kindly guide me the appropriate process

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 15, 2020, 7:35pm UTC](https://discuss.elastic.co/t/migrating-from-old-elastic-stack-cluster-to-higher-subscription-of-new-elastic-stack-cluster/232877/2 "2020-05-15T19:35:32Z")

</div>

Which version are you migrating from? What type of data do you have? Is it immutable or do you perform updates? Are you using time-based indices?

---

<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:** [June 14, 2020, 5:01am UTC](https://discuss.elastic.co/t/migrating-from-old-elastic-stack-cluster-to-higher-subscription-of-new-elastic-stack-cluster/232877/4 "2020-06-14T05:01:25Z")

</div>

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