Steps: Migrate Packages with Object Transporter 2.0

Object Transporter 2.0 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.

Create Customer Central accounts.

See Steps: Set Up Customer Central Accounts.

Enable Customer Central to access other tenants.

See Steps: Set Up Customer Central Tenant Access.

(Optional) To perform migrations to your Production tenant using Object Transporter 2.0, enable Customer Central access to Production and create a Customer Central session for authentication.

See Set Up Customer Central Production Access and Create Customer Central Sessions.

Configure Object Transporter 2.0 Security Permissions.

(Optional) Control Who Migrates Security Configuration Packages with Object Transporter 2.0.

Create a Configuration Package with OX 2.0
as its

Package Version

or create a Security Configuration Package.

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

Access the

Migrate with Object Transporter 2.0

task in 1 of these ways:

To start migration from a source tenant, select

Instance