Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-08-23
Migrate Configuration Catalog Content with Object Transporter 2.0

Migrate Configuration Catalog Content with Object Transporter 2.0

Use the
Tenant Dashboard
 in Customer Central to migrate a Configuration Catalog package or 1 or more instances of the package to your implementation or sandbox tenant.
  1. Sign in to Customer Central as a Customer Central User or Administrator.
  2. Access the
    Tenant Dashboard
     worklet.
  3. Select
    Configuration Catalog
    .
  4. From the
    Target Tenant
    prompt, select the tenant to migrate content to.
  5. Select a Configuration Package.
    You can click the
    Name
     column heading and filter to find your package.
  6. Click
    Configure Package Instances
    .
  7. Select 1 or more instances to migrate.
    To migrate the entire package, select the check box in the table header.
  8. If your selected Configuration Catalog content 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
    .
  9. On the Pre-Migration Status page, click
    Refresh
     or wait for Workday to complete the premigration check for the Configuration Catalog content.
    Some instances have prerequisites that must exist in the target tenant for migration to succeed. Example: a calculated field. When Workday:
    • Finds premigration issues, it generates a
      Pre-Migration Check
       report. Use the report to compare changes between configurations in the source and target tenants.
    • Finds no premigration issues, it skips the
      Pre-Migration Check
       report and generates a
      Diff
       report.
  10. 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.
  11. Click
    View Diff Report
     to display the differences Workday found between your source and target tenants for your Configuration Catalog instances. Each instance has a status icon:
    Option Description
    Change
    Instance exists in the target tenant but isn't identical to the version in the source tenant. Migration overwrites the target version with the source version.
    New
    Instance doesn't exist in the target tenant. Migration adds the instance from the source tenant to the target tenant.
    No Change
    Instance is identical in the source and target tenants. No migration takes 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
    . An attribute with
    Removal
     status exists in the target tenant but not in the source. Migration will remove 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 in the target tenant.
    Postmigration summary reports remain available for 2 years.
When you’ve refined your configuration content to meet your customers' requirements, you can migrate the Configuration Catalog content from your sandbox tenant to the Production tenant.