Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-05-17
Migrate Packages with Object Transporter 2.0

Migrate Packages with Object Transporter 2.0

You can start a migration from a source tenant or from Customer Central. After selecting the source and target tenants and which content to migrate, you complete the migration in these 2 basic steps:
  • Perform a pre migration check to complete any target tenant work for instances in the package that have migration prerequisites. Not all instances have prerequisites.
    Workday displays the changes a migration will cause in the target tenant before you proceed.
  • Migrate the package using Object Transporter 2.0.
  1. Access the
    Migrate with Object Transporter 2.0
     task in 1 of these ways:
    • From a source tenant, view the package that you want to migrate and select
      Migrate
      .
      Workday redirects you to the Customer Central to complete the migration.
    • From the Customer Central tenant, access the
      Object Transporter (OX 2.0)
       worklet and click
      Migrate with Object Transporter 2.0
      .
  2. If you started the migration from a source tenant, select the
    Target Tenant
     .
  3. If you started migration from Customer Central, select:
    • The
      Source Tenant
       that contains the package that you want to migrate.
    • The
      Target Tenant
       that you want to migrate the package to.
    • The single instance, configuration package, or security configuration package from the list of packages that are available for migration.
  4. If your selected configuration package contains instances with effective dates, select an
    Effective Date Strategy
    . You can apply a default effective date of 01/01/1900 or manually select a date.
    Object Transporter 2.0 attempts to apply your selected date to every effective-dated instance in the the table of
    Implementeation Types with Effective Dates
    .
  5. On the Pre-Migration Status page, click
    Refresh
     or wait for Workday to complete the pre-migration check for your package.
    Some instances have prerequisites that must exist in the target tenant for migration to succeed. Example: A calculated field. When Workday:
    • Finds pre-migration issues, it generates a
      Pre-Migration Check
       report.
    • Finds no pre-migration issues, it skips the
      Pre-Migration Check
       report and generates a
      View Diff
       report.
    that
  6. If Workday finds pre-migration issues:
    • Click
      View Pre-Migration Check Report
       to see which instances have prerequisites.
    • Follow the guidelines on the Object Transporter 2.0 Pre-Migration Check page to verify that each instance listed in the table exists in the source and target tenants. Also verify that each instance has the same Reference ID in source and target tenants.
  7. Click
    View Diff Report
     to display the differences Workday found between your source and target tenants for the instances in your configuration package. Each instance has a status icon:
    Status
    Description
    Change
    Instance exists in the target tenant but isn't identical to the version in the source tenant. Migration will overwrite the target version with the source version.
    New
    Instance doesn't exist in the target tenant. Migration will add the instance from the source tenant to the target tenant.
    No Change
    Instance is identical in the source and target tenants. No migration will take place.
    Diff reports for migrations that don't proceed remain available for 30 days.
  8. (Optional) Click
    View Dependencies
     . Workday recommends that you examine the dependent objects that make up the selected instance.
    As with instances, Workday provides a status icon for each dependency:
    Change
    ,
    New
    , or
    No Change
    .
  9. (Optional) If you're viewing dependencies, click
    View Attribute Diff
     to examine the individual attributes that make up each dependent object.
    Workday provides a status icon for each attribute,
    Change
    ,
    Removal
    , or
    New
    . An attribute with
    Removal
     status exists in the target tenant but not in the source. Migration will remove it.
  10. Click
    Proceed with Migration
     to view a final summary of the instances to migrate.
  11. Click
    Start Migration
    .
  12. When the migration completes, click
    View Migration Report
     to see a summary of the changes, including migration failures, in the target tenant.
    Post-migration summary reports remain available for 2 years.
When migration is successful, Workday makes the configuration package contents available in the target tenant.