Skip to main content
Start with a small, representative project. Verify its languages, keys, translations, and delivery before moving the rest of your content.

​
Choose how to start

Connecting a TMS does not migrate its projects into native storage. Glossary and translation-memory exchange do not migrate tasks, permissions, history, or review state.

​
Prepare the content

Export and retain the original source files, target files, glossaries, and translation memories from your current system. Record source and target locales, file paths, and the source revision used for each translation. Check supported formats. Use source files with stable keys and target files whose keys match those sources. Decide how locale variants such as pt-BR map to the languages in your product.

​
Move a pilot project

  1. Create a project and configure its languages.
  2. Upload the source files and confirm their paths.
  3. Import existing translations for one target locale at a time.
  4. Import a glossary and translation memory, then link the resources to the intended project.
  5. Add guidelines and configure team access.
Translation-file imports mark matching translations approved. Review the files before importing; do not use import to preserve an unreviewed draft status from another system.

​
Verify before switching delivery

Open representative strings in the Content Editor. Compare keys, target locales, placeholders, terminology, and any missing translations with your exports. Download target files and test them in your application. Recreate the required automations and delivery configuration, then test one source update. Coordinate when the previous system stops writing so two workflows do not compete for the same destination.

​
Next

Follow For localization managers to organize the team, or For developers to connect delivery. Contact support if a required import format or provider capability is unavailable.