Skip to main content
Administrator Guide
Last Updated: 2023-09-22
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 Configuratioh 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 the table of
    Implementeation Types with Effective Dates
    .
  9. On the Pre-Migration Status page, click
    Refresh
    or wait for Workday to complete the pre-migration 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 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 Configuration Catalog instances exist 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 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.
    Post-migration 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.