# Transfer es index from dev environment to PROD
**URL:** https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104
**Category:** Elasticsearch
**Created:** [May 3, 2016, 8:48pm UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104 "2016-05-03T20:48:40Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@subbu.nv](https://discuss.elastic.co/u/subbu.nv)
#### Post date: [May 3, 2016, 8:48pm UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/1 "2016-05-03T20:48:40Z")
current i am indexing 100GB of data in dev instance for testing. can i transfer this index to PROD and achieve the same search capabilities.
please advise.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 3, 2016, 10:33pm UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/2 "2016-05-03T22:33:23Z")
You can use snapshot and restore, or you can reindex the data into the other cluster.
---
### Author:  [@subbu.nv](https://discuss.elastic.co/u/subbu.nv)
#### Post date: [May 10, 2016, 11:58pm UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/3 "2016-05-10T23:58:30Z")
thanks, let me try out few these options. i used logstash to transfer from one index to other. but it is pretty slow.
input {
elasticsearch {
hosts =\> ["aaa-bb-search-1:9200"]
index =\> "type03"
scroll =\> "5m"
docinfo =\> true
scan =\> true
}
}
output {
elasticsearch {
hosts =\> ["localhost:9200"]
index =\> "type03"
}
stdout {
codec =\> "dots"
}
}
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 11, 2016, 4:02am UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/4 "2016-05-11T04:02:43Z")
> [@subbu.nv](#):
>
> it is pretty slow
How slow?
Have you tried increasing the bulk size in the output, and/or adding workers?
---
### Author:  [@subbu.nv](https://discuss.elastic.co/u/subbu.nv)
#### Post date: [May 11, 2016, 6:14am UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/5 "2016-05-11T06:14:38Z")
pretty Slow i meant, the movement of index from one env to other takes the same time of the actual index.
indexing to dev es = 2 hours.
movement of the index from dev to other env = close to 2 hours.
i tired workers 5 for both the case.
but i haven't tried bulk size in the output. can you please let me know how to do that. thanks.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 11, 2016, 6:49am UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/6 "2016-05-11T06:49:15Z")
Because that is what is happening, you are reindexing.
---
### Author:  [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [May 11, 2016, 7:05am UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/7 "2016-05-11T07:05:50Z")
Don't move the data, move the client.
Set up two clusters, and set up two client installations. If one is ready, turn that into production, and switch development to the other. If development is finished, turn development into production and switch back to the other for development, and so on. If you do this on the client installations, you don't have to move a single byte. This is blue-green deployment [http://martinfowler.com/bliki/BlueGreenDeployment.html](http://martinfowler.com/bliki/BlueGreenDeployment.html)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:52pm UTC](https://discuss.elastic.co/t/transfer-es-index-from-dev-environment-to-prod/49104/8 "2017-07-05T22:52:35Z")