Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2026-07-10
Steps: Migrate Translated Objects

Steps: Migrate Translated Objects

Configure access and security for Customer Central and Object Transporter:
Using Object Transporter, you can migrate any instance of a supported implementation type that contains translated values in their translatable fields. As you migrate, you can use the premigration Diff report to view the translation values in source and target tenants before migration. Workday never overwrites the translated values in the target tenant before migration. 
After migration completes, you can use the postmigration summary report to confirm migration success. Using Tenant Compare, which Workday makes available after migration in the Object Transporter workflow you can also compare instances of the implementation types between the source to target tenants and then save the comparisons as
Tenant Compare
 reports.
  1. Enable the relevant languages in your source tenant and any tenant to which you want to migrate.
    Security:
    Set Up: Tenant Setup - Global
     domain in the System functional area.
  2. Enter translations in your source tenant for a migratable instance.
    For a list of Workday objects and how to add translations to them, see Reference: Translations.
  3. To ensure that the Implementation Types for the instances you want to translate can migrate, view the tenanted
    Object Transporter Supported Objects (OX)
     report.
  4. If you’re adding translations to an object that you want to package with other objects, create a configuration package.
  5. Migrate the object with translated values in 1 of these ways:
  6. On the
    Pre-Migration Diff Report
     page, compare the premigration status of translated values in the source and target tenants.
    1. On the
      Modified
       tab, expand the implementation types to view the top-level instances.
      Workday enables you to compare translated values only for modified instances at the level of the modified dependency.
      Example: When you create a new object and add a translation value to it at the same time, Workday displays it on the
      New
      tab, which doesn't include views into the attributes that enable you to view translations. When you add, change, or remove a translation value to an already existing object instance, Workday displays the instance on the
      Modified
       tab, which enables you to view and therefore compare attribute values such as translations.
    2. Click
      View Dependencies
       for each new or modified top-level instance.
      The
      Dependencies Diff
      report shows you whether there are modifications to dependencies that, when migrated, will change corresponding target tenant dependencies in some way.
      The listed dependencies may or may not have attributes with translated values. You can examine translated values of modified dependencies in the
      Attribute Diff
       report.
    3. On the
      Dependencies Diff
      page, click
      View Attribute Diff
      for every modified dependency.
    4. On the
      Attribute Diff
       page, compare translated values in the side-by-side view. The left side displays the translated values in the source tenant. The right side displays the corresponding translated values in the target tenant.
      Workday assigns a
      Not Matching
       status to new, modified, or removed translated values and highlights them green. The source and target side-by-side view enables you to quickly assess the impact on the target tenant.
      If you don't want to include translated values in a migration, clear the
      Include Translations?
       check box during the migration process in Customer Central.
      Object Transporter doesn’t apply updates if you only modify a translation on an existing object. If you encounter this issue, we recommend that you clear the
      Include Translations?
       check box, complete the migration, and manually update the target tenant.
  7. (Optional) When migration completes:
    1. Click
      View Post Migration Report
      .
    2. Click
      View
      to verify that the instances migrated successfully.
      Postmigration summary reports remain available for 2 years.
    3. (Optional) On the
      Post-Migration Report
      page, click
      Run Tenant Compare
       to compare instances of implementation types between 2 tenants. You can save the comparisons as
      Tenant Compare
       reports.