Migrating from i18nexus to Locize
If you want to move your translations from i18nexus 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 i18nexus to understand how our engineering-first approach differs.
1) Export your localization files from i18nexus
There are three straightforward ways to get your translations out of i18nexus:
A) Export from the i18nexus dashboard (Export tab)
- Log in to your i18nexus account and open the project you want to migrate.
- Open the Export tab in the project dashboard.
- Choose the i18next/JSON export (i18nexus provides an i18next JSON export and a ready-to-copy configuration snippet for i18next integrations).
- Download the exported JSON files for each language and namespace you use.
B) Download using the i18nexus CLI
i18nexus provides a CLI that can pull translations as JSON files. Example:
# pull translations (replace <YOUR_PROJECT_API_KEY>)
i18nexus pull -k <YOUR_PROJECT_API_KEY>This downloads your project translations as JSON files that you can import into Locize.
C) Export via the i18nexus API
If you prefer scripting or automation, i18nexus exposes HTTP endpoints that return project translations as JSON. Example endpoints:
GET /project_resources/translations/:language_code.json— translations for a single language (all namespaces)GET /project_resources/translations/:language_code/:namespace.json— translations for a single language + namespaceGET /project_resources/translations.json— all translations for the project
You can curl these endpoints or call them from your CI to fetch JSON programmatically.
2) Create a Locize project
- If you haven’t already, create an account and your first project.
- Add the languages you need in Locize.
- (Optional but recommended) Decide on namespaces and create them in Locize so your imported JSON files map to the correct namespaces.
3) Import your files into Locize
You can import the JSON files you exported from i18nexus into Locize using any of these options:
- UI import — upload JSON files directly in the Locize dashboard.
- CLI — if you prefer to import programmatically or keep translations in sync with your repository.
- API — automate imports from scripts or CI pipelines.
4) Verify & go live
- Spot-check a few keys in each language (pay special attention to plural forms and interpolation placeholders).
- Confirm your reference language in Locize matches what your app expects.
- If you use i18next in your app, use the Locize CLI or API to keep Locize and your repo in sync (pull translated JSON into your repo as part of your build/deploy).