Salesforce Translation Workbench: Deploying Translated Terms via Change Sets to Another Org

Requirement: Include Both the Translation and the Translated Component

In order for translated terms to be migrated via change set, both the language translation and the component being translated must be included in the change set.  For example, if you are migrating a custom field label translation, the custom field must be in the change set.

Requirement: Set Language to Active in Target Org

The language must be set to Active in order for it to display correctly in the target organization. Otherwise the translations will only appear in the editor and not on the live records.

Limitation: Components That Cannot Be Included in Change Sets

When the translated components cannot be included in a change set (such as custom picklist values for a standard field), these components must be translated with the translation workbench in the target organization.