Workflow guides · · Frank Wei
Moving from Trados or Phrase to BabelBee: TMX and glossary migration
How LSPs and language teams export TMX 1.4 and glossary files from legacy CAT tools and reuse them in BabelBee in an AI-assisted production workflow.
Your translation memory and glossary are years of institutional knowledge. Switching production tools should not mean throwing that away. BabelBee is an AI-native production platform, but it still speaks TMX 1.4 — the format Trados, Phrase (Memsource), and OmegaT have exported for decades.
What to export from your CAT tool
Translation memory
In Trados Studio: File → Export → TMX. In Phrase: export TM as TMX 1.4. Keep language codes consistent (e.g. en-US → zh-CN) so BabelBee can match pairs correctly.
Glossary
Export CSV or TBX if your CAT supports it. BabelBee accepts glossary uploads on each project (see FAQ for size limits). For workspace-wide reuse, maintain a shared glossary under Account → Workspace.
How BabelBee uses TM differently
BabelBee uses translation memory to support AI-assisted production:
- Recalls relevant TM units semantically into the AI prompt (not only 100% matches)
- Flags inconsistencies with prior approved wording in the quality report
- Auto-saves approved segments back to TM when a project completes (opt-out per project)
Platform quota is word-based. It does not replace the TM-match and repetition analysis your team may need for client quotes or translator payments. If translations are revised after export, sync the final approved wording before reusing it in TM.
Recommended migration steps
- Pilot one language pair — export TM for your highest-volume pair only.
- Upload a representative document — contract, notice, or manual you know well.
- Compare terminology — check the quality report for TM-related flags.
- Invite one reviewer — run a Team Verified project to validate workflow.
- Expand — import additional TMX files into workspace translation memories.
What we do not migrate automatically
- Trados project packages (SDLPPX) — export to TMX first
- Segment-level status from old projects — only bilingual units in TMX carry over
- Vendor-specific QA profiles — re-create checks via BabelBee QA + human review
Frequently asked questions
Is TMX 1.4 enough?
For most teams, yes. If you rely on inline tags or custom XML, contact us before migrating complex DTP-linked projects.
Can we keep using Trados for some clients?
Many hybrid teams use CAT for agency production and BabelBee for in-house or fast-turn work. The same TMX can feed both if you export after each delivery.
Who can help with enterprise migration?
Email sales@babelbee.ai for Business-tier onboarding and bulk TM import guidance.