# Migrate the machine learning job from one environment to other

**URL:** <https://discuss.elastic.co/t/migrate-the-machine-learning-job-from-one-environment-to-other/150070>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [September 26, 2018, 6:20pm UTC](https://discuss.elastic.co/t/migrate-the-machine-learning-job-from-one-environment-to-other/150070 "2018-09-26T18:20:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [September 27, 2018, 12:47pm UTC](https://discuss.elastic.co/t/migrate-the-machine-learning-job-from-one-environment-to-other/150070/2 "2018-09-27T12:47:34Z")

</div>

> [@Moving ML jobs and their data](https://discuss.elastic.co/t/moving-ml-jobs-and-their-data/136635/2):
>
> Hello, There currently is no officially supported way to export ML job configurations, models, and results as a unit and move to a new system. There are documented enhancement requests to add this capability in the future. The current recommended procedure is to manually, or programmatically copy ML job configurations from the old system to the new system re-train the ML models using historical data on the new system allow the new job(s) to run on-going on real-time data coming into the new …

---

_[View the full topic](https://discuss.elastic.co/t/migrate-the-machine-learning-job-from-one-environment-to-other/150070)._