How can I migrate my data to Localazy from another provider?

Export your content from your current provider into any of Localazy’s supported file formats, such as JSON, XLIFF, YAML, CSV, Excel, RESX, or PO/POT, then upload it to Localazy like any other content. There’s no special “migration” format; Localazy treats already-translated files the same way it treats a fresh upload.

The main thing to get right is telling Localazy which language each file represents, either through auto-detection or by extracting it from the file path or name, and uploading those already-translated files in a separate CLI upload group from your source language files. That keeps the migration from interfering with work your translators are already doing on the project.

Localazy also identifies each string by its path, file name, and key together, so keep those consistent across the languages you’re migrating. Before running the real thing, use localazy upload -s to simulate the upload and check how Localazy will map your files, without changing anything in your project yet.

If what you’re migrating is a translation memory rather than app resource files, Localazy can also take a TMX file directly.