Migration
Switch to Lingobit without translating everything again.
Lingobit imports existing translations straight from your localized EXE, DLL, and resource files — no old project needed. Switching costs a project setup, not a retranslation.
- Start from
- The version you translated
- Bring
- Its localized EXE, DLL, or resource files
- Then
- Scan for Changes to your current build
- Also
- Translation memory and terminology
On this page
Translated it once? Those translations are still yours.
By hand, in another tool, or by an agency: what matters is the localized files you shipped. Lingobit takes the translations from them.
Translated long ago? Reuse it for the new release.
Why start from the old version?
Its localized files were made from it: a 100% match, sizes included. Scan for Changes then marks exactly what changed, the same step as for every release if you had used Lingobit all along. Imported straight into the new version, a changed string takes its old translation unmarked.
Pick your path by what you have today.
After the switch, the next release costs only the changes.
From now on every build goes through Scan for Changes: translations carry over, and only what is new or changed goes to translators.
Import works best when old and new versions still match.
Best fit
- You still have the build that the localized files were made from
- Resource IDs stayed stable between versions
- The old process produced localized binaries or resource files
Needs review
- Resources were renamed or reorganized
- The UI was rewritten on another platform: use translation memory
- Localized files were edited by hand
- Custom formats or mixed workflows are involved
- Runtime-generated strings are not in the files
What migration does and does not do
Migration brings old translation work forward, but it does not guarantee perfect automatic reuse or remove manual review.
What Lingobit helps with
- Importing translations from the localized files you already have, item by item
- Carrying them to the current build with Scan for Changes
- Reusing translation memory, CAT tool files, and terminology
- Finding what to fix and review with validation, statuses, and filters
What still needs review
- Everything listed under Needs review
- Strings marked as changed, fuzzy, or new after the scan
- Final testing of the localized application and sign-off before release
See how much of your existing translation work can be reused.
Use the version you translated, its localized files, and your current build. Import, scan, validate, and review what changed.