# Migrating clusters from ECE 1.1 to ECE 2.6

**URL:** <https://discuss.elastic.co/t/migrating-clusters-from-ece-1-1-to-ece-2-6/265100>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [February 22, 2021, 5:40pm UTC](https://discuss.elastic.co/t/migrating-clusters-from-ece-1-1-to-ece-2-6/265100 "2021-02-22T17:40:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhegarty](https://avatars.discourse-cdn.com/v4/letter/j/e495f1/32.png) [@jhegarty](https://discuss.elastic.co/u/jhegarty)\
**Post date:** [February 22, 2021, 5:40pm UTC](https://discuss.elastic.co/t/migrating-clusters-from-ece-1-1-to-ece-2-6/265100/1 "2021-02-22T17:40:53Z")

</div>

My team is attempting to come up with procedures to migrate clusters created on ECE 1.1 to a new installation that will be running ECE 2.6. We're trying to use remote snapshots. Our ECE 1.1 clusters have custom base paths, so we're copying that into `transient.restore_snapshot.repository_config` settings in the create deployment payload on ECE 2.6. The JSON validates and the create works until we receive the following error:

![Screen Shot 2021-02-22 at 9.37.08 AM](https://us1.discourse-cdn.com/elastic/original/3X/d/6/d62c82ae4ed747cf7ab44e818058a9d8271e021d.png)

Has anyone seen this error? We specified the type in `transient.restore_snapshot.repository_config`, but we still get the same error. We also tried specifying only one index, but that also failed with the same error.

---

<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:** [March 22, 2021, 5:41pm UTC](https://discuss.elastic.co/t/migrating-clusters-from-ece-1-1-to-ece-2-6/265100/2 "2021-03-22T17:41:04Z")

</div>

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