# Changing field type - unexpected behaviour **URL:** \ **Category:** Developing with Prismic\ **Created:** [April 28, 2022, 10:40am UTC](https://community.prismic.io/t/changing-field-type-unexpected-behaviour/9900 "2022-04-28T10:40:17Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [May 3, 2022, 1:24am UTC](https://community.prismic.io/t/changing-field-type-unexpected-behaviour/9900/6 "2022-05-03T01:24:01Z")
@peter2, we've mentioned this in different threads in the past. Prismic can't know that a field has been changed to another type. So you need to be careful when moving from field types. See Phil's related response about this topic: > [@Migrating from 'Select' to 'Key Text' field type](https://community.prismic.io/t/migrating-from-select-to-key-text-field-type/1260/2): > > Hey Luke, This is a really tricky one given that you’re trying to get the selected data of the select field. There’s no way the Prismic will remember this even if you keep the same API ID. The only solution that I can see here is to use the [import/export feature](https://user-guides.prismic.io/en/articles/846079-introduction-to-import-export) that starts on the medium plan. You can export the current set up and run a script to get the select data and convert it in to key text fields. Then change your custom types and re-import the new restructured data. Let me know if you… --- _[View the full topic](https://community.prismic.io/t/changing-field-type-unexpected-behaviour/9900)._