Vendor Migrations
Moving to a new localization vendor can touch more than your translation data. We help move your workflows and connected codebases so your team can leave the old system behind.
Know what needs to move
Your localization team may know the new vendor is a better fit without knowing every place the old one connects to your work. We review your current setup with your teams and identify what the move involves:
- Translation memories and termbases that your team needs in the new system.
- Handoffs, approvals, and translation release workflows that need to keep working.
- Integrations across codebases that may need to change when the vendor changes.
The work depends on your current and new vendors. A change of language service provider, for example, may require different technical work than a change of TMS.
Get fully onto the new vendor
We make a migration plan with your localization and development teams, move the translation history and terminology you use, and set up the new workflows. When code changes are needed, our developers can work with yours or make changes directly in your repositories if your company prefers.
We help your teams check that translation work and releases run through the new vendor before disconnecting the old one. If you have not chosen a vendor yet, we can help evaluate your options first.