Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2023-09-22
Migrate Single Instances with Object Transporter 2.0

Migrate Single Instances with Object Transporter 2.0

From source tenant, you can migrate an individual instance of a supported Implementation Type to a target tenant. Example: In the sandbox tenant, you use the related actions menu of a Custom Report to migrate that Custom Report to your production tenant. This method of migration saves you the effort of bundling multiple instances of Implementation Types in to configuration packages.
After you start the migration in your source tenant, Workday redirects you to Customer Central to complete the migration. Workday only migrates an instance when Object Transporter has an enabled Implementation Type for it. The
Object Transporter Supported Objects (OX)
 report details which objects you can migrate.
  1. From the related actions menu of the instance that you want to migrate, select
    Instance
    Migrate with Object Transporter 2.0
    .
  2. If Workday leaves the
    Implementation Type
     prompt unpopulated, select a valid type for your migration.
    Workday enables Object Transporter 2.0 to migrate instances of objects for a subset of implementation types. If Workday informs you it can't migrate using your selected Implementation Type, select another Implementation Type.
  3. (Optional) Enter an
    External Change Request ID
    .
    This option enables you to track requested and approved migrations. You can view
    External Change Request ID
     flags in the
    Available for Migration from Source Tenant
     table. You can also view them with all migration activity in the
    Object Transporter Migration Reports (OX 2.0)
     dashboard in Customer Central.
  4. Click
    Launch Object Transporter 2.0 in Customer Central
    .
  5. Sign in to Customer Central.
  6. Select the
    Target Tenant
     that you want to migrate the package to.
    When you start migration from a source tenant, Customer Central pre populates the task with your source tenant selections and displays the instance to migrate in the table.
  7. Click
    Migrate
    .
  8. When the selected instance is effective-dated, select the relevant
    Effective Date Strategy
     for this migration.
    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
    .
  9. On the Pre-Migration Status page, click
    Refresh
     or wait for Workday to complete the pre-migration check for your instance.
    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. Use the report to compare changes between configurations in the source and target tenants.
    • Finds no pre-migration issues, it skips the
      Pre-Migration Check
       report and generates a
      Diff
       report.
  10. If Workday does find pre-migration issues:
    • Click
      View Pre-Migration Check Report
      .
    • Follow the guidelines on the Object Transporter 2.0 Pre-Migration Check page to verify that the instance exists in the source and target tenants. Also verify that each instance has the same Reference ID in source and target tenants.
  11. Click
    View Diff Report
     to display the differences Workday found between your source and target tenants for the single instance. 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.
  12. (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
    .
  13. (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
    . When an attribute with
    Removal
     status exists in the target tenant but not in the source, migration removes it.
  14. Click
    Proceed with Migration
     to view a final summary of the instances to migrate.
  15. Click
    Start Migration
    .
  16. When the migration completes, click
    View Migration Report
     to see a summary of the changes, including migration failures, in the target tenant.
When migration is successful, Workday makes the single instance data available in the target tenant.