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. - Sign in to Customer Central as a Customer Central User or Administrator.
- Access theTenant Dashboardworklet.
- SelectConfiguration Catalog.
- From theTarget Tenantprompt, select the tenant to migrate content to.
- Select a Configuration Package.You can click theNamecolumn heading and filter to find your package.
- ClickConfigure Package Instances.
- Select 1 or more instances to migrate.To migrate the entire package, select the check box in the table header.
- If your selected Configuratioh Catalog content contains instances with effective dates, select anEffective 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 ofImplementeation Types with Effective Dates.
- On the Pre-Migration Status page, clickRefreshor 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 aPre-Migration Checkreport. Use the report to compare changes between configurations in the source and target tenants.
- Finds no pre-migration issues, it skips thePre-Migration Checkreport and generates aDiffreport.
- If Workday does find pre-migration issues:
- ClickView 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.
- ClickView Diff Reportto display the differences Workday found between your source and target tenants for your Configuration Catalog instances. Each instance has a status icon:
Option Description ChangeInstance 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.NewInstance doesn't exist in the target tenant. Migration adds the instance from the source tenant to the target tenant.No ChangeInstance 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. - (Optional) ClickView 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, orNo Change.
- (Optional) If you're viewing dependencies, clickView Attribute Diffto examine the individual attributes that make up each dependent object.Workday provides a status icon for each attribute,Change,Removal, orNew. An attribute withRemovalstatus exists in the target tenant but not in the source. Migration will remove it.
- ClickProceed with Migrationto view a final summary of the instances to migrate.
- ClickStart Migration.
- When the migration completes, clickView Migration Reportto 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.