Concept: Migrate Workforce and Financial Planning Applications Using Object Transporter

When you migrate your workforce and financial planning application packages using Object Transporter, we use these web services in the background for migration:

Get Workforce Planning Application
Put Workforce Planning Application
Get Financial Planning Application
Put Financial Planning Application

The Put web service doesn’t work if you try to use it by itself instead of through Object Transporter. We require you to use Object Transporter to ensure that a relationship exists between the sheet columns and the custom reports created. By itself, the Put web service can’t create that relationship.

When you migrate your planning application, we don’t migrate these values if your planning configuration manager is already active on your target tenant; instead, we retain these values on the target tenant as-is:

Instance code.
Plan version name.
Sheet name.
The metadata refresh schedule from the
Refresh Schedule
page.
The roster sheet data refresh schedule from the
Refresh Schedule
page.

If the planning configuration manager on your target tenant is inactive or doesn’t exist yet, then we override or copy over these values instead.