Migrating from Crowdin to Locize

If you want to move your translations from Crowdin to Locize, this guide walks you through exporting your files, setting up a Locize project, and importing everything cleanly.

Evaluating Locize?
See our comparison with Tolgee to understand how our engineering-first approach differs.

---

1) Export your localization files from Crowdin

1. Log in to your Crowdin account.
2. Open the project you want to migrate.
3. Go to Project Settings > Export.
4. Choose the format you need (recommended: JSON, but other formats like XLIFF or CSV are also supported).
5. Click Export to download your translation files.
6. If you have multiple languages, export each one as needed.
7. Extract the ZIP file if your export is compressed.

Crowdin also supports exporting via:

• CLI
• API

---

2) Create a Locize project

1. If you haven’t already, create an account and your first project
2. Add the languages you need
3. (Optional but recommended) Decide on namespaces and create them

---

3) Import your files into Locize

You can import using any of these options:

• UI import
• CLI
• API

---

4) Verify & go live

• Spot-check a few keys in each language (especially plural forms and interpolation placeholders).
• Confirm your reference language matches what your app expects.
• If you use i18next, consider setting up a workflow that keeps Locize and your repo in sync (CLI) or updates keys automatically (API).