Import from another localization tool
Bring a project's keys and existing translations across from Lokalise, Phrase, Crowdin, Transifex, Weblate or POEditor in one run.
The importer is a one-time migration. It reads a project out of the tool you are leaving and writes its keys and translations into transglot. It only reads from the other tool and never writes back to it, and nothing stays connected after the run: the imported strings are ordinary transglot keys and translations.
Your existing translations arrive as human-authored translations, so AI never overwrites them. The source language seeds the keys, and any gaps can be filled by AI translation afterwards if the project has automatic translation on.
Requirements
- Plan: any plan. An import that creates a new project needs room for another project on your plan, and new languages count towards your plan's language limit.
- Role: Admin of the workspace, or an Owner of its account.
- A read API token from the tool you are leaving. A read-only token is enough.
| Tool | Where to find the token |
|---|---|
| Lokalise | Profile settings, then API tokens |
| Phrase | Phrase Strings: Profile settings, then API tokens. Generate a token with read access |
| Crowdin | Account settings, then API, then Personal Access Tokens |
| Transifex | User settings, then API token. The token starts with 1/ |
| Weblate | hosted.weblate.org only: Your profile, then API access |
| POEditor | Account settings, then API access |
Self-hosted Weblate is not supported by the importer. Export your files from Weblate and import them as files instead.
Run an import
Source
Open Settings for your workspace and choose Import. Under Where it is now, pick the tool, paste the token into API token and select Verify the token. Use show to check what you pasted.
The token is used only for this import and is not kept after the run ends.
What to read
Pick the source project to import. For Transifex and Weblate you pick one resource or component at a time, listed as Project > Resource, because the same key name can repeat across them.
Under Import into, choose A new project, or an existing project to merge into. An existing project keeps everything already translated and reviewed in it. Then select Review this import.
Review
Nothing has been written yet. The review shows four figures before you commit:
| Figure | Meaning |
|---|---|
| comes across | Keys and translations that will be written, as human-authored |
| does not | Content that stays in your old tool |
| stops the import | Problems that must be cleared before the import can run |
| makes it smaller | Limits that trim the import; it still runs |
Select each figure to see its detail.
Run
Select Start import. The import runs in the background and you can leave the page. When it finishes, What this run did shows the Keys created, Translations written and Languages landed.
To stop a run early, select Cancel this import. Cancelling stops the rest of the import; it does not undo what has already landed. An import cannot be undone once it has finished.
Every run is listed under Import history, newest first, with what it wrote and what it could not carry.
What stops an import
Your plan's project limit is reached. Choose an existing project under Import into, or change your plan.
When you import into an existing project, the source project's source language must match it. The review names both languages. Pick a project with a matching source language, or import into a new one.
What makes an import smaller
- Languages beyond your plan. If your plan has no room for every language in the source project, only the ones that fit are created, and the review says how many.
- Very large projects. One import run carries a limited number of keys and of keys times languages. The review tells you how much will come across before you start.
- Untranslated strings are not imported as translations: an empty translation is skipped.
- Keys transglot cannot carry as they are. After the run, What this run did lists them: Keys that did not come across (names longer than transglot allows) and Translations that did not come across (a plural form that does not match the key already in the project), alongside counts such as Plural keys skipped and Keys with a repeated name.
When you import into an existing project, translations already edited or reviewed there are kept, and the run lists them as Left alone here.
Troubleshooting
Check that it is a token for the tool you picked, that it has not expired, and that it can read the project you want. Picking a different tool clears the token field, so paste it again after switching.
The token is valid, but the account it belongs to holds nothing the importer can read. Check you pasted a token for the right account or workspace in the other tool.
This workspace has not run an import before. It is not an error.