Skip to content
Open fromusers

Import and export translations

SurveysUsability testsIn-product surveys

Excel import and export lets localization teammates work outside FromUsers, then sync translations back into the study.

  • External linguists without FromUsers seats
  • Large studies where spreadsheet review is preferred
  • Backup or archival copies of translation state
  • Hybrid workflows: AI draft in-product, human edit in Excel
  1. Open the study translations tools.
  2. Choose Download Excel (or equivalent export action).
  3. Include the target languages you need.
  4. Share the file with translators.

The workbook maps rows to study entities and fields so FromUsers can merge changes safely on import. Keep identifier columns intact.

  1. Keep the exported column structure.
  2. Fill target-language cells only.
  3. Upload the Excel file from the translations tools.
  4. Review statuses after import. New or changed strings may need review.
  5. Preview participant screens in each language.
DoAvoid
Preserve entity and field identifier columnsRenaming or deleting key columns
Translate only target language cellsOverwriting default-language source text
Keep placeholders like {{first_name}} unchangedTranslating variable tokens
Note character limits for buttons and mobile UIPasting unbounded marketing copy into short labels
  1. Freeze default-language copy in the builder.
  2. Export Excel for French and German.
  3. Vendor returns the file.
  4. Import, then filter to needs review.
  5. Research lead spot-checks tasks and endings.
  6. Set the study Live.
  • Structural changes (new questions, deleted pages) should be exported again so row mappings stay current.
  • Import does not replace the need for in-product preview, especially for Arabic RTL.
  • Logic and randomization are not translated in Excel. Only participant-facing strings move through this file.

Common questions

What file format does FromUsers use?

Excel workbook format (XLSX). Export from the translations tools, edit offline, then upload the same structure.

Can one file include multiple languages?

Yes. Exports can include multiple target languages in a single workbook mapped back by entity and field identifiers.

Should I translate the default language column?

No. The default language is the source of truth and is not a translation target.