Steps: Migrate Packages with Object Transporter

Configure access to Object Transporter.

See Steps: Configure Access to Customer Central and Object Transporter.

Control Who Migrates Security Configuration Packages with Object Transporter

Object Transporter can migrate up to 300 instances and their dependencies collected together in a single entity called a configuration package. The

Object Transporter Supported Objects (OX)

report details which objects you can migrate.

You create a configuration package by selecting implementation types and specific instances of those types. You migrate a package by selecting the tenant where it was created and the tenant you want to move it to. Workday enables you to view exactly what changes a migration will cause in the target tenant before you proceed. If granted permission, you can also migrate security configuration packages containing domain or business process security policies associated with a specified functional area.

Before migrating reports, consider the downstream impact to edited reports in lower level tenants so that you don't migrate potential issues. Workday recommends that you validate reports after migrating them and consider the downstream impact to alerts and other processes.

Create a configuration package or a security configuration package.

See Create Configuration Packages for Object Transporter or Create Security Configuration Packages with Object Transporter.

Access the

Migrate with Object Transporter

task in 1 of these ways:

To start migration from a source tenant, select

Instance

Migrate with Object Transporter

Alternatively, you can view the package you want to migrate and select

Migrate

When you’re in the source tenant, Workday redirects you to the Customer Central to complete the migration.

To start migration from the Customer Central tenant, access the