# Issue with encoder\_options in JSON -\> YML migration script

**URL:** <https://ask.openrouteservice.org/t/issue-with-encoder-options-in-json-yml-migration-script/5952>\
**Category:** Announcements\
**Created:** [April 5, 2024, 9:46am UTC](https://ask.openrouteservice.org/t/issue-with-encoder-options-in-json-yml-migration-script/5952 "2024-04-05T09:46:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![amandus](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/amandus/32/669_2.png) [@amandus](https://ask.openrouteservice.org/u/amandus)\
**Post date:** [April 5, 2024, 9:46am UTC](https://ask.openrouteservice.org/t/issue-with-encoder-options-in-json-yml-migration-script/5952/1 "2024-04-05T09:46:59Z")

</div>

Dear users,

this is relevant to you if had a ors-config.json and:

- you were using the [ors-config-migration](https://hub.docker.com/r/heigit/ors-config-migration) tool before today
- you were setting `encoder_options` for your profiles
- there were numeric values for an encoder option

To fix this, just set the numeric values to the actual values they had before.

(There was [only a check for boolens](https://github.com/GIScience/ors-config-migration/commit/c91f8ef30290269a31e3c33d94193dfec5738c42) and would set 0 for anything else regardless of what your setting was)

Best regards