---
title: "Sandbox to Production Object Transporter checklist — Kiweely"
description: "Prepare access, package or single instance, clear Pre-Migration Check, Merge security by default, then migrate Sandbox config to Production."
url: https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist
---

# Sandbox to Production Object Transporter checklist

Confirm Customer Central access, build a supported Sandbox package or single instance, clear Pre-Migration Check, review Pre-Migration Diff, keep Merge for security unless you mean Override, then migrate to Production and keep the Post-Migration report.

-   **Checked** against Workday on November 17
-   Applies to **Workday Object Transporter**
-   3 min read
-   Published November 17
-   By Kiweely

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 |
| --- | --- |
| Customer Central and OX access configured | Steps: Configure Access to Customer Central and Object Transporter completed for migrators |
| Package migration rights granted | Maintain Access to Customer Central Tooling allows the package type you will move |
| For CCT Advanced packages | OX Migration: Full Object Coverage selected; CCT auditor and packager domains assigned |
| Supported objects confirmed | Object Transporter Supported Objects (OX) report includes your implementation types |
| Reference IDs cleaned in Sandbox | Blank or colliding IDs fixed before packaging |
| Not an extract aimed at Production | Extracts cannot load to Production; stage on Implementation or Sandbox, then OX to Production |

## Choose the migration shape

1.  **One known object.** On the Sandbox instance, Related Actions > Migrate with Object Transporter. Workday redirects you to Customer Central.
2.  **A prepared package.** Create the configuration or security configuration package, then Migrate Packages with Sandbox as source and Production as target.
3.  **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

1.  Select Source Tenant (Sandbox) and Target Tenant (Production) when you start from Customer Central. Starting from Sandbox prepopulates the source.
2.  Optional: enter an External Change Request ID so Migration Reports keep the approval trail.
3.  Wait for Pre-Migration Status. If Workday finds missing prerequisites, open Pre-Migration Check.
4.  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.
5.  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.
6.  Rescan Target after Production fixes, or Retry Migration after Sandbox fixes.
7.  When the Pre-Migration Diff appears, expand Modified and New. Use View Attribute Diff on dependencies. Workday recommends reviewing dependents before you proceed.
8.  Set effective dates when prompted. Default 01/01/1900 or a chosen date; dependencies of a single instance inherit that date.
9.  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.
10.  Security group and business process security policy permission migrations stay additive. A security administrator must remove Production assignments manually if something should go away.
11.  Proceed with Migration, review the summary, Start Migration.
12.  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.

## Sources checked

-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Migrate Packages with Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/dgv1633434385688.html)
-   [Migrate Single Instances with Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/tmt1675299857714.html)
-   [Migrate Configuration Changes with Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/migrate-obect-changes-by-specific-users-and-timefr.html)
-   [Object Transporter Migration Paths](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/reference--object-transporter-migration-paths.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Which Object Transporter migration paths does Workday support? Object Transporter allows migrations only between documented tenant types. Implementation and Sandbox can target Implementation, Sandbox, and Preview. Production can target those non-Production tenants for supported types, but single-instance migration from Production is not supported.](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [### Object Transporter or Configuration Change Tracker: which moves Workday config? Object Transporter migrates configuration you select, with dependents on standard packages. Configuration Change Tracker builds a change list by user and time, then hands an Advanced package to OX without auto-adding extra dependents.](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [### Why does Object Transporter block single-instance migration from Production? Workday does not support OX single-instance migration from Production. Production can still source Sandbox, Implementation, and Preview for other supported types. Use a package or Configuration Change Tracker instead.](https://kiweely.com/guides/workday-ox-production-single-instance-limits)
-   [### How do I build a Configuration Change Tracker package by user and time? Configuration Change Tracker builds a change list for selected users and a timeframe. Package Ready to Migrate instances as an Advanced configuration package, run blank reference ID and exception audits, then launch Object Transporter. Advanced packages migrate only what you selected.](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [EIB spreadsheet mapping when an AI assistant drafts the load](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [Custom reports and RaaS when an AI assistant is helping you build them](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)
-   [What AI tools can a Workday consultant use to build reports, calculated fields and EIB loads faster?](https://kiweely.com/guides/ai-tools-for-workday-reports-calculated-fields-eib)
-   [Which Workday Integrations May Auto-Remediate](https://kiweely.com/guides/which-workday-integrations-may-auto-remediate)
-   [An Integration Run Book Assistants Can Query](https://kiweely.com/guides/workday-integration-run-book-for-assistants)
-   [When Workday Integrations Should Leave the Tenant](https://kiweely.com/guides/when-workday-integrations-leave-the-tenant)
-   [Workday API Rate Limits When Many Employees Ask Questions in Chat](https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)
-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)
-   [How an admin sets up the Workday API client for Kiweely Bridge](https://kiweely.com/blog/kiweely-bridge-ai-admin-api-client-setup)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
