Importing Translations via Data Import

The Data Import wizard's Translation Studio target lets you bulk-import translations from CSV files. This is the right path for large initial translations, externally translated batches, or replacing many translations at once. For ongoing edits, use the Translation Studio editor.

This page covers the wizard flow for the Translation Studio target. For the full Translation Studio module, see Using the Translation Studio and Bulk Importing Translations.

Supported Categories

The Translation Studio target supports four translation categories. Pick one per import.

Step-by-Step

1. Open Setup > Manage > Import Data.
2. Select the Translation Studio target.
3. Select the category. If you chose Entity, also select the entity.
4. Select the target language.
5. Click Download Sample CSV Template. The Current Translation column is pre-filled with any existing translation for the selected category, language, and entity; you enter new or updated values in the empty New Translation column.
6. Edit the CSV offline. Add or update target-language values; leave rows you don't want to change as-is.
7. Return to the wizard and upload the completed CSV.
8. Confirm encoding (UTF-8 default) and delimiter (Comma default).
9. Proceed through the wizard's preview and review steps.
10. Click Start Import.

The Translation Studio target uses a simpler wizard flow than entity imports — there's no Operation step (translations are always upserts by item ID and language), no Configure step, and no Map Fields step (the template format is fixed).

The Template CSV

The downloaded template contains every translatable item for the selected category, language, and (where applicable) entity. Each row corresponds to one item with one aspect (where the type has aspects).

Columns include:

• RelatedToId — system-generated identifier; do not modify.
• Item Name — a human-readable label for the item.
• Type — e.g., Entity, Field, App; do not modify.
• Aspect — where applicable (Label, Help Text, PluralLabel, etc.).
• Master Value — the English source text. Do not modify.
• Current Translation — the existing translation, shown for reference. Do not modify.
• New Translation — the target-language column. This is the column you fill in.

Rules for the Translation Column

• Empty cells are skipped. Rows with an empty translation cell are not processed, preserving any existing translation for that row.
• Non-empty cells are upserted — existing translations are updated, new ones are inserted.
• To delete a translation (and let the master value serve as fallback), use the Translation Studio editor — the bulk import path does not delete translations.
• UTF-8 encoding is required to preserve accented characters and non-Latin scripts.

Reviewing Results

When the import completes:

• Total Processed, Succeeded, and Failed counts are shown on the Results page.
• The Success File lists translations that were applied.
• The Failure File lists rows that failed and why. Common reasons: item no longer exists, language no longer active, translation value exceeds maximum length.
• Open the Translation Studio in the same language to spot-check the imported translations.

To retry just the failures, edit the Failure File and re-upload it as a new import.

Tips

• One file per category — keep your batches focused. Don't mix Apps, Menu Items, Custom Labels, and Entity content in one CSV.
• Translate by entity for the Entity category. The template scopes to one entity per file.
• Share Custom Labels with your translators first so brand and product names stay consistent across every category they translate.
• Re-download the template between large translation batches if other admins have been editing translations. This keeps your file in sync with the current state.

Troubleshooting Tips

• If many rows fail with "language not active", confirm the target language is enabled in Language Settings.
• If rows fail with "item not found", the underlying item was deleted or renamed after the template was downloaded. Re-download and re-merge.
• If accented characters render as garbage, the file is not UTF-8. Re-save in UTF-8 and re-upload.
• For full symptom-by-symptom resolutions, see Translation Studio Troubleshooting and Data Import History and Troubleshooting.

<< Importing Records into Entities | Importing Portal Users >>