Translation Data Transports 
The term translation data refers to both the proposal pool and any fingerprints in a translation system. When long text objects are evaluated in a worklist run, the translation status of most object types is determined by version management, whereby the version number of the source text is compared with that of the target text. However, there are some object types for which the fingerprint database is searched instead for an identical entry. If found, the object is given status translated, otherwise it remains modified. If no target text exists, then the object is new.
While transporting proposal pools is an efficient way of saving time and money and improving translation quality in the area of short text translation, it does not deal with any long texts that you may have translated. For long text translations, you have to use the translation data transport functions to transport all fingerprints from one translation system to another. It is possible to transport fingerprints and proposal pools at the same time using the translation data transport function, or you can transport either fingerprints or proposal pools on their own.
Here is an explanation of two key concepts when transporting translation data:
Source system: The system from which you export translation data.
Target system: The system into which you import translation data.
Prerequisites
Fingerprints and/or proposal pools exist for the required source and target language combinations. For example, while translating objects into five different target languages you saved long text translations actively and created proposals in the proposal pool.
You must be confident that the translation data you export is of an acceptable translation quality. Otherwise you will just be spreading errors from one system to the next.
Why not organize a proposal pool cleanup in the source system before exporting proposals? For more information, see DEMS Objects for Quality Assurance.
To play it safe, you could export or import only those proposals with a specific quality status or higher, as long as you are confident that only experienced translators create proposals with high quality statuses.
You could export only those fingerprints where you are confident that they have been created only by experienced translators.
Features
You can transport some or all of the translation data in a translation system to another translation system. When transporting fingerprints, you can choose to transport the proposal pool at the same time.
We recommend using the translation data functions for transporting fingerprints and/or proposal pools for the following reasons:
This is the only way of transporting fingerprints from one translation system to another.
It is a better method for transporting proposal pools because you can enter all the criteria for transporting fingerprints and proposal pools on one screen. Fingerprints and proposal pools are then transported at the same time.
It is easier to fine-tune your proposal pool transports on the translation data transport screens.
You do not have to specify the filenames yourself, these are generated automatically by the system.
You can enter a meaningful description for the export and import.
Activities
You need to perform the following steps for each source language and target language combination
Check that fingerprints and proposal pools actually exist for the source and target language combination. If not, then you have nothing to transport!
Export the translation data (fingerprints and/or proposal pool) from the source system.
Import the translation data (fingerprints and/or proposal pool) into the target system.