# Moving ML jobs and their data

**URL:** <https://discuss.elastic.co/t/moving-ml-jobs-and-their-data/136635>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [June 20, 2018, 8:13am UTC](https://discuss.elastic.co/t/moving-ml-jobs-and-their-data/136635 "2018-06-20T08:13:37Z")\
**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:** [June 20, 2018, 10:40am UTC](https://discuss.elastic.co/t/moving-ml-jobs-and-their-data/136635/2 "2018-06-20T10:40:14Z")

</div>

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

1. manually, or programmatically copy ML job configurations from the old system to the new system
2. re-train the ML models using historical data on the new system
3. allow the new job(s) to run on-going on real-time data coming into the new system

---

_[View the full topic](https://discuss.elastic.co/t/moving-ml-jobs-and-their-data/136635)._