Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-08-23
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 you select the source and target tenants and which content to migrate, Workday processes the data. When Workday finds:
  • No errors or prerequisites to migration, it displays a
    Diff
    Report in the migration workflow. The report lists the changes to your target tenant after you complete the migration.
  • Errors in your migration, it displays the View Errors page in the migration workflow. The page includes guidelines for fixing the errors and retrying the migration.
  • Missing migration prerequisites, it displays a Pre-Check Migration page. The page lists source instances that are prerequisites to migration, with guidelines for resolving them.
    If you know the reference ID of a compatible target instance for a missing prerequisite, you can use Tailored Loading to map to the instance without leaving the workflow.
  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 table of
    Implementation Types with Effective Dates
    .
  5. On the Pre-Migration Status page, click
    Refresh
     or wait for Workday to complete the premigration 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 missing prerequisites, it generates a
      Pre-Migration Check
       report.
    • Finds no missing prerequisites, it skips the
      Pre-Migration Check
       report and generates a
      View Diff
       report.
  6. If Workday finds missing migration prerequisites in the target tenant:
    • Click
      View Pre-Migration Check Report
      .
    • Follow the guidelines on the Object Transporter 2.0 Pre-Migration Check page. In the Pre-Migration Check
      Errors
       table, Workday lists source instances that are prerequisites for migration. Prerequisites have no corresponding instances on the target tenant, or have missing or mismatched Reference IDs. To resolve a prerequisite, you can sign in to the target tenant and create the missing instance or resolve its Reference ID. You can also use Tailored Loading to map source instances that have no corresponding target instances to other compatible instances on the target tenant.
    You need the Reference ID of a compatible instance to map to it.
    To map to compatible instances:
    1. In the
      Errors
       table, click
      Map Instance
       for the missing prerequisite that you want to resolve.
    2. Enter the Reference ID of a compatible instance on the target tenant.
    3. Click
      Search
      .
    4. In the table of results, select the check box for the compatible instance. When the table lists multiple instances, select the one that is:
      • The same Implementation Type.
      • The most compatible with the source tenant instance.
    5. Click
      Apply Mapping
      .
      To view information on the compatible instance, click the link for it in the
      Mapping to
       column.
      To remove a mapping you don’t want, click
      Remove
       and follow the workflow to apply a new mapping.
    6. Click
      Rescan Target
      .
      When you’ve resolved all the missing prerequisites in the
      Errors
       table, Workday displays the Diff Report page to continue the migration.
  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.
    Postmigration summary reports remain available for 2 years.
When migration is successful, Workday makes the configuration package contents available in the target tenant.