# How to migrate not\_analyzed ES 1.4.4-\>7.5.0

**URL:** <https://discuss.elastic.co/t/how-to-migrate-not-analyzed-es-1-4-4-7-5-0/212511>\
**Category:** Elasticsearch\
**Created:** [December 19, 2019, 3:40pm UTC](https://discuss.elastic.co/t/how-to-migrate-not-analyzed-es-1-4-4-7-5-0/212511 "2019-12-19T15:40:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michalz](https://avatars.discourse-cdn.com/v4/letter/m/6de8d8/32.png) [@michalz](https://discuss.elastic.co/u/michalz)\
**Post date:** [December 19, 2019, 3:40pm UTC](https://discuss.elastic.co/t/how-to-migrate-not-analyzed-es-1-4-4-7-5-0/212511/1 "2019-12-19T15:40:19Z")

</div>

I am migrating ES 1.4.4 to ES 7.5.0 and I get the following error in the logs:

In ES 1.4.4 we had several fields of type "index";"not\_analyzed" and a few with type "index":"no" and "index":"analyzed".  
How to migrate these index options to the new 7.5.0 options which are "idex":"true"/"false"?  
Should I migrate like this:  
"no" -\> "false"  
"not\_analyzed" -\> "true" + "type": "keyword"  
"analyzed" -\> "true"

?  
I have started by migrating everything to "true", yet I get:  
"Caused by: java.lang.IllegalArgumentException: Fielddata is disabled on text fields by default.  
Set fielddata=true on [type] in order to load fielddata in memory by uninverting the inverted index.  
Note that this can however use significant memory. Alternatively use a keyword field instead.",

I am new to ES and would like to ask for some direction.

Thanks

---

<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:** [January 16, 2020, 3:40pm UTC](https://discuss.elastic.co/t/how-to-migrate-not-analyzed-es-1-4-4-7-5-0/212511/2 "2020-01-16T15:40:21Z")

</div>

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