Migration of choices from another application into sys_choice

Jhansi73966
Tera Contributor

‎04-16-2026 04:44 PM

what are the Certified possible ways to migrate choices in integrations?

0 Helpfuls
  • 892 Views
5 REPLIES 5

Palash_Sarkar
ServiceNow Employee
In response to SowmiyaC

2 weeks ago

Hi  @SowmiyaC 

 

If this is an OOTB option, please activate the i18n language plugin. Here is the list of plugins supported by ServiceNow.
 

ServiceNow does not support choice field translation natively using Dynamic Translation.

Dynamic Translation is designed for translating dynamic user-entered content or runtime text, and it explicitly supports only specific field types, such as:

  • String

  • String (Full UTF-8)

  • Multi Line Small Text Area

  • Wide Text

  • Translated Text / Translated HTML

How Choice Fields Are Handled Instead

Choice lists (drop-down values) are static user interface configurations rather than dynamic, user-generated string data. ServiceNow manages their translations through standard platform localization mechanisms:

  • The sys_choice Table: Choice list options and their translated labels are stored directly in the sys_choice table.

  • Language Packs: When you activate a standard ServiceNow Language Pack, translations for standard choice fields (like Incident State or Priority) are automatically populated here.

  • Manual or Bulk Translation: For custom choice fields, you must add the corresponding translated label and specify the target language code within the sys_choice record manually, or use the Localization Framework to manage the translation workflow.

 

With Regards,

Enterprise Globalization Deployment Architect

Palash Sarkar
Palash Sarkar
0 Helpfuls