Import translated entity and field text


Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2013, Dynamics CRM 2015, Dynamics CRM Online, Dynamics CRM 2016

If you have customized entity or field text, such as field labels or drop-down list values, you can provide the users in your organization who are not working with the base language version of your Microsoft Dynamics 365 implementation with this customized text in their own languages. To do so, you export the text strings for all your customizations so that they can be translated into the languages you use in your organization.

After the translation, you need to import the translated text strings into your Microsoft Dynamics 365 implementation before users can take advantage of the changes.


  • The file that you import must be a compressed file that contains the CrmTranslations.xml and the [Content_Types].xml file at the root.

  • Microsoft Dynamics 365 can’t import translated text that is over 500 characters long. If any of the items in your translation file are longer than 500 characters, the import process will fail. If the import process fails, review the line in the file that caused the failure, reduce the number of characters, and try to import again. Also note that after you import translated text, you must republish customizations.

  1. Make sure that you have the System Administrator or System Customizer security role or equivalent permissions. 

    Check your security role

    • Follow the steps in View your user profile.

    • Don’t have the correct permissions? Contact your system administrator.

  2. Go to Settings > Customizations.

  3. Click Customize the System.

  4. In the solution explorer, on the Actions toolbar, click Import Translations.

  5. In the Import Translated Text dialog box, specify the file that contains the translated text, and then click Import.

  6. When Microsoft Dynamics 365 finishes importing the translated text, click Close.


Publishing customizations can interfere with normal system operation. We recommend you schedule publishing when it’s least disruptive to users.

See Also

Export customized entity and field text for translation