Workday’s Object Transporter topics treat Sandbox to Production as a normal cutover: the single-instance guide’s example migrates a Sandbox custom report to Production, and Migrate Packages calls out routine updates from sandbox environments to Production. Use this checklist so access, package shape, prerequisites, and security merge behavior are settled before Start Migration.
Before you open Object Transporter
| Step | Done when |
|---|---|
| StepCustomer Central and OX access configured | Done whenSteps: Configure Access to Customer Central and Object Transporter completed for migrators |
| StepPackage migration rights granted | Done whenMaintain Access to Customer Central Tooling allows the package type you will move |
| StepFor CCT Advanced packages | Done whenOX Migration: Full Object Coverage selected; CCT auditor and packager domains assigned |
| StepSupported objects confirmed | Done whenObject Transporter Supported Objects (OX) report includes your implementation types |
| StepReference IDs cleaned in Sandbox | Done whenBlank or colliding IDs fixed before packaging |
| StepNot an extract aimed at Production | Done whenExtracts cannot load to Production; stage on Implementation or Sandbox, then OX to Production |
Choose the migration shape
- One known object. On the Sandbox instance, Related Actions > Migrate with Object Transporter. Workday redirects you to Customer Central.
- A prepared package. Create the configuration or security configuration package, then Migrate Packages with Sandbox as source and Production as target.
- A user-and-time change window. Run Configuration Change Tracker in Sandbox, package Ready to Migrate, validate, then Launch Object Transporter in Customer Central.
Do not start from Production with a single-instance related action. Workday does not support single-instance migration from Production.
Premigration checklist
- Select Source Tenant (Sandbox) and Target Tenant (Production) when you start from Customer Central. Starting from Sandbox prepopulates the source.
- Optional: enter an External Change Request ID so Migration Reports keep the approval trail.
- Wait for Pre-Migration Status. If Workday finds missing prerequisites, open Pre-Migration Check.
- Resolve issues in order. Workday shows the first 50 prerequisites only until those are fixed. Missing means no corresponding target instance, a missing Reference ID, or a mismatched Reference ID.
- For Non Mappable = Yes, sign in to Production and create or fix the instance and Reference ID. For Map Instance, use tailored loading with a compatible Production Reference ID.
- Rescan Target after Production fixes, or Retry Migration after Sandbox fixes.
- When the Pre-Migration Diff appears, expand Modified and New. Use View Attribute Diff on dependencies. Workday recommends reviewing dependents before you proceed.
- Set effective dates when prompted. Default 01/01/1900 or a chosen date; dependencies of a single instance inherit that date.
- If security policies differ, open Edit Migration Behavior.
- Merge (Recommended): additive; Workday’s default for routine Sandbox to Production updates.
- Override: replace Production policies with Sandbox. Use for initial deployments or when Sandbox is authoritative.
- Manual Selection: Merge or Override per policy.
- Security group and business process security policy permission migrations stay additive. A security administrator must remove Production assignments manually if something should go away.
- Proceed with Migration, review the summary, Start Migration.
- Open the Post-Migration report. Summaries remain available for 2 years. Optional: save a Tenant Compare.
Do not skip
- Viewing Attribute Diff on modified dependencies.
- Matching Reference IDs across Sandbox and Production before you force the migrate.
- Keeping Merge unless you intentionally overwrite Production security.
- Confirming that transactional and reference data OX will not move (locations, workers, and similar) already exist correctly in Production.
Frequently asked questions
Can I load a configuration extract straight into Production?
No. Concept: Object Transporter says you cannot load configuration extracts to Production. Import to Implementation or Sandbox, then OX to Production.
What if Pre-Migration Check keeps growing?
You must clear the first 50 listed prerequisites before Workday reveals the next set. Fix, Rescan Target, and continue.
Should I use CCT or a hand-built package for Production?
Use CCT when several users changed Sandbox during a window and you want only vetted Ready to Migrate instances. Use a hand-built package or single instance when you already know the objects.