Documentation Center

Translation Memory migration

Many WorldServer prospects and customers have legacy TM data originating from other third-party TM systems. Often, this data is the result of years of translation efforts. While WorldServer provides greater control over their translation processes, it would not be economically feasible for customers to lose the ability to effectively leverage their historical TM data. In the past, moving TM data from one TM system to another could result in a substantial loss in leverage, and thus, additional translation costs.

SDL has invested substantial time and development into improving the migration process involving TMs from products such as TRADOS, Star Transit, and SDLX.

Now customers can enjoy the benefits of the WorldServer product with minimal loss in leverage of their historical TMs. In fact, some customers have benefited from increased leverage rates due to related WorldServer TM technologies, such as the automatic split/merge and segment repair technologies (described elsewhere in this document).

The WorldServer product provides two tools for assisting in the migration of legacy TM and translation data: the asset alignment automatic action, and the TMX migration utility. The choice of which tool to use depends on the format in which the translated content is available.
  • Use asset alignment if the source and target assets are all that is available.
  • Migrate TMX files, with the stored TM data, from third-party tools in two ways. Import files directly if they are in 1.4b format. If they are not, use the Trados2Idiom utility to process the files before import.

An automatic WorldServer process performs alignment validation on the source and target segments when SID values are available. This ability can be modified as described in SID- based alignment.