My import did not bring everything across
Usually the run is still going or stopped early, the token could not see everything, or the content is something an import does not carry.
These checks apply to a migration from Lokalise, Phrase, Crowdin, Transifex, Weblate or POEditor. See Import from another tool.
Is it still running?
An import runs in the background, so you can leave the page. Open Import again to see the run's state, and Import history for past runs. What this run did lists what actually happened: Keys created, Translations written and Languages landed.
Did the run stop early?
- "This run stopped at the import limit, so your source project still holds more than came across." Run the import again: it adds the rest rather than starting over.
- "Import cancelled" or "Import stopped": whatever had already been imported is kept. Running the import again adds the rest.
Could the token see everything?
A read token imports exactly what it can see. If it was limited to some projects or some languages in the tool you are leaving, the rest stays behind. Check the token's scope there, and check which projects you picked under Choose what to read: projects you did not pick are never touched.
Was it something an import does not carry?
Before you start, Review this import shows what comes across, what does not (it stays in your old tool), and what makes it smaller. Two things in particular:
- Plural keys skipped in the run's ledger counts plural keys the import did not bring across.
- Keys with a repeated name counts keys whose name appeared more than once in the tool you are leaving. One project holds each key name once.
Translation memory and glossaries are separate from a migration: they do not come across with your keys. You can import glossary terms from a CSV or TBX file; see The glossary.
Are you looking at the right project?
If you chose A new project under Import into, the content is in a newly created project, not in one you already had.
Do the translations look untranslated?
Imported translations land as human-authored translations, marked edited, not as Glossa drafts. If a string is empty here, it was probably empty in the tool you are leaving too.
Related
My single sign-on login fails
Get back in with an Owner's password first, then check the test result, the domain, the certificate and the values your identity provider holds.
My strings are not showing up in the editor
Check the filters first, then the language, then whether the push actually landed, in that order, because the first is by far the most common.